Jamie Zawinski <[EMAIL PROTECTED]>:
> > You cannot just run "xscreensaver-command -lock" that is not how KDE
> > Screensaver work.
>
> Please explain. Because that's *exactly* what they should be doing.
>
The KDE Screensaver has it's own password dialog, and this will conflict
with xscreensaver's one. The kdesktop_lock Program requires the screensaver
to run on the root window and will grab the keyboard and mouse, it calls
the *.kss with "-root" and not with "-lock". I only have looked at
at my system and that was what happens. If you apply the patch, the
hack will run in KDE's root window, and on mouse
or keyboard activity KDE's password dialog will come up and kill this root
window and the screensaver hack.
I know that my patch is evil, you probably know a better way to get
the configured hack out of ~/.xscreensaver :-)
cheers,
Peter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
