Unlocking screen from CLI prompts for password
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Triaged
|
Wishlist
|
Unassigned | ||
unity (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I use blueproximity to lock my screen when I am going away from my computer.
It is python script that checks distance to bluetooth device and uses:
gnome-screensav
to lock the screen when the bluetooth device is away and
gnome-screensav
to unlock it.
Since 14.04 I have been prompted for password when I get back to my computer (it is not gnome keyring password, it is unlock screen password). It worked without password before.
I am aware of the bug causing lock screen asking for password twice and I turned off the lock in Brightness and Lock system settings to fix it. It seems that the problem is unrelated and authors of the new unlock mechanism didn't consider unlocking screen remotely or from command line interface.
Changed in unity: | |
importance: | Undecided → Wishlist |
Changed in unity (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in unity: | |
status: | New → Triaged |
Changed in unity (Ubuntu): | |
status: | New → Triaged |
The problem with screen lock asking for password twice is already solved and it was caused by the fact that the new Unity lock screen didn't turn off the screen.
https:/ /bugs.launchpad .net/unity/ +bug/1292451
https:/ /bugs.launchpad .net/unity/ +bug/1292041
The new lock screen is entirely implemented in Unity so your gnome-screensaver commands are useless. I know that gnome-screensaver is still used as a fallback mode in two cases. The first is if you have sreen reader enabled and the second one if you have OSK (On-Screen Keyboard) enabled.
This is the branch that implemented new Unity lock screen:
https:/ /code.launchpad .net/~andyrock/ unity/lockscree n/+merge/ 206291