Bug 369625

Summary:	org.kde.screensaver quit shuts down entire KDE session
Product:	[Plasma] plasmashell	Reporter:	Luke-Jr <luke-jr+kdebugs>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED NOT A BUG
Severity:	critical	CC:	kde, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.6.5
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Luke-Jr 2016-10-02 04:25:51 UTC

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

Comment 1 David Edmundson 2016-10-03 01:06:15 UTC

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

Comment 2 Luke-Jr 2016-10-03 02:10:17 UTC

Is there a way to have ksmserver restart without losing my session on upgrades?

Comment 3 Kai Uwe Broulik 2016-10-03 07:26:06 UTC

You can't. To unlock your session you could use loginctl unlock-session

Comment 4 Luke-Jr 2016-10-03 11:27:07 UTC

loginctl seems to be part of systemd which I don't want anywhere near my system...

Comment 5 Bhushan Shah 2016-10-03 11:45:13 UTC

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

Comment 6 Luke-Jr 2016-10-03 12:13:02 UTC

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)

Comment 7 Bhushan Shah 2016-10-03 12:20:00 UTC

(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.