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