Given that it can't be reproduced by the original reporter and that I
fixed several issues in this space recently, I'd like to tentatively
close this bug. If you see this behavior again on recent images, please
re-open and I'll look at it again.
** Changed in: ubuntu-system-settings (Ubuntu)
Ok bootstrapped to our oldest still available image which does not require a
pin entry to lock phablet - 282
Then upgraded to the newest available image 232 on manta.
And tried the exact same steps again and it works now.
But unity8 greeter only requests the pin after rebooting another time?
image version 182 instead of 282 was meant in the last comment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366814
Title:
Configure lock pin or passphrase initially fails after upgrade to 229
To
I cannot remember the exact message. I thought I could reproduce it
easily but after some trial and error that part of the issue
disappeared. I thought it was something with 'failed'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
I experienced this with mako and manta. After updating to #229 I tried
to configure a pin/passphrase to enable developer mode, but setting the
pin failed, and entering a password fails too.
Open System Settings - About this phone - Developer mode - Lock
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: Undecided = High
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) = Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This sounds like a dup of bug 1365095
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366814
Title:
Configure lock pin or passphrase initially fails after upgrade to 229
To manage notifications
Description sounds different - unity8 greeter did request a password in
case of mako (where I managed to lock myself out, because inactivity
timer disabled the screen while I was puzzled about system setting). In
manta going switching around between pin entry and no pin entry finally
resolve the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You say System Settings complains with a red failure message. -- what
is the text of that message?
pmcgowan reports seeing a does not match (or similar wording) error.
Is that what you see, Andreas?
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Confirmed = Incomplete
--
You
Can this be reproduced after upgrading to image 233?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366814
Title:
Configure lock pin or passphrase initially fails after upgrade to 229
To manage
11 matches
Mail list logo
