Passcode is set but passcode screen is not presented to unlock
Bug #1488397 reported by
Pat McGowan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-system-settings (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
rc-proposed r96
Turn off passcode and use swipe
Enable passcode via developer mode
the passcode is set and remembered
Hit power to suspend then reumes, the passcode prompt is not displayed
The groups command shows the user is still part of the nopasswdlogin group
phablet adm tty dialout cdrom sudo dip video plugdev nopasswdlogin radio bluetooth android_graphics android_input audio android_media sdcard_rw gps android_cache android_net3 android_net android_net2 android_nvram
summary: |
- Passcode is set but lock screen is not presented + Passcode is set but passcode screen is not presented to unlock |
To post a comment you must log in.
the settings backend has this code/note
" QDBusReply<void> reply = iface.call( "SetPasswordMod e", newMode); ).name( ) == "org.freedeskto p.Accounts. Error.Failed" ) { p.Accounts. Error.Failed" because we actually nDenied) .
if (reply.isValid() || reply.error(
// We allow "org.freedeskto
// expect that error in some cases. In Ubuntu Touch, group memberships
// are not allowed to be changed (/etc/group is read-only). So when
// AccountsService tries to add/remove the user from the nopasswdlogin
// group, it will fail. Thankfully, this will be after it does what we
// actually care about it doing (deleting user password). But it will
// return an error in this case, with a message about gpasswd failing
// and the above error name. In other cases (like bad authentication),
// it will return something else (like Error.Permissio
return true;"
That's a good point, you had the user in that group likely because your device is rw, that can't happen with a "normal" ro image, still an issue but probably not an high one