gnome-shell freezes after resume then unlock

[Rocko]

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)

[Daniel van Vugt (vanvugt)]

Rocko,

Sorry to hear about this problem. However with a large number of open bugs with similar symptoms we can't pin down the exact cause of this one without more information.

If you can then please try logging into the machine remotely (e.g. via SSH), and run 'journalctl -f' before reproducing the bug. Do you see any log messages that are helpful? How about from 'dmesg'?

Also while logged in remotely, after reproducing the problem please check if the gnome-shell process is still running. And if so then please run 'kill -ABRT' on it to generate a crash file which you can later upload with 'ubuntu-bug' or 'apport-cli'.

[Rocko (rockorequin)]

Ok, I'll try that when it happens and I can get ssh access (I can't always trigger the freeze).

One thing that might be helpful is that every single time I unlock the screen (whether after resume or not), the UI _always_ freezes for a second or two, including the mouse pointer. It's as if gnome-shell is waiting for some event to occur or a condition to become true before it continues, and in some cases it ends up waiting forever.

[Rocko (rockorequin)]

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.

[Rocko (rockorequin)]

This is still an issue in Ubuntu 18.04.

[Andi (redplanet)]

Hi!

I've got the same problem on a debian unstable.

I solved it by resetting the desktop environment.
You may want to save your configuration first (i forgot it ;))
dconf dump
This is the command for the hard reset - use it with caution:
dconf reset -f /

Bug description:
I'm not sure what caused the bug. But one thing i did was creating a second user via gnome and deleting it a few days later.

The same problem also appeared always when i used the gnome shell search or application menu.

After a few seconds, the window decorators disappeared and then the session stopped. I got back to the gdm.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Rocko (rockorequin)]

It's still happening every now and again.

[Daniel van Vugt (vanvugt)]

OK. Please provide some/all of the information requested in comment #2.

I suggest the next steps are:

1. Apply the workaround from bug 994921 first.

2. Then next time the problem happens look in /var/crash for relevant crash files and if found then run: ubuntu-bug /var/crash/YOURFILE.crash

3. If there were no crash files then please run 'kill -ABRT <PID>' on the hung gnome-shell process. Then goto step 2.

4. Tell us here the IDs of any new bugs opened via 'ubuntu-bug'.

5. After the problem happens next time, please run these commands and send us the resulting files:
  dmesg > dmesg.txt
  journalctl -b > journal.txt

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Rocko (rockorequin)]

It keeps locking at inconvenient times when I can't get access to another PC, which is why I'm having trouble providing crash logs.

It was fine suspending/resuming for the last week and a half and then crashed this morning. The only difference was that I applied updates last night before I suspended it and that I moved the laptop from a house where it had been on the same network for the week and a half to a library where the laptop didn't know the WIFI.

[Daniel van Vugt (vanvugt)]

We can keep this discussion open indefinitely, but please don't set the bug to confirmed without first providing more information in reply to comments #2 and #9.

[Rocko (rockorequin)]

I finally managed to generate a crash file - see bug #1781647.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Gao Shichao (xgdgsc)]

I experience this everyday. I don' t know if it is related to my recent change of theme to Arc-Dark and icon to Papirus-Dark. I' m uploading the crash file to some disk because it is so huge (500MB).

[Gao Shichao (xgdgsc)]

https://mega.nz/#!bOw3yKhR here' s the crash file

[Gao Shichao (xgdgsc)]

https://mega.nz/#!bOw3yKhR!01YJQWaC4jNmh3R2OArqi9ZmHsoc7K3MAWvlz4JoWfE sorry, this is the direct link.

[Daniel van Vugt (vanvugt)]

Please don't send us crash files. Crash files should instead be reported by running:

  ubuntu-bug /path/to/your.crash

P.S. This bug is already closed.

[Gao Shichao (xgdgsc)]

But apport doesn' t show any progress bar. I wouldn' t know how long it would take to use that to upload the huge crash file.

[spi (spi-gmxpro)]

Is anybody else who is facing the freezing using autofs (or systemd's automount feature)?