no, I intend to keep it in common-session, after discussion with upstream and Steve Langasek. Putting it into "login" and "gdm" would actually have been my first choice, but we can't auto-configure pam-ck-connector in those. Also, the PAM configuration framework Steve was writing only supports the non-conffiles for good reason.
I think we should just fix pam-ck-connector to not create a CK session for "those" PAM sessions. This might be "system user", or "no associated terminal", I'm not quite sure yet.
James,
no, I intend to keep it in common-session, after discussion with upstream and Steve Langasek. Putting it into "login" and "gdm" would actually have been my first choice, but we can't auto-configure pam-ck-connector in those. Also, the PAM configuration framework Steve was writing only supports the non-conffiles for good reason.
I think we should just fix pam-ck-connector to not create a CK session for "those" PAM sessions. This might be "system user", or "no associated terminal", I'm not quite sure yet.