> pam_gnome_keyring needs to be in the pam stack for "systemd-shared" of > course.
pam_gnome_keyring needs authinfo to unlock login keychain. Will that be passed to new systemd instance? > Which environment would that be? When systemd fully runs session, than that will be full profile environment + environment setted by login manager. For example, DM should setup DISPLAY variable. > Can you elaborate? Where exactly does it hang? Some kind of debugging environment should be setted up before that. With shared user instance [email protected] hangs alot. Sometimes session scopes rests in timeouts, when user session terminated without systemctl --user exit. Looks like logind/pam_systemd doesn't kill something. I have some units in user session with KillMode=process. Maybe that matters _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
