Hi, in my desktop using KDE I would like to use xscreensaver to lock the screen instead of the standard (I don’t know how to know its name) to lock the screen, how can I do it?
I am not sure you can do something with this, but the process running here is
/usr/lib64/libexec/kscreenlocker_greet --immediateLock --graceTime 5000 --ksldfd 53
man xscreensaver
and take a look at the “INSTALLING XSCREENSAVER ON KDE” section. (Manual’s capitalisation, not mine…)
Hmm… Having just fully read that myself, rather than the cursory glance I gave it earlier, it appears rather outdated, sorry about that.
Found this: https://man.archlinux.org/man/xscreensaver.1#INSTALLING_XSCREENSAVER_ON_KDE
Which seems far more up to date.
maaaaanythanks, it seems to works,
about point 3: Launch XScreenSaver at login.
I cannot find the file /usr/share/applications/xscreensaver.desktop, there is /usr/share/applications/xscreensaver.properties.desktop,
so I used systemsettings>startup and shutdown>autostart to insert there xscreensaver, I will try if it works when I’ll have access to my desktop.
as the point 4: Make KDE’s “Lock” icon use XScreenSaver.it seems that I have to repeat this point every update, is there a way to solve this?
about point 5: Turn off KDE’s built-in locking on suspend, even harder.
I didnt operate this as it is not a laptop
Yes… I’ve just looked at the file list for the xscreensaver package and there is no “xscreensaver.desktop”, perhaps that’s specific to the Arch package. Creating it via “System Settings → …” is as good a way to go. In the (xscreensaver) man pages it does show what the contents of the “xscreensaver.desktop” should be, although as I later noted, those pages seem somewhat out of date.
as the point 4: Make KDE’s “Lock” icon use XScreenSaver.it seems that I have to repeat this point every update, is there a way to solve this?
My first thought would be to create a bash script to carry out those modifications, that could then be manually ran after any update that zapped your xsceensaver setup.
Alternatively you could probably incorporate that as part of xscreensaver’s autostart. Instead of autostarting xscreensaver directly as a program, use a script which carries out the replacement of “kscreenlocker_greet” and then executes xscreensaver. OK, the bulk of the time the replacement of “kscreenlocker_greet” would be redundant, but it means you wouldn’t have to manually run the script after any “offending” update…