GNOME Lock support - Githubissues

samcday commented 4 months ago

GNOME warns on session launch that locking isn't supported. Why tho?

Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable

samcday commented 4 months ago

This could be a fairly deep rabbit hole. I think GDM is fundamentally different to greetd in that it stays resident (and can be reached on its original VT) and does extra DBus stuff.

samcday commented 1 month ago

I'm guessing that gnome-session wants to be able to just call org.freedesktop.login1.Session.Lock, which is implemented by systemd-logind.

Things I'm not quite sure of:

Whether gnome-session is indeed calling that DBus method - I should trace the source and be sure otherwise all further line of inquiry here is pointless.
How gnome-session determines that screen locking isn't available.
What systemd-logind expects to see to signal that locking is available.

Some cursory scanning of GDM sources suggest to me that it's interacting with org.freedesktop.login1 interfaces in all sorts of interesting ways.

I also wonder if GNOME is simply looking for the existence of the org.gnome.displayManager bus to decide if locking is enabled. If so, a satisfying conclusion to this issue would require shimming the necessary bits of that API..?

samcday commented 5 days ago

I'm moving this to the 0.43 milestone. The main priority is ensuring phrog is suitable for mobile greeter duties as a direct successor to phog, and in that case 9 times out of 10 users will be launching a Phosh session.

samcday / phrog

GNOME Lock support #5