Since my screensaver-unlock script from KDE 4 no longer works, I was trying to find a new way to implement it for Plasma... Sadly, the most obvious way just killed my entire KDE session. :( qdbus org.kde.screensaver /MainApplication quit This is very unexpected and bad behaviour. Reproducible: Always
That's correct behaviour, you just told ksmserver to quit. Paths on a DBus object are not unique per registration, so this is identical to qdbus org.kde.ksmserver /MainApplication quit
Is there a way to have ksmserver restart without losing my session on upgrades?
You can't. To unlock your session you could use loginctl unlock-session
loginctl seems to be part of systemd which I don't want anywhere near my system...
On Mon, Oct 03, 2016 at 11:27:07AM +0000, Luke-Jr via KDE Bugzilla wrote: > loginctl seems to be part of systemd which I don't want anywhere near my > system... Are you running consolekit based session? if so, please see following comment. https://bugs.kde.org/show_bug.cgi?id=360489#c3
I might be (but wish I wasn't - if I am, it is only because KDE forced it on me...) The commands in that link don't work, though: # ck-list-sessions (ck-list-sessions:26255): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Error calling StartServiceByName for org.freedesktop.ConsoleKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the setuid helper is not correct Segmentation fault (core dumped)
(In reply to Luke-Jr from comment #6) > I might be (but wish I wasn't - if I am, it is only because KDE forced it on > me...) If you have this opinion, I am out from this discussion.