[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring

[Bryan Quigley]

** Patch removed: "samba_3.6.6-3ubuntu6.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+attachment/3732522/+files/samba_3.6.6-3ubuntu6.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1003296

Title:
  lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when
  password is expiring

Status in “samba” package in Ubuntu:
  Confirmed
Status in “samba” source package in Precise:
  Confirmed

Bug description:
  My precise client is member of a Windows Domain. A domain user can
  login using samba/winbind without problem in tty and via lightdm if
  the user password is ok.

  If the password is expiring a domain user logs in correctly via TTY,
  with a message "Your password is expiring in 10 days". if tries with
  lightdm the user gets the message "Your password is expiring in 10
  days", but then returns to the username request.

  On /var/log/syslog i get:

  May 23 08:50:52 tv52605 kernel: [ 1046.645230] lightdm[2415]: segfault
  at 0 ip b73d976a sp bfd66fa8 error 4 in libc-2.15.so[b729c000+19f000]

  for each time the user tries to login with the domain user
  credentials.

  Expected behaviour:

  the user sees the message  "Your password is expiring in 10 days",
  then logs in (like gdm in ubuntu 10.04 does).

  I attach the crash file i found in /var/crash/ (that i'm unable to
  send via apport-bug tue to same strange bug)

  [Impact]

   * This bug makes users unable to login via the LightDM interface when
  their password is close to expiring.

   * This upload just checks for a null reference so that LightDM won't
  crash on it.

  [Test Case]

   * Set up Active Directory (not tested with Samba AD)
   * Have user passwords to expire after a certain time
   * Wait until they would be alerted for this, note crash on login

  [Regression Potential]

   * It is has been upstream for a while now and has been tested by several users.  It is also already fixing in Ubuntu Raring+
   * There might be a better way to handle the null pointer?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions