← Back to team overview

dx-packages team mailing list archive

[Bug 1499354] Re: Invalid password after long uptime

 

Just got it again, this time immediately after a screen lock. As usual,
had to jump to a terminal, lightdm restart, and blow away my session.

No login failures counted in /var/log/faillog (faillog -u myuser shows
0).

That leads me to think it's not even communicating with PAM in this
state....

I'll give the screensaver idea a try, at least. I think killing it off
from a root shell on another TTY would be less destructive than having
to wipe out my session :)

I can tell you that when it does get in this state, absolutely nothing
will allow my user account to unlock the screen - so again, is there any
kind of debug logging, tracing, etc I could enable?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1499354

Title:
  Invalid password after long uptime

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  After a 15.04 system has been running for a long time (more than 2-3
  days), and the system has locked the screen automatically during
  inactivity, attempting to unlock the screen will result in an "invalid
  password" message at the lock screen, despite using the correct
  password.

  The only fix I've found is to jump to a TTY, log in there (which
  works), and do a "sudo service lightdm restart".

  I've made no changes to my PAM configuration, nor do I have any
  packages installed which modify it.

  Only other thing I've noticed is that normally, my screens go to sleep
  after the display is locked. Every time this problem presents itself,
  the displays have awoken at some point overnight.

  No obvious errors in auth.log, xorg.log, or lightdm.log.

  Using the proprietary NVIDIA drivers.

  Unity Installed: 7.3.2+15.04.20150420-0ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1499354/+subscriptions


References