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 339330 - Screensaver not throttled when session not displayed.
Screensaver not throttled when session not displayed.
Status: RESOLVED FIXED
Product: gnome-screensaver
Classification: Deprecated
Component: daemon
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
: 339331 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-04-21 17:45 UTC by Constantine Evans
Modified: 2006-07-12 23:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
backport to 2.14 (13.21 KB, patch)
2006-07-11 21:30 UTC, William Jon McCann 		none Details | Review
tiny tweak (13.69 KB, patch)
2006-07-11 21:53 UTC, William Jon McCann 		committed Details | Review

Description Constantine Evans 2006-04-21 17:45:09 UTC 
When gnome-screensaver is running on a session which is not being displayed (for example, when using fast user switch applet), the screensaver is not throttled. This wastes resources and is disruptive, since the screensaver is not being displayed, and the user is typically using the computer at the time.
Comment 1 Constantine Evans 2006-04-21 17:48:01 UTC 
*** Bug 339331 has been marked as a duplicate of this bug. ***
Comment 2 William Jon McCann 2006-04-21 19:26:49 UTC 
FUSA tries to throttle via gnome-screensaver-command when it switches users.  However, gnome-power-manager also tries to throttle and unthrottle when display power management changes.  So, I've fixed g-s to do reference counting and life cycle tracking of callers of Throttle.  This means that I've had to remove throttling from gnome-screensaver-command because it doesn't stay on the bus and FUSA shouldn't do it because it never unthrottles.

So, we're back to the age old problem of user switching: getting signals when the console changes.  We need a good solution for this.
Comment 3 William Jon McCann 2006-07-11 21:30:19 UTC 
Created attachment 68786 [details] [review]
backport to 2.14

Turns out there is a clean way to do this.  Here is a backport to 2.14 of the patch that I've committed to cvs head.

Can you test this?
Comment 4 William Jon McCann 2006-07-11 21:53:10 UTC 
Created attachment 68787 [details] [review]
tiny tweak