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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730540 Title: gnome-shell freezes after resume then unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
