After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 724930 - System freezes after suspend session
System freezes after suspend session
Status: RESOLVED NOTGNOME
Product: gnome-shell
Classification: Core
Component: general
3.10.x
Other Linux
: Normal blocker
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-02-22 00:53 UTC by Cristian Aravena Romero
Modified: 2014-07-07 12:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cristian Aravena Romero 2014-02-22 00:53:44 UTC
Open bug in launchpad.net
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1262201

"After suspend the session the system freezes. This happens when I try to resume the
 session, in the login screen.

 To make it happen:

  1- Suspend the session from the user menu
  2- Resume the session
    (The system should freeze on the login screen)"
Comment 1 drago01 2014-02-23 11:56:01 UTC
I can't see how this is a gnome-shell bug. If the system freezes like that its most likely a driver / kernel bug.
Comment 2 Jazz 2014-07-06 16:33:48 UTC
I can confirm this behaviour on Arch running Gnome 3.12.2. This started approximately two days ago.

On Launchpad, another Arch user describes the same problem (posted today): https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1262201/comments/17

The users on Launchpad experience the error with Nvidia chipsets. I have an Intel HD chipset.
So I don't think it is a distro-only or driver-only bug.

I can provide log files if you tell me what you need.
Comment 3 Jazz 2014-07-07 12:10:20 UTC
After some testing, my problem is slightly different to the ones described in the link above:

This bug only happens with automatic suspend, NOT when doing manual (HW button or menu) suspend.


Steps to reproduce:

1) Run laptop on battery, have automatic suspend activated
2) Wait until the laptop suspends. (the notification "[...] will suspend soon due to inactivity" should appear right before)
3) Wake up the laptop after a few seconds -> login screen is frozen. 
4) "Rescue": switch to tty2 and sudo killall gdm or reboot from tty2. In both cases open programs are (obviously) killed and unsaved work is gone...


Please re-open this case.
If you need log files, tell me which ones and I will send them.