** Changed in: lightdm
Status: Fix Committed = Fix Released
--
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
This bug was fixed in the package lightdm - 1.1.4-0ubuntu1
---
lightdm (1.1.4-0ubuntu1) precise; urgency=low
* New upstream release.
- Change session directory once user permissions are set so it works
on NFS filesystems that don't allow root to access files. (LP:
Fixed in 1.1.4
** Changed in: lightdm
Status: Triaged = Fix Committed
** Changed in: lightdm (Ubuntu Precise)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
** Branch linked: lp:~ubuntu-desktop/lightdm/ubuntu
--
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:
Also related to this, the way lightdm does PAM is problematic with
SystemD.
I'm starting lightdm as a service from SystemD but as soon as I login,
my session is killed.
From auth.log I can see that I did successfully login, but the session is
killed imidiatelly:
auth.log:Feb 23 23:43:04
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
Robert,
Wry's comment called my attention to this bug, and I can't help thinking of a
functionality aspect that I mentioned in an email message a few weeks ago;
please see the SetLanguage_call.txt attachment.
From my POV things would better happen in this order:
1. Lock up home if encrypted
7 matches
Mail list logo
