← Back to team overview

dx-packages team mailing list archive

[Bug 1311316] Re: After locking screen there is no input field to type password for unlock

 

I have the same bug as described on my fresh install of Ubuntu 14.04, however I'm with a newer kernel because of problems with my wifi drivers in previous versions, which were fixed:
Linux
3.17.3-031703-generic 
#201411141335 SMP Fri Nov 14 18:36:40 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 14.04.1 LTS
14.04
trusty

The problem is reproducible multiple times. After closing the laptop lid
and going in suspend for a longer period, when opened the laptop
displays the welcome screen with my wallpaper, but does not have any
field to enter password. Clicking any sound/lang icons on the menu bar
does not help, but waiting for a bit of time does.

Diagnostics so far:
So I dig a bit myself and looked at the log of lightdm, with "the problem" occurring here:
[+0.28s] DEBUG: Session pid=1224: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+0.28s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.28s] DEBUG: Session pid=1224: Logging to /var/log/lightdm/x-0-greeter.log
[+0.33s] DEBUG: Activating VT 7
[+0.33s] DEBUG: Activating login1 session c1
[+0.45s] DEBUG: Session pid=1224: Greeter connected version=1.10.3
[+0.60s] DEBUG: Session pid=1224: Greeter start authentication for alex
[+0.60s] DEBUG: Session pid=1283: Started with service 'lightdm', username 'alex'
[+1.67s] DEBUG: Session pid=1283: Got 1 message(s) from PAM
[+1.67s] DEBUG: Session pid=1224: Prompt greeter with 1 message(s)
[+3.49s] DEBUG: Session pid=1283: Authentication complete with return value 0: Success

As can be seen the period 0.60-1.67 is just waiting for the PAM service
to respond (1 minute wait). I typed my password asap as it was
available, so my guess is it is connected with the PAM service. I will
look into it, but if someone has an idea why would be great.  The
/var/log/auth.log does not contain any useful information for the why
the problem is occurring.

-- 
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/1311316

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information)
  5. Please specify the unity version
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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


References