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 661006 - 3.2.0: playing a movie no longer inhibits screensaver
3.2.0: playing a movie no longer inhibits screensaver
Status: RESOLVED DUPLICATE of bug 660482
Product: gnome-settings-daemon
Classification: Core
Component: power
3.1.x
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-05 18:13 UTC by Dominique Leuenberger
Modified: 2011-12-09 12:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Cosimo's logs (116.54 KB, text/plain)
2011-10-20 08:15 UTC, Bastien Nocera
Details

Description Dominique Leuenberger 2011-10-05 18:13:01 UTC
While playing a movie on totem 3.2.0 (on a fully updates gnome stack), the screensaver is no longer inhibited.

dbus-monitor does show messages passing when pressing 'play' and 'stop', so it might be an error between gnome-session and totem dbus API.

### dbus-monitor log ### PLAY 

signal sender=org.freedesktop.DBus -> dest=(null destination) serial=64 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string "org.freedesktop.ReserveDevice1.Audio0"
   string ""
   string ":1.15"
method call sender=:1.15 -> dest=org.freedesktop.DBus serial=44 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RequestName
   string "org.freedesktop.ReserveDevice1.Audio0"
   uint32 5
method call sender=:1.142 -> dest=:1.0 serial=74 path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; member=Inhibit
   string "Totem Movie Player"
   uint32 54525963
   string "Playing a movie"
   uint32 8
signal sender=:1.0 -> dest=(null destination) serial=165 path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; member=InhibitorAdded
   object path "/org/gnome/SessionManager/Inhibitor10"
method return sender=:1.0 -> dest=:1.142 reply_serial=74
   uint32 2054379884

### end dbus-monitor ###
method call sender=:1.142 -> dest=:1.0 serial=77 path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; member=Uninhibit
   uint32 2054379884
signal sender=:1.0 -> dest=(null destination) serial=167 path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; member=InhibitorRemoved
   object path "/org/gnome/SessionManager/Inhibitor10"
method return sender=:1.0 -> dest=:1.142 reply_serial=77
### dbus monitor log ### PAUSE

### end dbus-monitor ###
Comment 1 Bastien Nocera 2011-10-20 08:13:52 UTC
I've found that gnome-session works correctly, and from Cosimo's logs, it seems that the power plugin in gnome-settings-daemon also works correctly.

What seems to be broken is that something doesn't notice that the session isn't idle and DPMS kicks in. There's no fade when the screen blanks, then turns off.

$ gdbus monitor --session --dest org.gnome.SessionManager 
Monitoring signals from all objects owned by org.gnome.SessionManager
The name org.gnome.SessionManager is owned by :1.24

/org/gnome/SessionManager: org.gnome.SessionManager.ClientAdded (objectpath '/org/gnome/SessionManager/Client36',)
/org/gnome/SessionManager: org.gnome.SessionManager.InhibitorAdded (objectpath '/org/gnome/SessionManager/Inhibitor12',)
/org/gnome/SessionManager: org.gnome.SessionManager.ClientRemoved (objectpath '/org/gnome/SessionManager/Client36',)
/org/gnome/SessionManager: org.gnome.SessionManager.InhibitorRemoved (objectpath '/org/gnome/SessionManager/Inhibitor12',)
Comment 2 Bastien Nocera 2011-10-20 08:15:14 UTC
Created attachment 199504 [details]
Cosimo's logs
Comment 3 Richard Hughes 2011-10-20 08:19:27 UTC
So, this sounds a lot like #660482 given that the screen doesn't dim and goes
straight to dpms off. You can verify by doing "xset -q" and checking that the
DPMS timeouts should all zero. Could you retry with the recently released
gnome-desktop 3.2.1 installed, after logging out and logging back in. Thanks.
Comment 4 Sebastian Pölsterl 2011-10-22 13:34:48 UTC
With 3.2.1 it works as expected. However, when configuring Totem to only deactivate the screensaver when playing video, the screensaver will NOT be activated when playing music only. Accordingly, Totem should not disable the screensaver when playing music.
Comment 5 Reda Lazri 2011-12-09 08:05:24 UTC
Any news on this bug? It is still a problem with NVIDIA and its proprietary drivers. I have to add DPMS "OFF" to xorg.conf to make gnome-screensaver appear correctly, but it stays there, the screen doesn't turn off after 10mn.
Comment 6 Bastien Nocera 2011-12-09 11:45:25 UTC
(In reply to comment #4)
> With 3.2.1 it works as expected. However, when configuring Totem to only
> deactivate the screensaver when playing video, the screensaver will NOT be
> activated when playing music only. Accordingly, Totem should not disable the
> screensaver when playing music.

That's a separate bug to file.

(In reply to comment #5)
> Any news on this bug? It is still a problem with NVIDIA and its proprietary
> drivers. I have to add DPMS "OFF" to xorg.conf to make gnome-screensaver appear
> correctly, but it stays there, the screen doesn't turn off after 10mn.

It's fixed with the newest gnome-desktop. If your distribution does not ship it, I suggest telling them.

*** This bug has been marked as a duplicate of bug 660482 ***
Comment 7 Reda Lazri 2011-12-09 12:07:31 UTC
@Bastien Nocera

What version? I'm on Arch with GNOME 3.2.1, and I still have that!
Comment 8 Bastien Nocera 2011-12-09 12:10:06 UTC
(In reply to comment #7)
> @Bastien Nocera
> 
> What version? I'm on Arch with GNOME 3.2.1, and I still have that!

gnome-desktop-3.2.1:
http://ftp.acc.umu.se/pub/GNOME/sources/gnome-desktop/3.2/gnome-desktop-3.2.1.news
Comment 9 Reda Lazri 2011-12-09 12:20:35 UTC
Yes, I've seen the bug report and the changelog before, and I have the latest
version. It is not fixed here, sorry.
Comment 10 Bastien Nocera 2011-12-09 12:22:31 UTC
(In reply to comment #9)
> Yes, I've seen the bug report and the changelog before, and I have the latest
> version. It is not fixed here, sorry.

Then file a new bug, because the original bug is fixed. And include a D-Bus monitor log as well, like the original reporter.