touch-packages team mailing list archive

[David Ireland <1311316@xxxxxxxxxxxxxxxxxx>]

I see this on systems with LDAP, and systems without. It's just happened
on this machine, which is built from scratch about 1 week ago. It's with
a new user - so all the user config is as created by a new clean Ubuntu
system. I haven't customised PAM at all.

I see lots of failures in auth.log, but none of them are specific to
this condition. E.g:

Feb 14 19:21:25 wilpena pkexec[29914]: david: Executing command [USER=root] [TTY=unknown] [CWD=/hom
e/david] [COMMAND=/usr/lib/update-notifier/package-system-locked]
Feb 14 19:40:28 wilpena compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so:
 cannot open shared object file: No such file or directory
Feb 14 19:40:28 wilpena compiz: PAM adding faulty module: pam_kwallet.so
Feb 14 19:40:28 wilpena compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlog
in" not met by user "david"


Feb 14 22:17:17 wilpena dbus[595]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.44" (uid=0 pid=2810 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=1637 comm="NetworkManager ")
Feb 14 22:17:17 wilpena compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Feb 14 22:17:17 wilpena compiz: PAM adding faulty module: pam_kwallet.so
Feb 15 09:12:42 wilpena dbus[595]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.68" (uid=1000 pid=3214 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.1" (uid=0 pid=667 comm="/usr/sbin/bluetoothd ")

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
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