** Changed in: wpa (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: wpa (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: wpa (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Deskt
Yes it appears the crash is:
Dec 25 15:18:52 x1c5 gnome-session[3657]: gnome-session-binary[3657]: WARNING:
App 'org.gnome.Shell.desktop' exited with code 1
Dec 25 15:18:52 x1c5 gnome-session-binary[3657]: WARNING: App
'org.gnome.Shell.desktop' exited with cod
which looks likely to be caused by
Public bug reported:
Where
-
This is happening on a fresh Linux Mint Tessa whose upstream is bionic
cat /etc/upstream-release/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"
What
The upstream package is provided by the
** Also affects: wpa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: wpa (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/173456
@Daniel,
Because this issue is for bionic,do we have schedule to back port it to bionic?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1772811
Title:
different behaviors for switch di
Incomplete: Someone please answer comment #7.
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu)
Status: New => Confirmed
** No longer affects: gdm3 (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplet
your boot options have 'drm.debug=0xe'
remove that from /etc/default/grub
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, whic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cheese (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/177855
> It has been privately reported as "gnome-control-center crashed with
SIGABRT".
Can you please tell us the bug ID? I can't seem to find any recent bug
by that title.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Package : gnome-control-center
Package version : 1:3.28.2-0ubuntu0.18.04.2
Ubuntu release 18.04
Hardware : Processor sandybridge i3 2.2Ghz Memory 3GB Disk capacity 128GB
I will move the dock position down. I open the gnome-control-center and
select Dock and move the position
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1810388
Title:
syslog filled with drm
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bu
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bu
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-c
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/
Can you try a different desktop that doesn't share code with Gnome
Shell? Unfortunately Cinnamon does, so isn't a useful test.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1807056
Are you using any gnome-shell extensions? If so, could you try
uninstalling them and tell us if the problem persists?
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notificat
** Summary changed:
- Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already
deallocated from ubuntu-d...@ubuntu.com/theming.js:416]
+ Gnome Shell logs errors [Object Meta.WindowActor (...), has been already
deallocated from ubuntu-d...@ubuntu.com/theming.js:416]
It is still crashing in the latest bionic update though :(
3.28.3-0ubuntu0.18.04.3
** Changed in: libgweather (Ubuntu Bionic)
Status: Fix Committed => Confirmed
** Tags removed: verification-done verification-done-bionic
** Tags added: verification-failed verification-failed-bionic
--
Y
Oops. I confused packages with similar versions.
** Changed in: libgweather (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Tags removed: verification-failed verification-failed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification b
Although... is bionic updates missing the fix?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1803487
Title:
gnome-shell crashes with SIGSEGV in
gweather_location_common_deseria
Any work on this bug will occur upstream, so you should ask there
instead:
https://gitlab.gnome.org/GNOME/mutter/issues/263
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1786757
T
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1769383, so it is being marked as such. Please look
** Tags added: disco
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1796251
Title:
gnome-shell crashed with SIGSEGV in __strlen_avx2() from
real_save_png() from gdk_pixbuf__png_
Thanks. That only shows a few seconds of CPU usage. How long was the
machine running when you collected that?
Can you please try again, leaving the machine idle for as many hours as
possible?
Also, did you confirm the power usage is still too high before sending
allprocs.txt?
--
You received th
Any update on this bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1786757
Title:
Gnome Shell screencast doesn't work at desktop resolution 4880x1085
Status in gnome-shell pa
Dear Jeremy, noted. I also find another bugs, Cheese. I will open a new
bugs report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1755536
Title:
gnome-control-center i
The mutter and gnome-shell fixes are both in version(s) 3.30.1, so Fix
Released in 18.10 and 19.04 already.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-shell (Ubuntu)
St
Ubuntu 19.04 will get the fix (in future, some time) via gnome-shell
version 3.31.2 or later.
Ubuntu 18.10 will get the fix (in future, some time) via gnome-shell
version 3.30.2 or later.
Ubuntu 18.04 doesn't seem to have the fix committed yet (gnome-3-28).
--
You received this bug notification
** Summary changed:
-
/usr/bin/gnome-shell:5:_g_log_abort:g_log_default_handler:default_log_handler:g_logv:g_log
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from g_logv("Function
AsyncReadyCallback terminated with uncatchable exce
It appears that in the recent past this crash became so prolific that it
might have been confused for other similar crashes in day to day bug
maintenance. For example, the link
https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
is actually a different crash with a differen
** Tags removed: artful
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1743736
Title:
In overview, windows from all workspaces are shown for the second
display (when using "Work
** Changed in: gnome-shell (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723857
Title:
onscreen keyboard appears whenever i t
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1025388
and then change the status of the bug to 'Confirmed'.
If, due to the nature
I think you'd need someone to figure out what/where is detecting the
combo jack is in use and whether it thinks an external mic is plugged in
or just blindly assumes one is plugged in.
I don't know what component is responsible for that detection so adding
a kernel task in case that's relevant...
I moved the above bug to GVFS:
https://gitlab.gnome.org/GNOME/gvfs/issues/360
In that bug, I've attached a Python script that reproduces the problem.
So this is not unique to duplicity or deja-dup.
However, we might reasonably work around it in duplicity by remounting
or similar when such an erro
Then you are commenting on the wrong bug. Please open a new one instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu login screen never appears when using the
Closed for Ubuntu since the bug is closed upstream. If you feel this is
incorrect then please comment upstream
(https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/505) and
then here.
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notifi
So, seems I have figured out the issue (at least on my Lenovo T460s) and
I think it lies with the Intel chip internal GPU.
If you use display port and HDMI-->Display Port adapter it won't work.
The Intel chip doesn't seem to support two DP connections at a time. But
you can connect Dp & HDMI-->DVI
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libcanberra (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/b
*** This bug is a duplicate of bug 1796606 ***
https://bugs.launchpad.net/bugs/1796606
** This bug has been marked a duplicate of bug 1796606
gnome-shell crashed with SIGSEGV in st_widget_get_theme_node →
ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
--
You received
*** This bug is a duplicate of bug 1799205 ***
https://bugs.launchpad.net/bugs/1799205
Sounds like it was bug 1799205, which is now fixed.
Please let us know if the problem persists.
** This bug has been marked a duplicate of bug 1799205
Ubuntu wayland sessions are not migrated to yaru
-
*** This bug is a duplicate of bug 1808853 ***
https://bugs.launchpad.net/bugs/1808853
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a membe
Comment on attachment 8959924
Bug 336193 - P1: Use SignalPipeWatcher to detect signals SIGTERM/SIGINT/SIGHUP
and quit application gracefully.
https://reviewboard.mozilla.org/r/228682/#review235956
r+ with or without the SIG_IGN case.
--
You received this bug notification because you are a memb
Comment on attachment 8959924
Bug 336193 - P1: Use SignalPipeWatcher to detect signals SIGTERM/SIGINT/SIGHUP
and quit application gracefully.
https://reviewboard.mozilla.org/r/228682/#review235302
> I based this off nsProfileLock's CATCH_SIGNAL() which does not
register for signal handlers that
Created attachment 8963553
Bug 336193 - P2: Use a second SIGTERM in killPid() to ensure parent process is
killed.
killPid() needs to do more than send a single SIGTERM to the parent
process now that it only triggers graceful shutdown, sending a second
SIGTERM terminates it forcefully like before.
Created attachment 8959924
Bug 336193 - P1: Use SignalPipeWatcher to detect signals SIGTERM/SIGINT/SIGHUP
and quit application gracefully.
Review commit: https://reviewboard.mozilla.org/r/228682/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/228682/
--
You received this
(sorry, by which I meant to say more specifically: 'killall firefox' has
the same issue, it prompts a session crash dialog for me on next
startup. It's just not something I use often since I usually use the
close button which works, but on shutdown the same mechanism is used -
of course with a time
Any news on this?
killall firefox does not work at all (Ubuntu).
pkill -x firefox-bingives a crash dialog when starting firefox next time.
A simple and gentle way to end firefox from Linux commandline would be nice.
--
You received this bug notification because you are a member of Des
Comment on attachment 8959924
Bug 336193 - P1: Use SignalPipeWatcher to detect signals SIGTERM/SIGINT/SIGHUP
and quit application gracefully.
Review request updated; see interdiff:
https://reviewboard.mozilla.org/r/228682/diff/1-2/
--
You received this bug notification because you are a member
*** Bug 365749 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/73536
Title:
MASTER Firefox crashes on instant X server shutdown
Status
*** Bug 1032010 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/73536
Title:
MASTER Firefox crashes on instant X server shutdown
Status
Comment on attachment 8959924
Bug 336193 - P1: Use SignalPipeWatcher to detect signals SIGTERM/SIGINT/SIGHUP
and quit application gracefully.
https://reviewboard.mozilla.org/r/228682/#review235302
(I'm not an XPCOM peer and so I considered passing the nsDumpUtils part to
Nathan, but the initial
(In reply to James Graham [:jgraham] from comment #45)
> Marionette has a method to invoke shutdown,
> but sending the response races with closing the marionette connection, so it
> isn't reliable. Signalling the process with SIGTERM would be the obvious
> solution, except for this bug. So we eithe
Comment on attachment 8959924
Bug 336193 - P1: Use SignalPipeWatcher to detect signals SIGTERM/SIGINT/SIGHUP
and quit application gracefully.
https://reviewboard.mozilla.org/r/228682/#review235302
> Is the |dispatchQuit| single quit logic necessary?
> It looks like nsAppStartup::mShuttingDown al
Comment on attachment 8963553
Bug 336193 - P2: Use a second SIGTERM in killPid() to ensure parent process is
killed.
https://reviewboard.mozilla.org/r/232486/#review237940
Harnesses built on top of Marionette client as test runner will use
SIGKILL to force killing the browser process. It is only
(In reply to Karl Tomlinson (:karlt) from comment #48)
> (In reply to James Graham [:jgraham] from comment #45)
>
> > Marionette has a method to invoke shutdown, but sending the
> > response races with closing the marionette connection, so it
> > isn't reliable. Signalling the process with SIGTER
(In reply to jonas from comment #63)
That is a bug (IMO) in most distros' shutdown/reboot sequences, where
they give applications no time to shut down before sending SIGKILL. I
would report to your distro.
--
You received this bug notification because you are a member of Desktop
Packages, which
Does this bug also include the session not being properly counted as
regularly closed when I shut down the computer normally with firefox
open? (And firefox offering me a misguided tab restore after a supposed
"crash" on next run) Because that's what I'm seeing here as a normal
Linux desktop user.
Comment on attachment 8963553
Bug 336193 - P2: Use a second SIGTERM in killPid() to ensure parent process is
killed.
https://reviewboard.mozilla.org/r/232486/#review237940
r+ with improved logging.
It seems odd that this is the only place in our test automation
requiring this change. Other test
Here's a revised version of the SignalPipeWatcher patch.
* SIGTERM/SIGINT/SIGHUP all do a graceful exit. I tested Chromium, VLC
and GIMP using strace with these signals and they all exit normally
returning exit codes and not signals.
* SignalPipeWatcher does not chain to previous handler and regi
'killall firefox' has no timeout as far as I know, so I think that is
completely irrelevant
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/73536
Title:
MASTER Firefox crashes on insta
Comment on attachment 8959924
Bug 336193 - P1: Use SignalPipeWatcher to detect signals SIGTERM/SIGINT/SIGHUP
and quit application gracefully.
Review request updated; see interdiff:
https://reviewboard.mozilla.org/r/228682/diff/2-3/
--
You received this bug notification because you are a member
Someone needs to rebase the patch here and push it to try. I'd be
willing to mentor this, but I don't have the time to do it myself.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/73536
Comment on attachment 8750107
Bug 336193 handle SIGTERM in SignalPipeWatcher then in the main thread to quit
I think this approach will work well, thanks.
SIGTERM will have no effect if Firefox gets stuck during shutdown, but I guess
that's reasonable because SIGTERM is intended to effect normal
Still a major problem, 9 years after raising this I only can see
discussions about? Firefox is not able to handle a standard SIGTERM? For
me a reason to change. Sorry to be this rude, but it is really a shame.
--
You received this bug notification because you are a member of Desktop
Packages, whi
Comment on attachment 8750107
Bug 336193 handle SIGTERM in SignalPipeWatcher then in the main thread to quit
Let's at least review all the patches here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.laun
Comment on attachment 8626516
bug336193.patch
Unfortunately, the last paragraph of comment 23 is still relevant.
(In reply to Kestrel from comment #39)
> * nsAppStartup::Quit calls nsIAppShell::Exit asynchronously which does most
> of the work so it doesn't block the signal handler.
It is more
Created attachment 8626516
bug336193.patch
Summary:
* nsProfileLock is already rigged for handling signals and is already
terminating (fatally) so it is only a small change to make it clean, this is
preferable to a GTK-specific implementation.
* A clean quit should be performed for SIGINT and
Created attachment 8750107
Bug 336193 handle SIGTERM in SignalPipeWatcher then in the main thread to quit
What about the attempt in this patch? I intercept SIGTERM using
"SignalPipeWatcher" as suggested, then I pass a task to the main thread
so it calls "nsIAppStartup::Quit(nsIAppStartup::eForceQu
(In reply to Christian Holler (:decoder) from comment #33)
>
> Are there any remaining problems with the attached patch?
What happened back in December 2012? Did the patch make it to the
official source?
The issue is still present in the current version of Firefox for Linux.
--
You received th
The SignalPipeWatcher class defined in xpcom/base/nsDumpUtils.cpp might
be of interest — it's used to trigger memory reports from a signal
handler (via the usual pipe-to-self trick), which sounds like the same
basic problem as this bug.
--
You received this bug notification because you are a memb
Comment on attachment 8626516
bug336193.patch
Review of attachment 8626516:
-
Karl, mind reviewing this? I'm not qualified to review unix signal
handling code.
--
You received this bug notification because you are a member of Deskt
This is a problem for geckodriver and for anything else that's using
marionette to control the browser (e.g. various test harnesses including
wpt). If we don't shut down the browser gracefully we lose out on the
ability to do various things that depend on clean shutdown (certainly
leak logging, per
** Changed in: mutter
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60
Public bug reported:
I was using ubuntu 18.04 on my computer (and previously 17.10), and I
got the sound card working correctly with pulseaudio.
After upgrading to 18.10, pulseaudio interface only detect my usb
microphone (BIRO UM1), but it does not detect my computer internal sound
card, either
I'm clearing the needinfo request since I cannot provide info without
assistance myself.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1796979
Title:
Intermittently can't connect to
Public bug reported:
graphics drivers on ubuntu 18.04 problem.
Live cd works ok, ubuntu 16 works ok.
Graphics card is atom series .. im thing
THANKS FOR HELP
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.18.0-041800-generic x86_64
NonfreeKernelModules
Thanks Diego. A similar situation here today. The whole Christmas season
at home no issues at all - many suspends (lid close), with and without
power supply. Coming today to the office, boom, unlock screen freeze
after providing the password.
One more hint - I've got the same SSID at home and my o
*** This bug is a duplicate of bug 1760795 ***
https://bugs.launchpad.net/bugs/1760795
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member
** Package changed: ubuntu-docs (Ubuntu) => network-manager (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1810660
Title:
vpn static route
Status in network-manager
Public bug reported:
After booting the system and login screen is displayed top right gear-
icon contains option to Suspend. However, selecting that action has no
results at all (no error message, nothing in any file under /var/log or
journalctl). I would like to get the suspend action to work sim
You have been subscribed to a public bug:
After upgrading to 18.04 I can no longer create a vpn with a static
route unless a gateway is specified.
Before (with 16.04) I could add 1 or more destination networks without a
gateway for each. Once the VPN connection was established, all static
routes
** Package changed: ubuntu => deja-dup (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1810665
Title:
Ubuntu 19.04 / DejaDup / can not Data return
Status in deja-dup package
You have been subscribed to a public bug:
Hello
Can not Data return of my system.
package missing
duplicity
python-gi
Install this
Start DejaDup, found not Files.
Action from ubuntuusers DejaDup to 18.10
Fond files, start return data, Error!
DejaDup is not in function.
I can not more test
Eero I filed the original report. To me your comment seems only critical
and not helpful, especially in a report where a fix is being released. If
someone uses the same location for backup this problem doesn't appear to
exist.
I try to file bug reports as I encounter them, along with any workaroun
It doesn't work on Ubuntu 18.04!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/975222
Title:
ath3k bluetooth adapter cannot load firmware
Status in libmtp:
Unknown
Status in libmtp
Hi guys, I have the same problem than John and Miles over different
Epson Wifi Scanners or combis (printer + scanner). After searching a
lot, many other Linux Distributions have the same problem in their
latest versions with the scanner drivers well installed and the
conection to the equipment work
Public bug reported:
Hi guys, in relationship with this closed post:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/950843, I
have the same problem than John and Miles over different Epson Wifi
Scanners or combis (printer + scanner). After searching a lot, many
other Linux Distributi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1205
The bug still persists in cosmic cuttlefish in combination with Samsung
SCX-470x, 13 years after #195782 was filed. The workaround also works
still, after I installed libsane-extras, xsane miracally started up
without an error. I suggest to change the package dependence so that
libsane-extras is in
Hi, please confirm the attached output of `ps auxw`.
** Attachment added: "allprocs.txt"
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+attachment/5227223/+files/allprocs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
hendra, please don't comment on old closed bugs since people don't
really look at closed bugs. It's better to open a new bug isntead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.n
I used my computer with "legacy boot" + gpt partitioning.
I added a second drive (an ssd to the hdd) and tried to install ubuntu
on the ssd. The installation failed (twice) at grub2.
The solution was to select "uefi boot" in bios and setting up an efi
partition. After that the installation went t
Yeah, let me close this :)
** Changed in: cheese (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1006515
Title:
cheese does not start and
** Description changed:
## Bug Reproduction Instructions ##
1. Install iscan-gt-s650-bundle-1.0.1.x64 driver from Epson
- 2. Launch iscan or any SANE application
+ 2. Connect Epson Perfection V39
+ 3. Launch iscan or any SANE application
## Current behavior ##
After a few seconds of the
Public bug reported:
## Bug Reproduction Instructions ##
1. Install iscan-gt-s650-bundle-1.0.1.x64 driver from Epson
2. Connect Epson Perfection V39
3. Launch iscan or any SANE application
## Current behavior ##
After a few seconds of the function call `sane_get_devices` the application
crashed
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Do you still see a problem related to the
1 - 100 of 128 matches
Mail list logo
