desktop-packages team mailing list archive

[Robert Ancell <robert.ancell@xxxxxxxxxxxxx>]

PAM_TTY has been set since 0.9.7.  PAM_XDISPLAY is not currently set.
XAUTHORITY is set later in the process, as it requires the home
directory to be mounted.  We could set it to a system XAUTHORITY earlier
then replace it with the user XAUTHORITY.

** Package changed: unity-greeter (Ubuntu) => lightdm (Ubuntu)

** Also affects: lightdm
   Importance: Undecided
       Status: New

** Summary changed:

- Missing PAM environment variables in unity-greeter
+ Does not set PAM_XDISPLAY and or XDISPLAY, XAUTHORITY variables

** Changed in: lightdm
       Status: New => Triaged

** Changed in: lightdm (Ubuntu)
       Status: New => Triaged

** Changed in: lightdm
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

-- 
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:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged

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