[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #52 from Luke-Jr --- I don't (and hope to never) use systemd... elogind is what I finally let Gentoo install. I also don't like/use any fancy session management. Just CLI login and startx. -- You are receiving this mail because: You are

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #51 from m1st0 --- (In reply to Luke-Jr from comment #50) > $ loginctl lock-session > Failed to issue method call: Is a directory > $ loginctl unlock-session > Failed to issue method call: Is a directory I tried to look up any obvious

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #50 from Luke-Jr --- $ loginctl lock-session Failed to issue method call: Is a directory $ loginctl unlock-session Failed to issue method call: Is a directory -- You are receiving this mail because: You are watching all bug changes.

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #49 from m1st0 --- Sorry, missed mentioning examples for your own session: loginctl lock-session; sleep 3 loginctl unlock-session Use as needed. -- You are receiving this mail because: You are watching all bug changes.

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #48 from m1st0 --- Simple enough now using loginctl as a privileged user for example: sudo loginctl lock-sessions; sleep 3 sudo loginctl unlock-sessions Therefore without specifically needing to call with sudo, you can easily

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 Luke-Jr changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #45 from Martin Gräßlin --- (In reply to Luke-Jr from comment #44) > Service 'org.freedesktop.login1' does not exist. As I said just above: you can write your own small tool which implements it. That's what we did in

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #44 from Luke-Jr --- Service 'org.freedesktop.login1' does not exist. -- You are receiving this mail because: You are watching all bug changes.

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #43 from Martin Gräßlin --- (In reply to Luke-Jr from comment #42) > Sigh, systemd and Consolekit are not dbus. see and that's the stupid discussion which you should stop to do. I just gave you a dbus command which will

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #42 from Luke-Jr --- Sigh, systemd and Consolekit are not dbus. -- You are receiving this mail because: You are watching all bug changes.

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #41 from Martin Gräßlin --- (In reply to Luke-Jr from comment #40) > > There is a way to unlock the lockscreen through dbus. > > Ok, I missed this point entirely. Sorry for the useless discussion. What is > the current

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #39 from Martin Gräßlin --- Stop the useless discussion. There is a way to unlock the lockscreen through dbus. There won't be another one added. -- You are receiving this mail because: You are watching all bug changes.

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #40 from Luke-Jr --- > There is a way to unlock the lockscreen through dbus. Ok, I missed this point entirely. Sorry for the useless discussion. What is the current way to do this? -- You are receiving this

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #37 from Martin Gräßlin --- Can we please stop that? We won't do the change you want. There is a good enough replacement with logind and consolekit. -- You are receiving this mail because: You are watching all bug

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #38 from Luke-Jr --- Stop what, exactly? Reporting regressions in KDE? Commenting on desirable behaviour? Using KDE at all? (I'm sure if enough users get told off, eventually there will be enough interest in a

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #36 from Luke-Jr --- An application executing with user privileges is considered equivalent to the user. That's the way *nix security is designed, and while I agree it could probably use some improvement, the

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #35 from Martin Gräßlin --- (In reply to Luke-Jr from comment #34) > Don't applications need user privileges to call dbus commands in the first > place? If they have dbus access, they can access anything else already,

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #34 from Luke-Jr --- Don't applications need user privileges to call dbus commands in the first place? If they have dbus access, they can access anything else already, or even ptrace ksmserver to shut it off the

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #33 from Martin Gräßlin --- (In reply to Luke-Jr from comment #32) > Could we just add a dbus Unlock method? No! That would allow any unprivileged application to unlock the lock screen. The lock screen is there to

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #32 from Luke-Jr --- Could we just add a dbus Unlock method? -- You are receiving this mail because: You are watching all bug changes.

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #31 from Martin Gräßlin --- (In reply to Luke-Jr from comment #30) > How do I unlock my screen in KDE 5 without systemd/logind ugliness? There is also support for consolekit2, though I don't know how to use that. --

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 Luke-Jr changed: What|Removed |Added CC|