xscreensaver to use CPU, even if not current VT (New User Login)
Bug #21705 reported by
Paul Sladen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xscreensaver (Debian) |
New
|
Unknown
|
|||
xscreensaver (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
For fast-user switching, multiple X sessions are started on multiple virtual
terminals, but non-visible screensavers are still left running.
If one X login is being used (for example on vt7) and another is in the
background (eg. on vt9) then xscreensaver will continue to run unabated on the
background X server, in turn using up 50%-100% of the CPU.
xscreensaver can be put into 'suspend' mode and this should to done (perhaps
polling?) if the vt of the X session is not the currently visible vt.
Changed in xscreensaver: | |
status: | Unknown → New |
Changed in xscreensaver (Ubuntu): | |
assignee: | Oliver Grawert (ogra) → nobody |
To post a comment you must log in.
On Jul 10, 2005, at 10:57 AM, Michael Shields wrote:
> However, this leaves a
> screensaver running on the old display, now hidden but likely
> consuming
> a significant amount of CPU.
Do you have evidence that this CPU usage is a problem? Because it www.jwz. org/xscreensave r/faq.html# suspend
shouldn't be:
http://
> It would be helpful if starting a new command -throttle" had been run.
> session also set the old one to a blank screen instead of a graphics
> hack, as if "xscreensaver-
Not a bad idea, I suppose, but the more general solution would be to
throttle while (and only while) the VT that the X server is running
on is not the selected one. You want the screen saver to un-throttle
when the user switches back.
However, I don't know how to tell A) which VT X is on; B) whether it
is the front; or C) when it changes.
-- www.jwz. org/
<email address hidden> http:// www.dnalounge. com/
http:// jwz.livejournal .com/
Jamie Zawinski <email address hidden> http://