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 332974 - Totem power manager integration
Totem power manager integration
Status: RESOLVED NOTABUG
Product: totem
Classification: Core
Component: general
1.3.x
Other All
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
: 339376 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-01 10:22 UTC by Christian Fredrik Kalager Schaller
Modified: 2006-04-23 13:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Christian Fredrik Kalager Schaller 2006-03-01 10:22:45 UTC 
Please describe the problem:
Totem now handles keeping the screensaver in check nicely. What I do notice
however using Totem on my laptop is that I am having a similar irritation with
the laptop hardware power/screensaving features. After a while the laptop turns
of the monitor unless I press a key. Would be nice if Totem could use
gnome-power -manager to keep my laptop from going into rest mode while playing a
movie.

Steps to reproduce:



Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Bastien Nocera 2006-03-01 23:51:28 UTC 
Totem shouldn't need integration with g-p-m, it already tells gnome-screensaver not to switch itself on. Jon?
Comment 2 William Jon McCann 2006-03-02 04:31:34 UTC 
Correct.  g-p-m shouldn't set the DPMS timeouts unless it gets a session-idle signal from gnome-screensaver.  The session-idle signal should be inhibited by totem.  You might try logging out and back in and using dbus-monitor --session to  see if g-s or g-p-m are doing anything.  However, it might be some other application taking liberties with xset dpms.
Comment 3 Bastien Nocera 2006-04-23 13:08:11 UTC 
*** Bug 339376 has been marked as a duplicate of this bug. ***