Summary: | screensaver started when X session is not even active | ||
---|---|---|---|
Product: | kscreensaver | Reporter: | pesarif |
Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | l.lunak |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | kdebase/kdesktop/lock patch |
Description
pesarif
2002-03-27 12:08:26 UTC
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 |