Public bug reported:
Binary package hint: gnome-screensaver
At some point, I just haven't figured when yet, g-s-s seems to be losing
track of user activity and doesn't issue SessionIdleChanged signals
anymore. Consequently gnome-power-manager doesn't change the DPMS
timeouts of X and they either stay as they were when g-p-m set them or
(worse) they stay zero all the time, which has the effect of not
blanking the displays anymore.
I ran both g-s-s and g-p-m (latest version as of Gutsy) with --debug and
--no-daemon for quite some time, plus dbus-monitor. The screensaver
timeout was set to 1 minute without activation when idle (even "blank
screen" eats 25% of CPU with Compiz here) and the display sleep timeout
in g-p-m was set to 2 minutes. I'm also running X with Compiz and
Twinview (nvidia's latest driver 100.14.23). The debug output of g-p-m
was useless in this case as it did output almost nothing.
First strange thing, g-s-s doesn't always issue
SessionPowerManagementIdleChanged signals, but that's another question.
Usually, g-s-s goes like this:
Idle notice signal detected: 1
Idle notice signal not handled: 1
in idle timer
Idle signal detected: 1
Setting session idle: 1
Checking for activation
Changing idle state: 1
and it issues a SessionIdleChanged(true) signal. Then g-p-m sets the
DPMS timeouts and displays eventually go to sleep. G-s-s sees that the
display is put to sleep and goes like that:
adding throttler from Power screensaver for reason 'Display DPMS activated'
on connection :1.73
Checking for throttle
throttler: Power screensaver for reason: Display DPMS activated
Changing throttle status: 1
Upon user activity, the displays turn back on, the DPMS timeouts are
reset to 0 and g-s-s goes like that:
Idle signal detected: 0
Setting session idle: 0
Checking for activation
Changing idle state: 0
and a few seconds later:
removing throttler from Power screensaver for reason 'Display DPMS activated'
on connection :1.73
Checking for throttle
Changing throttle status: 0
Now after some time, probably due to some specific activity that I've
not been able to determine yet, the behavior changes and it goes like
this:
Idle notice signal detected: 1
Idle notice signal not handled: 1
in idle timer
Idle signal detected: 1
Setting session idle: 1
Trying to set idle state when already idle
Idle changed signal not handled: 1
Idle signal was not handled, restarting watcher
turning watcher: OFF
Stopping idle watcher
turning watcher: ON
Starting idle watcher
and no SessionIdleChanged is issued anymore.
There are probably other exact behaviors, depending on the state that
DPMS was left (active or zero), but I don't know really how to reproduce
it. If you need more debug info I have kept all the debug logs of g-s-s
and dbus-monitor.
** Affects: gnome-screensaver (Ubuntu)
Importance: Undecided
Status: New
--
Looses track of user activity
https://bugs.launchpad.net/bugs/156620
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
