FS#31797 - [gnome-settings-daemon] Display sleep broken

Attached to Project: Arch Linux
Opened by Zachary Dovel (zakkudo) - Wednesday, 03 October 2012, 23:33 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 10 November 2012, 01:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



About a month or so ago extra/gnome-settings-daemon 3.4.2-1 started inhibiting the monitor from going to sleep on my system. I did some testing to narrow down what the problem could possibly be.

1. In twm with sleep set in the xorg.conf file works
2. If the gnome3 session is started without gnome-settings-daemon-3.4.2-1 and it is set in xorg.conf, sleep works
3. I have removed my .config directory to make sure I didn't have any odd settings.
4. The gnome-control-center settings will only backen the screen at the set time instead of sleeping the display
5. With gdm display sleep works correctly.
6. It does not work with "exec ck-launch-session gnome-session" or exec "ck-launch-session dbus-launch gnome-session"
7. I have not texted with 3.6.x yet

Additional info:
* package version(s)
* config and/or log files etc.

Steps to reproduce:
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Saturday, 10 November 2012, 01:46 GMT
Reason for closing:  Fixed
Comment by Zachary Dovel (zakkudo) - Thursday, 04 October 2012, 22:21 GMT
It looks like 31801 posted today covers the same topic but in more detail. I'm double checking on my side if I stop using systemd.
Comment by Zachary Dovel (zakkudo) - Thursday, 04 October 2012, 23:50 GMT
Yeah, switching from systemd back to sysvinit fixes this. It is definitely related.
Comment by Jan de Groot (JGC) - Friday, 09 November 2012, 14:42 GMT
  • Field changed: Status (Assigned → Waiting on Response)
Does the current gnome-settings-daemon version fix your bug?
Comment by Zachary Dovel (zakkudo) - Friday, 09 November 2012, 23:46 GMT
Yeah. This bug is fine now.