I had a new development.. Maybe I should report as a new bug? In case this helps anyone as a workaround or to fix the bug I thought I would post here:
I had the lock screen complain of the wrong password. I sure it was the right one as I tried many times and eventually opened a virtual terminal where the password worked (tried several times again in the lockscreen to be sure) BUT instead of using the unity or compiz trick as usual I found this process with ps -ef: /usr/lib/unity/unity-panel-service --lockscreen-mode and killed it, then the lock screen would take the password. This might be something for you to try I guess as as a workaround next time.. At least when I restarted the old way, the desktop, that is the panel, didn't quite work afterwards (at least the time disappears from the panel), and I would restart after getting in to be on the safe side. I might do that now also, but at least I do not seem to have any problems. [This may not stricly be the same bug, but I guess the bug is in the same program and I would guess both this and the bug in the subject have the same root cause - memory at some point running out and making trouble afterwards.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
