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 728939 - Automatic suspend (still) does not work if the screen is locked
Automatic suspend (still) does not work if the screen is locked
Status: RESOLVED DUPLICATE of bug 731241
Product: gnome-shell
Classification: Core
Component: general
3.12.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-04-25 09:29 UTC by Luis Henrique Mello
Modified: 2014-08-01 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gnome-settings-daemon --replace --debug > ~/gsd-debug.log 2>&1 (48.01 KB, text/plain)
2014-04-25 09:29 UTC, Luis Henrique Mello
Details

Description Luis Henrique Mello 2014-04-25 09:29:21 UTC
Created attachment 275117 [details]
 gnome-settings-daemon --replace --debug > ~/gsd-debug.log 2>&1

This was supposed to be fixed on 3.12 (see https://bugzilla.gnome.org/show_bug.cgi?id=712706) but on Arch Linux the problem persists.

I set the screen to lock after 1 minute and with dconf I set automatic suspend to 2 minutes idle - instead of suspending the machine, the lock screen shows up again.

A log is attached.
Comment 1 thido 2014-05-23 14:09:23 UTC
I confirm that the problem is still here with ubuntu-gnome 14.04 with gnome 3.12.
Automatic suspend work if the "black screen" is settled by the same as suspend (15 min for both) but not if the screen is shut down before.
It would be great to find a solution for this issue.
Comment 2 Florian Müllner 2014-05-23 14:44:47 UTC
(In reply to comment #1)
> I confirm that the problem is still here with ubuntu-gnome 14.04 with gnome
> 3.12.

Are you sure that gnome-settings-daemon is at version 3.12.x as well? Ubuntu has been infamous of shipping mismatching versions of that package in the past (e.g. 3.6 with GNOME 3.8 etc.) ...
Comment 3 thido 2014-05-23 16:54:10 UTC
Yes it's 3.12.1 version, installed with gnome staging ppa
Comment 4 Pasquale Marino 2014-07-30 12:24:30 UTC
I can definitely confirm this bug! 
I'm on Arch Linux on a desktop with GNOME and automatic suspend doesn't work!

gnome-shell 3.12.2-1
gnome-settings-daemon 3.12.2-1

This is what I tried:

1)
   * Blank screen = 5min
   * Lock screen = Off
   * Notification on lock screen = On
   * Automatic suspend = 7min (by dconf-editor)

2)
   * Blank screen = 5min
   * Lock screen = Off
   * Notification on lock screen = Off
   * Automatic suspend = 7min (by dconf-editor)

In both cases 1) and 2) auto suspend didn't work.
This is what happens: after 5 minutes the screen goes blank, but after some seconds before getting to 7 minutes (maybe 50-55 seconds after blank), the screen turns back on for a few seconds, then goes blank again, idle counter is reset and auto suspend is never triggered.


Then I tried:

3)
   * Blank screen = 5min
   * Lock screen = Off
   * Notification on lock screen = On
   * Automatic suspend = 5min (by dconf-editor)

In this case the screen never gets blank, a little before of 5 minutes a notification appears telling me that auto suspend is about to happen and after some more seconds my machine gets suspended correctly. When I turn it back on (by power key), I get no lock screen, I'm back directly in my desktop.


Last try:

4)
   * Blank screen = 5min
   * Lock screen = Off
   * Notification on lock screen = On
   * Automatic suspend = Off

In this last case after 5 minutes the screen goes blank and STAYS BLANK, it doesn't turn on for some seconds after blank (like case 1 and 2) and idle counter is not reset.


So it "SEEMS" to me that the problem has got something to do whit auto suspend after blank screen. In some way if the screen is blank, auto suspend notification (or something else) causes the idle time to be reset and the screen to get back on for a few seconds.

I hope I can help to fix this annoying bug.
Comment 5 Rui Matos 2014-08-01 14:03:09 UTC
This sounds like bug 731241. Should be fixed in the X server.

*** This bug has been marked as a duplicate of bug 731241 ***