gnome-shell froze just again after entering my password when I was running gnome-shell in an X session, and with X running the cursor does not freeze and I can use CTRL-ALT-F1 to switch back to the gdm login screen. I was able to log into another gnome-shell a different user; unfortunately, before I was able to run those commands in comment #2, I tried enabling dash-to-dock from gnome-tweak-tool, and this totally froze the Wayland session and I had to hard reboot the laptop since I didn't have access to another PC to get a ssh session.
I don't know if it is relevant, but loginctl reported this for the locked session: IdleHint=yes IdleSinceHint=1513219211113789 IdleSinceHintMonotonic=80125362795 LockedHint=yes If I try the same thing with two user sessions now after rebooting, IdleHint and LockedHint are both 'no' for both the screen-locked session and the current session. (Incidentally, gnome-shell no longer runs for my other user now that I have tried to enable dash-to-dock - I had to run a unity session. Perhaps Ubuntu should have waited for gnome-shell to become more stable before switching to it?) When a Wayland session freezes, CTRL-ALT-DEL no longer works. Is this something that can be configured or fixed? It is quite ridiculous that gnome-shell should be able to completely lock up the PC - surely only critical kernel faults should be able to do that. -- 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/1730540 Title: gnome-shell freezes after resume then unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: Often after resuming and then entering my password to unlock gnome- shell, when I press the enter key gnome-shell immediately freezes. The lock screen is still displayed, the mouse no longer responds, and the keys no longer respond (I can't even get a tty console with CTRL-ALT- Fn key). I have to perform a hard reset at this point because gnome- shell remains frozen even after leaving the PC alone for 15 minutes. I haven't been able to find any crash files or error logs. It seems that this freeze is much more likely to occur if I have changed location between suspending and resuming and am therefore connecting to a different wifi router. Once, however, it happened at home on the same router and I was able to log in via ssh from another machine (so only gnome-shell was frozen, not the kernel). However, I couldn't see any messages or reason that gnome-shell had crashed, so all I could do was reboot (any hints as to what I should try at this stage are welcome). Bug #1709994 looks similar but in that case a) the user is using Xorg, not Wayland, b) he also gets past the lock screen, and c) gnome-shell eventually restarts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.14.0-rc8-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 08:46:43 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-16 (82 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
