I'm not sure what all the auto-generated info is telling - supposedly
should be saying what I was running and what config when I hit the bug.
I assume however it's really telling what I'm runnig at bug-submit? I
may have installed libraries but not restarted and then still using
older libraries? Note I think that doesn't apply to unity but not sure
what unity/compiz used directly or indirectly. Anyway I restarted
recently and it's either a current bug or one fixed in last 9 days and
can't see that from changelogs of stuff I haven't installed. Can't see
changelog (in update-manager) for stuff I've installed after reset of
machine but may not have been running when hitting the bug.
Note what I said (including in previous bug submittion) that I restarted
unity (and compiz) after the bug and before "ubuntu-bug unity".
I have several packages with this version and that version available
(all with this changelog):
Changes for libgbm1 versions:
Installed version: 10.1.3-0ubuntu0.1
Available version: 10.1.3-0ubuntu0.2
Version 10.1.3-0ubuntu0.2:
[ Timo Aaltonen ]
* Drop fix-kwin.diff hack, as 10.1.3 has 0380ec467d78f40 which
fixes the issue properly.
[ Maarten Lankhorst ]
* Add fix-svga-ioctl.patch (LP: #1365490)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1378919
Title:
After going to lock screen can't login as not prompted for password -
maybe not a unity bug
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378919/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
