Related to this could also be the problem that capabilities gained via pam_cap.so are dropped when logging in via lightm. I haven't yet filed a seperate bug for this, and I think it won't be necessary if this is going to fix it. I'll see when this is changed.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/881466 Title: Run PAM code inside session process Status in Light Display Manager: Triaged Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Precise: Triaged Bug description: Currently PAM code is run inside the main lightdm daemon process. This means that buggy PAM modules can crash lightdm (see bug 829221). We should change the architecture to run the PAM code inside the session processes before launching the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/881466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
