[18879] in Athena Bugs
Re: xlock vs. xss on sgi 8.4
daemon@ATHENA.MIT.EDU (Robert A Basch)
Wed Mar 21 10:58:11 2001
Date: Wed, 21 Mar 2001 10:58:02 -0500
Message-Id: <200103211558.KAA20349@anhedonia.mit.edu>
From: Robert A Basch <rbasch@MIT.EDU>
To: John Hawkinson <jhawk@mit.edu>
CC: bugs@mit.edu
In-reply-to: "[18874] in Athena Bugs"
Thanks for the bug report.
I reproduced the problem, by configuring a locking screen saver via the
SGI desktop, which produced the following entry in panelsession:
/usr/bin/X11/xlock -mode blank -besaver & # SAVER_COMMAND:0.0 #
With both xlock and xss running, the display wedged after the idle
time elapsed.
There does not appear to be a good general way for xss to determine
that xlock is running. On SGI's, it does detect (and warn) when the
SGI screen saver extension cannot be initialized, suggesting that
another screen saver is already running, but it does not know that
the other saver also locks the screen.
On the brighter side, I built and tried the newer version of xss from
the source tree, and it looks like it might improve things, by detecting
a failure to grab the keyboard or mouse, and retrying later; it did not
wedge the display.
Bob
