(*** This bug was imported into bugs.kde.org ***) Package: kcmscreensaver Version: KDE 2.9.2 Severity: wishlist Installed from: Mandrake RPMs Compiler: Not Specified OS: Linux OS/Compiler notes: Not Specified Load up KDE then switch to a different VC (e.g. CTRL+ALT+F1). Return say 10 minutes later and the screen saver's running. What a waste of proccessing power (I have slow computer and this is noticeable)! The screensaver should only be activated if the current VC is in X. (Submitted via bugs.kde.org)
VisibilityNotify could help IIRC.
As far as I can see, that only covers widgets being covered/uncovered, so I'm not too sure how it could be used.
Created attachment 1462 [details] kdebase/kdesktop/lock patch But it works even for switching to another VT, somewhat surprisingly (DPMS doesn't trigger it though). Please test, this one might be nice to backport.
Subject: Re: screensaver started when X session is not even active Hi, On Wednesday 30 April 2003 11:24, Lubos Lunak wrote: > But it works even for switching to another VT, somewhat surprisingly (DPMS > doesn't trigger it though). Please test, this one might be nice to > backport. Absolutely superb! Thanks. I'll hopefully test sometime today. I was dubious about how this would work considering network transparency etc, but thinking about it, I actually can't see any problems.
Subject: kdebase/kdesktop/lock CVS commit by howells: Commit excellent patch by Lubos to fix #39864 "screensaver started when X session is not even active" To do next: stop screensaver when DPMS has blanked the screen. CCMAIL: 39864-done@bugs.kde.org M +46 -11 lockprocess.cc 1.19 M +7 -0 lockprocess.h 1.7