Screen saver running in sessions that are not in control of monitor
Bug #59400 reported by
Ken Pratt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-screensaver (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: gnome-screensaver
When two or more people are using the same computer via the "Switch User" method - hit the log out button then select "Switch User", it seems that the screen savers for those that are not currently in control of the sceen runs. This is a drain on CPU resources. The screen saver should only run under the account that currently controls the physical display.
This is the case on the 6.06 release.
Not really a bug with the screensaver - an unintended use exposes a problem.
Revision history for this message
| Micah Cowan (micahcowan) wrote | #1 |
Revision history for this message
| Micah Cowan (micahcowan) wrote | #2 |
| Changed in gnome-screensaver: | |
| importance: | Undecided → Low |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Lenbok (lenbok) wrote | #3 |
To post a comment you must log in.
Hm. I believe this is so that when the second user's session ends, the first user, when his X session is made the current one, will be required to log in. I agree that it would be beneficial to prevent the screensaver from actually using up CPU unless it's the currently visible one, but I think the fix for this is likely to be far from trivial.