[Portland] xdg-screensaver.in

[Bryce Harrington]

On Wed, May 10, 2006 at 03:14:51AM -0700, Bastian, Waldo wrote:
> I think it makes more sense to have an API in the X-server to "suspend"
> the screensaver for a defined amount of time rather than disable it
> entirely. That way you don't end up with a disabled screensaver when an
> application crashes, which would have a security impact.

The suspend function in xdg-screensaver restores the screensaver
regardless of whether the application crashes.  If the application
wishes, it can also restore the screensaver on its termination.

I tested this out a bit with terminating applications and am pretty
certain there is no problem, but if you see a common way that an app
crash could leave the screensaver disabled when using this script, tell
me and I'll take a look.  

Of course, it would be great if X had a built in suspend functionality,
but I could not find any mention of such a capability online.  And even
if it got it tomorrow, there'd be a lot of legacy X's around without
that capability, that Portland would need to support for at least a
couple years.

Bryce
 
> Waldo Bastian
> Linux Client Architect - Client Linux Foundation Technology
> Channel Platform Solutions Group
> Intel Corporation - http://www.intel.com/go/linux
> OSDL DTL Tech Board Chairman
> 
> >-----Original Message-----
> >From: portland-bounces at lists.freedesktop.org [mailto:portland-
> >bounces at lists.freedesktop.org] On Behalf Of Aaron J. Seigo
> >Sent: Tuesday, May 09, 2006 3:50 PM
> >To: portland at lists.freedesktop.org
> >Subject: Re: [Portland] xdg-screensaver.in
> >
> >On Tuesday 09 May 2006 16:02, Bryce Harrington wrote:
> >> Looking at the xset source code[2], it looks like we need an X
> routine
> >> like XActivateScreenSaver()[3] but that returns the current saver
> state
> >> instead of setting it.  Does XGetScreenSaver return this info in one
> of
> >> its args?
> >
> >apparently if the timeouts given by XGetScreenSaver are 0 then the
> >screensaver
> >is off. otherwise it's on.
> >
> >talking to one of the kde/x.org guys (frederik), he noted that while
> this
> >works it's pretty hacky and that at some point it needs to be fixed
> >properly
> >in x.org. they've recently added the ability to programmatically (and
> >safely)
> >block the screensaver w/out resorting to doing things like faking key
> >events,
> >but even that hasn't made it into an official release yet. xscreesaver
> is
> >still a bit of a mess =)
> >
> >hth.
> >
> >--
> >Aaron J. Seigo
> >GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
> >
> >Full time KDE developer sponsored by Trolltech
> (http://www.trolltech.com)
> _______________________________________________
> Portland mailing list
> Portland at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/portland