Make it so that greeter login unlocks automatically?

[alercah]

Some lockers automatically unlock when the greeter is used to log back into the same session. Is there a way to make xsecurelock do this as well?

[divVerent]

For now I have implemented SIGTERM handling; what is left is seeing what it takes to integrate with xss-lock or something else so we get told about the unlock event,

[divVerent]

XSecureLock should now properly respond to this code path of xss-lock:

static void
logind_session_on_signal_lock(GDBusProxy *proxy,                                 
                              gchar      *sender_name,                           
                              gchar      *signal_name,                           
                              GVariant   *parameters,                            
                              gpointer    user_data)                             
{                                                                                
    if (!g_strcmp0(signal_name, "Lock"))                                         
        start_child(&locker);                                                    
    else if (!g_strcmp0(signal_name, "Unlock"))                                  
        kill_child(&locker);                                                     
}                                                                                

I can trigger it like this:

loginctl lock-session; sleep 10; loginctl unlock-session

However, trying to log in from the greeter does not trigger this. Odd.

[divVerent]

xautolock has:

    if (unlockNow && !disabled)
    {
      (void) kill (lockerPid, SIGTERM);
    }

which is triggered by xautolock -unlocknow, without any other way for the greeter to do this.

[divVerent]

Lightdm runs:

        if (session->priv->login1_session_id)
            login1_service_unlock_session (login1_service_get_instance (), session->priv->login1_session_id);
        else if (session->priv->console_kit_cookie)
            ck_unlock_session (session->priv->console_kit_cookie);

This uses the org.freedesktop.login1 dbus service, and if that fails, the org.freedesktop.ConsoleKit service. xss-lock also listens to org.freedesktop.login1... so shouldn't this work? Why not?

[divVerent]

This is weird, as it now works for me - but only when xss-lock got started later manually, not when it came with my session. Weird. Maybe the initial connection to logind just failed?

[divVerent]

Also working for me on another system, using xss-lock as well. Closing as not reproducible.