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: #877766)
- Restructure session code so the PAM authentication is run in its
own process. (LP: #881466)
- Set PAM_XDISPLAY and PAM_XAUTHDATA pam items (LP: #862559)
- Don't send session stdout to .xsession-errors
- Fix Qt bindings crash when removing a user
-- Robert Ancell <[email protected]> Thu, 01 Mar 2012 20:54:07
+1100
** Changed in: lightdm (Ubuntu)
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/862559
Title:
Does not set PAM_XDISPLAY and or XDISPLAY, XAUTHORITY variables
Status in Light Display Manager:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Bug description:
If a PAM module with GUI interface for alternative authentication
methods (like fingerprint authentication) is used, this module needs
information about the xdisplay to connect to for showing up it's
widget. Therefore PAM has two enviroment variables to be setup by the
application before calling the "pam_authenticate" function. These
variables are PAM_XDISPLAY and PAM_TTY, both to be set to the current
display number (e.g. ":0"). Alternatively the environment variables
XDISPLAY and XAUTHORITY can be set, so the PAM module can get the
information by calling "getenv()".
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/862559/+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
