Bug#974172: libmutter-7-0: Cannot unlock screen with Wayland on arm64, keybard and mouse unresponsive
On Fri, Nov 13, 2020 at 1:54 PM Simon McVittie wrote: > Control: retitle -1 libmutter-7-0: Cannot unlock screen with Wayland on > arm64, keybard and mouse unresponsive > > On Thu, 12 Nov 2020 at 00:20:03 +0100, Gali Drudis-Sole wrote: > > On Wed, 11 Nov, 2020 at 10:32, Simon McVittie wrote: > > This works fine for me, and presumably other GNOME users, so there > must be > > something specific to your system that is relevant. > > > > Good. I hope to find it. > > One elephant in the room is that you're on an arm64 system, which is > certainly unusual for a GNOME desktop. We've had a report on IRC that > another arm64 user (with a different GPU) is seeing a similar bug. > Great. That looks like a good starting point. > > Nov 11 23:04:29 mobian gsd-usb-protect[2319]: Error calling USBGuard > DBus to > > change the protection after a screensaver event: > > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name > org.usbguard1 > > was not provided by any .service files > > This is not a problem and can safely be ignored. > > > Nov 11 23:04:29 mobian gnome-shell > > [2141]: Bogus presentation time 0 travelled back in time, using current > time. > > This might indicate a problem, I'm not sure. > > > Sorry, that was my error when reporting the bug. Version 3.38.0-2 DOES > WORK, > > but upgrading to the current testing version (3.38-1.2) DOES NOT WORK. > > Does 3.38.1-3 from experimental make any difference? That version has the > latest changes from the upstream gnome-3-38 branch, which will be released > in 3.38.2 at some point. > I've upgraded libmutter-7-0 and mutter-common to 3.38.1-3 from experimental, but there was no difference. The screen can be unlocked if it is not blanked, but it cannot be unlocked after blanking. > If 3.38.1-3 doesn't solve this, since you've been able to narrow this > down to two relatively close versions, it would be useful for someone > with appropriate hardware (I don't have this) to do a `git bisect` > between the good version and the bad version, to isolate which specific > change made this regress - that would make it a lot more likely that > someone can figure out the root cause. > I will give it a try. > > smcv > -- Galí Drudis Solé gal...@gmail.com
Bug#974172: libmutter-7-0: Impossible to unlock the screen with wayland+gdm, keybard and mouse unresponsive
Dear Simon, Thanks a lot for your answer. On Wed, 11 Nov, 2020 at 10:32, Simon McVittie wrote: Control: notfound -1 3.38.0-2 Control: found -1 3.38.1-2 Control: tags -1 + moreinfo On Wed, 11 Nov 2020 at 00:46:39 +0100, Gali Drudis-Sole wrote: After upgrading the system, locking the screen of gnome-shell under wayland, made it impossible to unlock the screen. This works fine for me, and presumably other GNOME users, so there must be something specific to your system that is relevant. Good. I hope to find it. What messages appeared in the system log (systemd journal) at the time that this happened? These two lines apear just after locking the system (gdm started with [debug] Enable=true). Nothing else is shown when I try to enter the password to unlock the screen: Nov 11 23:04:29 mobian gsd-usb-protect[2319]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files Nov 11 23:04:29 mobian gnome-shell[2141]: Bogus presentation time 0 travelled back in time, using current time. Are you using any GNOME Shell extensions? None. Downgrading gir1.2-mutter-7 and libmutter-7-0 to version 3.38.0-2 solved the issue. You reported this as a bug in version 3.38.0-2, but here you've said that version 3.38.0-2 *doesn't* have the bug. What version did you upgrade to that triggered this? (For now I've assumed 3.38.1-2.) Sorry, that was my error when reporting the bug. Version 3.38.0-2 DOES WORK, but upgrading to the current testing version (3.38-1.2) DOES NOT WORK. The system is a pinetab running mobian Mobian is a Debian derivative, and is not identical to Debian. If this is caused or triggered by a change made by Mobian, then changes in Debian will not fix it. It might be better to report bugs in Mobian to the Mobian developers. You are right. It could be some change in mobian that is incompatible with the upgrade of gir1.2-mutter-7 and libmutter-7-0. If you think that's the case, I'll report the bug to Mobian developers, as you suggest. smcv
Bug#974172: libmutter-7-0: Impossible to unlock the screen with wayland+gdm, keybard and mouse unresponsive
Package: libmutter-7-0 Version: 3.38.0-2 Severity: normal X-Debbugs-Cc: gal...@gmail.com Dear Maintainer, After upgrading the system, locking the screen of gnome-shell under wayland, made it impossible to unlock the screen. The keyboard and the mouse became completely unresponsive (Ctrl+Alt+F[1-6] did not work either). The only way to recover the system was by restarting gdm from a ssh session. Downgrading gir1.2-mutter-7 and libmutter-7-0 to version 3.38.0-2 solved the issue. The system is a pinetab running mobian -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.9-sunxi64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmutter-7-0 depends on: ii adwaita-icon-theme 3.38.0-1 ii gsettings-desktop-schemas 3.38.0-2 ii libatk1.0-02.36.0-2 ii libc6 2.31-4 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libcanberra0 0.30-7 ii libdrm22.4.102-1 ii libegl11.3.2-1 ii libfontconfig1 2.13.1-4.2 ii libfribidi01.0.8-2 ii libgbm120.1.9-1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libgl1 1.3.2-1 ii libglib2.0-0 2.66.2-1 ii libgnome-desktop-3-19 3.38.0-2 ii libgraphene-1.0-0 1.10.2-1 ii libgtk-3-0 3.24.23-1mobian2 ii libgudev-1.0-0 234-1 ii libice62:1.0.10-1 ii libinput10 1.16.2-1 ii libjson-glib-1.0-0 1.6.0-1 ii libpango-1.0-0 1.46.2-2 ii libpangocairo-1.0-01.46.2-2 ii libpangoft2-1.0-0 1.46.2-2 ii libpipewire-0.3-0 0.3.15-1 ii libsm6 2:1.2.3-1 ii libstartup-notification0 0.12-6 ii libsystemd0246.6-2 ii libudev1 246.6-2 ii libwacom2 1.5-1 ii libwayland-server0 1.18.0-2~exp1.1 ii libx11-6 2:1.6.12-1 ii libx11-xcb12:1.6.12-1 ii libxau61:1.0.8-1+b2 ii libxcb-randr0 1.14-2 ii libxcb-res01.14-2 ii libxcb11.14-2 ii libxcomposite1 1:0.4.5-1 ii libxcursor11:1.2.0-2 ii libxdamage11:1.1.5-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-2 ii libxi6 2:1.7.10-1 ii libxinerama1 2:1.1.4-2 ii libxkbcommon-x11-0 0.10.0-1 ii libxkbcommon0 0.10.0-1 ii libxkbfile11:1.1.0-1 ii libxrandr2 2:1.5.1-1 ii libxtst6 2:1.2.3-1 ii mutter-common 3.38.1-2 libmutter-7-0 recommends no packages. libmutter-7-0 suggests no packages. Versions of packages libmutter-7-0 is related to: ii libegl-mesa0 [libegl-vendor] 20.1.9-1 ii libgl1-mesa-dri 20.1.9-1 ii libglx-mesa0 [libglx-vendor] 20.1.9-1 -- no debconf information
