[Bug 1909594] [NEW] No feedback when unmounting is finished
Public bug reported: I'm using "Files" 3.36.3-stable on Ubuntu 20.04. When writing large amounts of data to USB HDD it can take up to a minute to fully flush the data to HDD. "Files" provides a button for unmounting of my USB HDD. When I click this button unmount is started with "Unmounting usbdisk - Disconnecting from filesystem" appearing in notification area. This notification stays on the screen until I remove it with "X". It stays on the screen even after unmounting is finished. But in GUI there is NO notification that unmounting has finished! And if the notification is removed (with "X") there is also no indication that unmounting is still in progress. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1909594 Title: No feedback when unmounting is finished To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1909594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873052] Re: Showing two cursors after login
Which is the tracking issue for the required focal (20.04) kernel update to fix this bug? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806257] Re: gnome-shell excessive logging cannot bind to x11-unix
For some reason (I cannot remember) my root filesystem node "/" had the owner set to my user. I guess this used to work for some time. And some change in mutter or related packages made this break. Changed back owner to root.root and system is now starting properly. Don't know what to say about the system failing in such an obscure way. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806257] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1806257/+attachment/5218200/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806257] Re: gnome-shell excessive logging cannot bind to x11-unix
The gigabytes of log messages consist only of messages like this: Dec 2 17:08:33 host gnome-shell[3869]: failed to bind to /tmp/.X11-unix/X1293301: Datei oder Verzeichnis nicht gefunden Dec 2 17:08:33 host gnome-shell[3869]: failed to bind to /tmp/.X11-unix/X1293302: Datei oder Verzeichnis nicht gefunden Downgrading the mutter package makes the error go away. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806257] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1806257/+attachment/5218199/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806257] [NEW] gnome-shell excessive logging cannot bind to x11-unix
Public bug reported: Since the latest mutter upgrade mutter:amd64 3.28.3-2~ubuntu18.04.1 to 3.28.3-2~ubuntu18.04.2 the login screen can no longer be reached. Following symptoms are observed * keypresses are not registered; cannot even toggle NUM/CAPS lock * gnome-shell taking 100% CPU * logging gigabytes of messages to syslog * power-button does work and system shuts down when pressed --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-12-29 (1069 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Package: mutter 3.28.3-2~ubuntu18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-17 (287 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: Since the latest mutter upgrade mutter:amd64 3.28.3-2~ubuntu18.04.1 to 3.28.3-2~ubuntu18.04.2 the login screen can no longer be reached. Following symptoms are observed * keypresses are not registered; cannot even toggle NUM/CAPS lock * gnome-shell taking 100% CPU * logging gigabytes of messages to syslog * power-button does work and system shuts down when pressed + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2015-12-29 (1069 days ago) + InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + Package: mutter 3.28.3-2~ubuntu18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-39-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-02-17 (287 days ago) + UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806257] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1806257/+attachment/5218198/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505278] Re: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?
Confirmed on 14.04.1. I'm irritated that security related bugs can have "low" priority. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/505278 Title: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/505278/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 828756] Re: getting "connection is untrusted" warnings
That is true, bug is back again :( -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/828756 Title: getting "connection is untrusted" warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/828756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 597092] Re: palimpsest cannot unmount partition in fstab
Bug reproducable with HDD installation of oneiric. gnome-disk-utility 3.0.2-1ubuntu1 still gives error message: Error unmounting: umount exited with exit code 1: helper failed with: umount: only root can unmount /dev/mapper/vg-data2 from /mnt/data2 ** Changed in: gnome-disk-utility (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/597092 Title: palimpsest cannot unmount partition in fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/597092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 814214] Re: gvfs-gdu-volume-monitor crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 743724 *** https://bugs.launchpad.net/bugs/743724 ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/814214 Title: gvfs-gdu-volume-monitor crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/814214/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377175] Re: Volume Up button locks screen
I see two possibilities why the Macally keyboard locks the screen. Either it emits Usage ID 0xF9 on HID Usage Page 0x07 (Keyboard), or it emits Usage ID 0x19e on HID Usage Page 0x0C (Consumer). In order to verify this theory, it might be useful to have a look at the HID descriptor and the HID events. Depending on the results, special quirk handling of the keyboard might be added to the linux kernel and/or gnome-screensaver gets a option to ignore the (fake) "lock screen" key. HOWTO: 1. get the USB vendor+product ID using lsusb > lsusb Search for the line with the Macally Keyboard (e.g. I get "Bus 001 Device 007: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard" for my keyboard, so the vendor:id is 046a:0023) 2. look at the device descriptors > cd /sys/kernel/debug/hid > ls (I have here four entries, my keyboard makes up two of them 0003:046A:0023.0002 and 0003:046A:0023.0003; notice the matching vendor:id 046a:0023) > sudo cat $YOUR_DEVICE1/rdesc > sudo cat $YOUR_DEVICE2/rdesc 3. look at the events of the keys (Please be aware that the following records all your keypresses, so don't enter passwords or other sensitive information if you intend to post the event log to the bug report! Entering the password for "sudo" is ok, because it asks the password _before_ running the command) 3.1 first device > sudo cat $YOUR_DEVICE1/events press the volume up key exit with CTRL-C 3.2 second device > sudo cat $YOUR_DEVICE2/events press the volume up key again exit with CTRL-C Please find attached the output from my keyboard. It is only for demonstration purposes, because when connected via USB my keyboard does not exhibit the "lock screen" bug. ** Attachment added: "Out from hid-debug console session" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/377175/+attachment/2145520/+files/hid-debug-cherry.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/377175 Title: Volume Up button locks screen -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377175] Re: Volume Up button locks screen
Further information: I use the Keyboard (Cherry CyMotion Master Linux) in PS/2 mode on a docking station of an HP notebook. In "/usr/share/hal/fdi/information/30-keymap-hp.fdi" the scancode of the copy key (e00a) is mapped to "screenlock". In the same directory, mappings for several other computer manufacturers are provided. And since gnome-screensaver listens on "screenlock" (which is identical to "coffee"), the screensaver is started when the "copy" key is pressed. I use the same keyboard on a different computer (non-HP) and there the behavior is not observed, since the manufacturer string does not match in "30-keymap-hp.fdi" and the scancode (e00a) is not set. This is not directly related to the Macally keyboard since it is connected by means of USB, but somehow on kernel level keycode 152 (KEY_COFFEE) is likely to be generated, which completely bypasses the X11 key handling. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/377175 Title: Volume Up button locks screen -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377175] Re: Volume Up button locks screen
Launching "dbus-monitor --system" and pressing the button gives signal sender=:1.12 -> dest=(null destination) serial=2054 path=/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input; interface=org.freedesktop.Hal.Device; member=Condition string "ButtonPressed" string "coffee" In gnome-screensaver/src/gs-listener-dbus.c there is a hard-coded(!) handler for the "coffee" button which instruct gnome-screensaver (i.e. itself) to lock the screen. Apparently, unrelated buttons are mapped by HAL to the "coffee" button. E.g. I have the problem with my Cherry CyMotion master linux keyboard, when I press the "Copy" key. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/377175 Title: Volume Up button locks screen -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377175] Re: Volume Up button locks screen
** Also affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/377175 Title: Volume Up button locks screen -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
