Screen no longer locks with passcode set

Bug #1400742 reported by Ken VanDine on 2014-12-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity8 (Ubuntu RTM)
Undecided
Unassigned

Bug Description

Image 14.09-proposed #173

I have a passcode (pin) set under security and developer mode works, but I can unlock the screen with swipe.

Ken VanDine (ken-vandine) wrote :
Ken VanDine (ken-vandine) wrote :
Ken VanDine (ken-vandine) wrote :

Over the weekend I switched from passcode to swipe, passcode was working before and the switch to swipe worked fine. But when I switched it back to passcode, the greeter didn't honor it. I've switched it a few times now and rebooted the device as well.

Michael Terry (mterry) wrote :

So in your unity8.log, I noticed the following interesting message:

file:///usr/share/unity8/Greeter/GreeterContent.qml:69:5: QML QQuickImage: Cannot open: file:///usr/share/backgrounds/Kronach_leuchtet_2014_by_Brian_Fox.jpg

Thinking maybe if there's some problem with the wallpaper, we enter an error case from hell and open the doors, but I couldn't reproduce that problem when I played around with bad wallpapers.

Your extrausers file indicates that your user *does* have a password set. So it is unity8 that's the odd one out, not system-settings.

I'm still confused why this would happen. One other bit of useful logs would be /var/log/auth.log if you can upload that...

Ken VanDine (ken-vandine) wrote :
Michael Terry (mterry) wrote :

I am still unable to reproduce, but it looks like we know why this happens. Ken's phablet user got added to the "nopasswdlogin" group, so unity8 isn't prompting for a login.

Now getting added to this group isn't so unusual. That happens when switching to swipe mode when your device is in writable mode (normally in RO mode, that doesn't happen).

But also when in writable mode, if you switch back to passcode, your user is supposed to be removed from the group. That isn't happening here, and it's not clear why. Ken's device is still in writable mode. And the permissions for /etc/group seem fine.

So this is either a bug in system-settings or accountsservice.

I haven't been able to reproduce yet on my krillin either. Ken says he can't reproduce on his other device, a mako. So something is messed up with his krillin.

Michael Terry (mterry) wrote :

Based off of Ken's system-settings log, we see:

2014-12-08 12:11:39,752 - WARNING - Could not set password mode: "Authentication is required"

Which means that AS and system-settings couldn't agree on authenticating the user enough to let the user change their password mode under the covers. We'd need to add some debug prints for both of those and investigate what's going on in more depth I think, to nail this down further.

Michael Terry (mterry) wrote :

But one important takeaway is that this would only ever happen on devices that were made writable. So not devices that users see, but only developers.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers