Nowadays the wizard lets you select the 4-digit pin code and set it, but
it's actually still the passphrase set during flashing. For ease of use
purposes, I now everytime go to system settings to really switch from
passphrase to 4-digit passcode manually.
--
You received this bug
Yep, certainly not a priority, just nice to have.
** Changed in: unity8 (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389771
Title:
[wizard] 4-digit
Timo, looks like I never actually explained what's going on behind the
scenes in this bug. There are two things going on in your workflow:
1) ubuntu-device-flash treats the --password argument as a passphrase
always. Ideally it would inspect and see if it looks like a PIN, then
set it as such.
** Package changed: ubuntu-system-settings (Ubuntu) = unity8 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389771
Title:
[wizard] 4-digit passcode code gets set incorrectly as passphrase
** 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.
https://bugs.launchpad.net/bugs/1389771
Title:
[wizard] 4-digit passcode code gets set incorrectly as
To be exact, when flashing with --developer-mode --password=, there
is no selection given about which kind of security is used, but it does
ask for the 4 digit code (twice). Ie it skips the screen one would
select passphrase or passcode.
--
You received this bug notification because you are
I haven't been able to reproduce, either with manually re-enabling the
wizard (and making sure to empty my password with sudo passwd -d
phablet before rebooting) or by flashing with --bootstrap. With image
krillin/rtm 143.
How reliable is this bug for you?
--
You received this bug notification
This happens to me every time on mako, but maybe it's something that
comes from the flash parameters:
ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed
--developer-mode --password= --bootstrap
That could be the most likely explanation? I only use the --password
because at
Confirming that bootstrap flashing without --developer-mode
--password= does not have this issue. Feel free to mark this as
Invalid, unless you want to fix the CI mode use case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
