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. 2) The wizard can't override an existing password for the user. Ideally if a password was already set, those pages would be skipped or grayed out or something. So that's two poor usability issues combining to be confusing when flashing with --password. But it's not a bug normal users see, just developers. I'd argue both could/should be fixed. But they just haven't been a priority. ** Summary changed: - [wizard] 4-digit passcode code gets set incorrectly as "passphrase" on first run + [wizard] 4-digit passcode code gets set incorrectly as "passphrase" on first run when flashing with --password -- 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" on first run when flashing with --password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389771/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
