On Sun, 08 Mar 2015 11:46:54 -0300 Ben Armstrong
<sy...@sanctuary.nslug.ns.ca> wrote:
> Yep, that's all it took. But wow, what a big accident waiting to happen
> for unsuspecting users! Some time ago, I had disabled xscreensaver to
> keep my session as light as possible, and the session appeared to be
> getting locked by lightdm anyway, so I didn't think anything of it. It
> was not until lxlock failed to produce any visible result when I pressed
> the "Lock Screen" button that I went looking and found this issue, so I
> don't know how long it has been that my session was not actually being
> locked!
Indeed.
The whole procedure is broken by design. The dbus methods which
dm-tool/lightdm use
org.freedesktop.DisplayManager.{Session|Seat}.Lock()
org.freedesktop.login1.Session.Lock()
don't return any value to the caller.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
