or even better:
while "$ xscreensaver-command -exit" fails (indicating screensaver active):
sleep 5 seconds
perform pam and xscreensaver installation
restart xscreensaver daemon
which eliminates any need for user intervention.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
the previous suggestion also seems like it would work pretty well.
some python-like pseudo code:
while "$ xscreensaver-command -exit" fails (indicating screensaver active):
present dialog indicating that an active xscreensaver was detected
wait for user to unlock screen and respond to di
if a sufficiently detailed note about this (and a recommendation to
disable the screensaver) is added to the release notes, then i believe
that this bug can be closed. btw, where can i review the release
notes at?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". T
Package: xscreensaver
Version: 5.05-3
Severity: grave
i just tested the etch -> lenny transition on two of my systems, and
xscreensaver ended up locking me out of both of them.
version 4.24 of the xscreensaver daemon was running when i started the
upgrade. i went off to work on some other thin
4 matches
Mail list logo
