GNOME Bugzilla – Bug 775284
System freeze on lock screen under Wayland
Last modified: 2016-12-20 14:38:53 UTC
Created attachment 340945 [details] lspci -nn output Recently upgraded from Fedora 24 to 25, and my default session is using Wayland. Whenever I lock the screen (using Super+l) or allow the screen saver to engage, my monitors go into power-save mode and will never come back on. The system appears frozen, and a hard reboot is the only way to recover. Using the gear drop-down menu on the login screen to switch to a "Gnome on Xorg" session fixes the problem (lock screen wakes back up to password prompt as expected). Steps to reproduce: 1. Login to a Wayland Gnome session 2. Press Super+l to lock screen (or wait for screensaver to lock), monitors will enter power-save mode 3. System appears to be frozen, screens will not show password prompt 4. Hold the power button to do a hard reboot :-( I'm running dual nVidia cards, with three monitors. See attached lspci output. Could be related to #709727, but I can't tell if my screens are just blank or not on at all.
Created attachment 340946 [details] journal output up to a hard reboot `journalctl -a -b -1 > lastboot-journal.log`
Correction.. I'm running a single nVidia card with three outputs.
*** This bug has been marked as a duplicate of bug 774557 ***
(In reply to Rui Matos from comment #3) > > *** This bug has been marked as a duplicate of bug 774557 *** Hi Rui, I'm not confident that this bug is a duplicate of 774557. The bug I reported here is 100% reproducible by locking the session, as opposed to the random (once per day) freeze reported in #774557. It is interesting to note, however, that while using Fedora 24 (prior to my upgrade... I'm currently running Fedora 24), I experienced behavior similar to #7774557. My Spotify streaming music would continue to play, but I could not move the mouse, nor switch to a different virtual terminal to regain control. After upgrading to Fedora 25, those freezes have stopped, but I now experience the lock-screen problem reported here.
Ok, then I suspect yours is a driver specific issue. Can you reproduce it on different hardware?
I do not have other hardware to test with, unfortunately. I just reproduced this bug again after installing the latest Fedora 25 updates. I confirmed that the displays go into power-save mode and do not come back on at all (as indicated by their power LEDs flashing), no matter how much I move/click the mouse or press keys on the keyboard. Switching to a different virtual also does not work. The underlying system system to still be there, though, as the num-lock and caps-lock LEDs on the keyboard can still be toggled. I'm now running: gnome-desktop3-3.22.2-1.fc25.x86_64 gnome-shell-3.22.2-2.fc25.x86_64 gdm-3.22.1-1.fc25.x86_64 mesa-dri-drivers-12.0.4-2.fc25.x86_64 mesa-libwayland-egl-12.0.4-2.fc25.x86_64 mesa-libGL-12.0.4-2.fc25.x86_64 I'm happy to help with any other debugging steps that might help track this down.
I installed Fedora updates today and retested this bug. It seems to be fixed now. In case it helps, here's a few of the relevant packages that were upgraded: Removed: kernel.x86_64 4.8.8-300.fc25 Installed: kernel.x86_64 4.8.14-300.fc25 Updated: gnome-software.x86_64 3.22.4-2.fc25 gnome-terminal.x86_64 3.22.1-2.fc25 mutter.x86_64 3.22.2-3.fc25 mesa-dri-drivers.x86_64 13.0.2-2.fc25 mesa-filesystem.x86_64 13.0.2-2.fc25 mesa-libEGL.x86_64 13.0.2-2.fc25 mesa-libGL.x86_64 13.0.2-2.fc25 mesa-libGLES.x86_64 13.0.2-2.fc25 mesa-libgbm.x86_64 13.0.2-2.fc25 mesa-libglapi.x86_64 13.0.2-2.fc25 mesa-libwayland-egl.x86_64 13.0.2-2.fc25 mesa-libxatracker.x86_64 13.0.2-2.fc25 xorg-x11-drv-libinput.x86_64 0.23.0-1.fc25 xorg-x11-drv-wacom.x86_64 0.34.0-1.fc25 xorg-x11-server-Xorg.x86_64 1.19.0-2.fc25 xorg-x11-server-Xwayland.x86_64 1.19.0-2.fc25 xorg-x11-server-common.x86_64 1.19.0-2.fc25 xorg-x11-xinit.x86_64 1.3.4-13.fc25 There were no gdm updates in this batch.