Jamie Zawinski wrote:
My problem is that when I come back and want to unlock, the screen gets
unblanked _after_ I enter my password, which basically means I have
to enter
my password blindly.
If you're trying to say that the screen is still completely black
while xscreensaver has an (invisible but functioning) password prompt
up, then this must be a bug in your video driver. There's no way
xscreensaver could still be painting the screen black at that point;
the password dialog is rendered *on* the window that is used to black
the screen.
No, that's not what I am saying. I am using an external program
(radeontool) to shutdown the screen while xscreensaver is running (it
reduces the power consumption since the screen is shutdowned instead of
being running with a black display). The manpage of
xscreensaver-command, in the -watch section, gives an example of this: I
have 'radeontool light off' if BLANK or LOCK is received (it shutdowns
my screen), and 'radeontool light on' if UNBLANK is received (my screen
comes back).
Xscreensaver works fine. But, xscreensaver-command -watch does not do
what I'd like: it could report UNBLANK (or anything else) as soon as the
password prompt comes (so that my radeontool starts my screen and the
xscreensaver prompt is displayed), not after the password is entered.
Currently, we have:
1) I lock the screen
2) LOCK is received from xscreensaver-command -watch
3) I move the mouse of touch the keyboard
4) I enter the password
5) UNBLANK is received
I'd like to have something like:
1) I lock the screen
2) LOCK is received from xscreensaver-command -watch
3) I move the mouse of touch the keyboard
4) UNBLANK is received
5) I enter the password
6) UNLOCK is received
thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
