Gnome-shell hang on wake from suspend

[KML]

Gnome-shell sometimes hangs when i wake it from suspend (by opening the lid on my Dell E6520 laptop).

I open the lid, and it just shows the lock-screen background, and everything seems frozen. I am able to switch tty and move the mouse, but no upwards arrow animation (like there normally is when it is locked), and you cannot get to the password prompt.

This mostly happends when i open the lid of the laptop after having taken it out of a docking station. My normal procedure for taking it out of the docking station is:

1. When it is in the dock (using 2 external monitors, and laptop-lid closed) i lock Ubuntu with CTRL-ALT-L.
2. I undock the laptop.
3. I open the screen, and see that the screen turns on. After a few seconds i shut it again. As it is now undocked my power settings let it go into suspend nicely.
4. Later when i open the lid (might be hours later) it hangs like explained above.

I do this every day, and 1/4 times it has done this now. I don't think it is exclusively in this situation that i have experienced this bug, but this has now happened so many times this way, so it might have something to do with it ?

Tell me if you need further info, as i will gladly provide it.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri May 23 22:40:48 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell.calendar' b'show-weekdate' b'true'
 b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2014-05-16 (6 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8fea66f853: mov (%r15),%esi
 PC (0x7f8fea66f853) ok
 source "(%r15)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 real_assign_crtcs (assignment=assignment@entry=0x7fff9bba85c0, output_num=output_num@entry=0) at core/monitor-config.c:1714
 meta_monitor_config_assign_crtcs (outputs=0x6217180, crtcs=0x39482e0, manager=0x69a2a0, config=0x804140) at core/monitor-config.c:1805
 apply_configuration (self=0x8418c0, config=0x804140, manager=0x69a2a0, stored=0) at core/monitor-config.c:864
 _g_closure_invoke_va (closure=0x1e64370, return_value=0x0, instance=0x1d9e8e0, args=0x7fff9bba8828, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:831
 g_signal_emit_valist (instance=0x1d9e8e0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff9bba8828) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3215

[Jason Eisner (jason-cs)]

I have had related behavior for a long time -- at least the 3 few editions of Linux Mint.
I am using MATE (the fork of Gnome 2).

Here is the problem, which is reproducible:

Sometimes I use a dual monitor setup. I've learned not to suspend (usually by closing the laptop lid) while the second monitor is active. Because then I am hosed: when I try to resume, the machine is frozen and needs to be rebooted. (I can't even do Ctrl-Alt-F1 to get a terminal login prompt. I think I do have mouse movement, like the original poster, but would have to check.)

Let me know if I can help with more information.

[Shay (sperlst)]

@Jason,
I can confirm that I face the same issue as you do with 3 monitors and a docking station.
I am using ubuntu 14.04 with gnome3 on DELL LATITUDE E6540

I need to kill gnome shell as soon as any of the menus is popping up, this is happening after I undock, suspend and then resume.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017

https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

[Launchpad Janitor (janitor)]

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