| 2014-08-30 11:28:47 |
Michał Sawicz |
bug |
|
|
added bug |
| 2014-08-30 11:28:59 |
Michał Sawicz |
bug task added |
|
unity8 (Ubuntu RTM) |
|
| 2014-08-30 11:29:29 |
Michał Sawicz |
description |
It's happened to me a few times that even though I selected passcode (4 digit) as my lock (e.g. in the wizard), I was still presented with a full keyboard.
I'm worried that for someone it might result in the opposite, rendering the phone inaccessible because you can't type your passphrase with a pin-pad.
We either need to improve robustness of the setting (ideally storing the lick type next to the password itself in PAM somehow?) or allow switching to a full keyboard entry in the passcode lockscreen.
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: ubuntu-system-settings 0.3+14.10.20140828.2~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.6-0ubuntu2
Architecture: armhf
Date: Sat Aug 30 11:23:04 2014
InstallationDate: Installed on 2014-08-30 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140830-030204)
SourcePackage: ubuntu-system-settings
UpgradeStatus: No upgrade log present (probably fresh install) |
It's happened to me a few times that even though I selected passcode (4 digit) as my lock (e.g. in the wizard), I was still presented with a full keyboard in the lockscreen.
I'm worried that for someone it might result in the opposite, rendering the phone inaccessible because you can't type your passphrase with a pin-pad.
We either need to improve robustness of the setting (ideally storing the lick type next to the password itself in PAM somehow?) or allow switching to a full keyboard entry in the passcode lockscreen.
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: ubuntu-system-settings 0.3+14.10.20140828.2~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.6-0ubuntu2
Architecture: armhf
Date: Sat Aug 30 11:23:04 2014
InstallationDate: Installed on 2014-08-30 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140830-030204)
SourcePackage: ubuntu-system-settings
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2014-08-31 09:15:39 |
Sebastien Bacher |
ubuntu-system-settings (Ubuntu): importance |
Undecided |
High |
|
| 2014-09-01 09:47:06 |
Oliver Grawert |
ubuntu-system-settings (Ubuntu): status |
New |
Confirmed |
|
| 2014-09-01 19:45:02 |
Sebastien Bacher |
ubuntu-system-settings (Ubuntu): assignee |
|
Michael Terry (mterry) |
|
| 2014-09-08 17:06:58 |
Martin Pitt |
bug |
|
|
added subscriber Martin Pitt |
| 2014-09-08 21:02:30 |
Launchpad Janitor |
branch linked |
|
lp:~mterry/ubuntu-system-settings/allow-some-failures |
|
| 2014-09-09 12:16:05 |
Michael Terry |
summary |
Storage of passcode vs. passphrase lock type unreliable |
Setting a PIN can result in a passphrase instead |
|
| 2014-09-09 20:09:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/utopic-proposed/ubuntu-system-settings |
|
| 2014-09-09 20:19:39 |
Launchpad Janitor |
ubuntu-system-settings (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2014-10-06 06:15:19 |
Michał Sawicz |
unity8 (Ubuntu RTM): status |
New |
Incomplete |
|
| 2014-10-17 08:21:22 |
Albert Astals Cid |
bug task added |
|
unity8 (Ubuntu) |
|
| 2014-10-17 08:21:42 |
Albert Astals Cid |
unity8 (Ubuntu): status |
New |
Incomplete |
|
| 2015-06-10 07:21:42 |
Alfonso Sanchez-Beato |
unity8 (Ubuntu): status |
Incomplete |
New |
|
| 2015-06-19 14:16:01 |
Albert Astals Cid |
bug |
|
|
added subscriber Albert Astals Cid |
