[Debian-eeepc-devel] Bug#499544: Bug#499544: Please add lock posibility for kde screensaver
dmn at debian.org
Sun Sep 21 10:06:07 UTC 2008
-=| Damyan Ivanov, Sun, Sep 21, 2008 at 12:35:10PM +0300 |=-
> -=| Darren Salt, Fri, Sep 19, 2008 at 09:32:25PM +0100 |=-
> > I demand that Artur R. Czechowski may or may not have written...
> > > Please support also KDE desktop when suspending. KDE can be locked via
> > > CLI using:
> > > dcop kdesktop KScreensaverIface lock
> > And xtrlock.
> Can you offer sample code that locks xtrlock?
OK, I've read the manual and it seems xtrlock is unlike the other
screen savers. it is no a daemon that needs to be activated in some
way, but a program that grabs the input until the user enters his
As such, it works independently from any screen saver and needs no
user configuration, other than starting it.
The current screen-saver actiation code just trries any screen saver
it knows of. If this scheme is extended to also try xtrlock, that
would mean that xtrlock will be used (in addition to any detected
screen saver) just after the user installed the xtrlock package.
This looks bad to me, as the fact a program is installed does not mean
it should be used. For example I installes xtrlock just to read its
manual, not actually lock my screen.
There are two solutions:
* add yet another configuration variable to
* make the functions.sh file a conffile by moving it under
/etc/eeepc-acpi-scripts and let the admin wishing to use xtrlock
modify the lock_x_screen function
My preference goes to the second solution. Comments welcome.
dam JabberID: dam at jabber.minus273.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/attachments/20080921/bbbc54af/attachment-0001.pgp
More information about the Debian-eeepc-devel