You are not logged in.
Hello.
Everything is in the title. As far as I searched, I found that apparently KDE Plasma (DE that I'm using) forces itself to use its own screensaver engine... even thought it doesn't seem very active: not mentioned in KDE system settings, is never launched.. That's really problematic to force its use when we could just use XScreenSaver.
When I relaunch the daemon via xscreensaver-settings, I got this output:
xscreensaver-systemd: 09:21:02: connection failed: "org.freedesktop.ScreenSaver" in use by pid 18786 (/usr/bin/ksmserver)
xscreensaver: 09:21:02: pid 24564: xscreensaver-systemd exited unexpectedly with status 1I also noticed I don't got the ./xscreensaver folder mentioned in the Arch wiki page.
Probably something related to ksmserver but I don't know how to solve it.
Thanks in advance.
Last edited by byjove01 (2021-08-19 18:50:28)
Offline
Online
I followed this guide, but I'm blocked at both final sub-chapters of the KDE installation part.
I can't find "kdesktop_lock" or its name variants, and there's no startkde script ; I also tried to substitute the ksmserver executable but when I tested it by myself it sent me an error, so I did go back to do not break something such important.
Offline
% pacman -F kscreenlocker_greet
extra/kscreenlocker 5.21.5-1 (plasma)
usr/lib/kscreenlocker_greettried to substitute the ksmserver executable but when I tested it by myself it sent me an error
Online
Well it apparently started to work, before I do everything.. guess an update repaired it. Solved.
Offline