On Tuesday, 12 September 2017 13:13:32 BST Michael Palimaka wrote: > On 09/12/2017 05:04 AM, Daniel Frey wrote: > > According to a comment in the bug, you can try to figure out which > > session it is (ck-list-sessions) and look for the X11 display property > > set. This will not work (or could be difficult) if you have several > > users using KDE at the same time and can't tell the sessions apart. > > > > Once you figure that out, remember the session name and: > > > > # su -c 'dbus-send --system --print-reply \ > > --dest="org.freedesktop.ConsoleKit" \ > > > > /org/freedesktop/ConsoleKit/<session name> \ > > > > org.freedesktop.ConsoleKit.Session.Unlock' > > If there a nice way to wrap this up in a script I'd be interesting in > shipping this for non-logind systems. > > Another option is sys-auth/elogind, which provides the logind interface > and tools (like loginctl) for non-systemd systems. This is what I've > been testing with OpenRC for some time. > > I read that ConsoleKit is also supporting the logind dbus interface now. > This would in theory make it easy to create a tool to unlock the > session, but I haven't had a chance to test it yet.
I think if Plasma shipped with screenlock unset as a default this problem would not exist for non-systemd set ups. I disabled Plasma's screenlock and after after some time of inactivity eventually DPMS kicks in and the monitors go into power saving mode. This negates for needing special scripts elogind or anything else KDE/Plasma never needed before now. Nevertheless, the suggestions for using dbus-send were useful for getting me out of a hole. Thanks again! :-) -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
