Robin, a fix for this issue is scheduled for next SRU (almost ready!). Resetting unity from tt1 should be just fine. Or you can run metacity --replace.
2015-01-08 17:01 GMT+01:00 nybbler <nybble...@gmail.com>: > I've just run into this with Ubuntu 14.04.1, updated today at about > 15:45. I didn't happen immediately after the update, in fact it was fine > for a few hours so I think it's unlikely to be related. > > Some info: > * unity --version: unity 7.2.3 > * uname -r -v -p -i -o: 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 > 19:35:06 UTC 2014 x86_64 x86_64 GNU/Linux > * Dual-head?: yes, 2 monitors > * modified pam?: no, and not using ldap > * Running 2 VMware Workstation 10 VMs (both Windows 7 x86_64) > > I have too much work (in VMs) going to risk re-setting unity, so I'm > going to have to wait for it to timeout and hope! > > Some redacted output from /var/log/auth.log: > > Jan 8 14:24:12 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:24:12 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:24:12 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:39:43 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:41:59 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:41:59 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:41:59 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:42:57 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:43:04 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:43:04 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:43:04 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:47:37 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:47:37 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:47:37 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:47:41 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:48:38 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:48:38 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:48:38 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:49:01 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:49:01 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:49:10 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:49:10 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:54:45 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:54:45 machinename compiz: PAM adding faulty module: > pam_kwallet.so > > Robin > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1311316 > > Title: > After locking screen there is no input field to type password for > unlock > > Status in Unity: > Fix Committed > 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 > -- Andrea Azzarone http://launchpad.net/~andyrock http://wiki.ubuntu.com/AndreaAzzarone -- 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 Committed 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 -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
