gnome-shell crashes often on unlock / resume from suspend

Bug #1709994 reported by hackel
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

It happens very frequently that, after resuming from suspend, as soon as I enter my password into GDM, gnome-shell crashes. I initially see my windows appear for a moment (with titlebars, etc.), then gnome-shell crashes, the titlebars disappear, and I am unable to do interact with any windows. Eventually gnome-shell restarts itself and the titlebars and functionality are restored.

This doesn't happen 100% of the time, and I have not been able to find any correlation. In my syslog, I see lines like:

Aug 10 14:30:49 hermes org.gnome.Shell.desktop[5325]: Window manager warning: Failed to set power save mode for output VGA-1: Permission denied
Aug 10 14:30:49 hermes org.gnome.Shell.desktop[5325]: Window manager warning: Failed to set power save mode for output eDP-1: Permission denied
Aug 10 14:30:58 hermes gnome-session[6503]: gnome-session-binary[6503]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Aug 10 14:30:58 hermes gnome-session-binary[6503]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6

This is on Ubuntu 17.04, gnome-shell 3.24.2-0ubuntu0.1, under Xorg with Intel HD 4600 graphics. I experience the same crashes under Wayland, making it *completely* unusable. At least under X I can still recover my session.

This is particularly annoying because whenever gnome-shell dies, it triggers a separate issue that kills all active Firefox content processes, requiring me to restart Firefox as well.

If there's a way to get some better debugging info for this, please let me know.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If just the titlebars disappear then that means you have indeed lost the window manager. A basic image remains on screen because Xorg is still running...

Please have a look in /var/crash for *.crash files. And then run ubuntu-bug on each:

  ubuntu-bug /path/to/your.crash

That should create a new bug with traceable details about the crash(es). We can't really do anything in this bug without such details.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
hackel (hackel) wrote :

Aha, I was wondering why appport/woopsie wasn't activating for these crashes. I did find one crash file there from yesterday, even though I just experienced this issue a few minutes ago when I logged in. I submitted the report, but I have no idea where it went or how to link it to this issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Stefan (stebp-vn) wrote :

Having the exact same problem.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Stefan, please open a new bug for yourself. There are many root causes of such crashes and it would be wrong to assume you have the exact same bug based on the short title of this bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.