[system settings] Count resets to 3 tries after 3 fails at sim unlock

Bug #1415850 reported by Dave Morley
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Bill Filler
ubuntu-system-settings (Ubuntu)
Fix Released
High
Ken VanDine

Bug Description

STEPS:
/!\ Note have your sim puk code to hand for this

1. Goto system settings→security→sim pin
2. Lock a sim
3. Tap on unlock and type in the code incorrectly
4. Repeat process two more times so you require your puk to unlock

EXPECTED:
I expect the your sim is locked please use your puk code to unlock the sim

ACTUAL:
It reverts to saying 3 tries remaining.

To see expected result tap on unlock from the indcator, or fail to unlock the sim from start up (ie before you get to the welcome screen) Both of these pop up the puk code as expected.

Related branches

Dave Morley (davmor2)
tags: added: qa-promotion
Changed in ubuntu-system-settings (Ubuntu):
importance: Undecided → High
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Can we get this assigned

Changed in ubuntu-system-settings (Ubuntu):
assignee: nobody → Bill Filler (bfiller)
tags: added: lt-blocker lt-category-visible
Changed in canonical-devices-system-image:
assignee: nobody → Bill Filler (bfiller)
importance: Undecided → High
milestone: none → ww13-2015
status: New → Confirmed
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

Design, can you comment on the design? For PUK unlock, does the current spec need to change any? Thank you.

Revision history for this message
Olga Kemmet (olga-kemmet) wrote :

After the SIM card is locked by user (after 3 attempts) the PUK screen always has to be presented.
Users have 10 attempts to enter the correct PUK.
We were discussing to change the SIM PIN and PUK screens into something similar as the WiFi password request. In user testing people often confused the SIM PIN screen with their passcode screen.

Revision history for this message
Dave Morley (davmor2) wrote :

Olga, Jonas:
So currently what happens in both booted system and indicator is as follows:
1. Pin input incorrect
2. You are told it's wrong, count say 2 chances
3. You input the wrong pin again
4. You now get a warning message that you have input the number incorrectly 2 times a third will lock the sim, count say 1 chance
5. You input the number incorrectly again
6. You see the PUK code entry page with a count of 10

In the system-setting app however the following happens:
1. Pin input incorrect
2. You are told it's wrong, count say 2 chances
3. You input the wrong pin again
4. You now get a warning message that you have input the number incorrectly 2 times a third will lock the sim, count say 1 chance
5. You input the number incorrectly again
6. Count resets to 3 chances you get not PUK code page.

The inconsistency in the three methods is the issue here. However the page redesign would be nice too I guess :)

Revision history for this message
Olga Kemmet (olga-kemmet) wrote :

Dave, the behaviour in system settings is not correct. :) It should be as you described for indicators or booted system.

summary: - Count resets to 3 tries after 3 fails at sim unlock
+ [system settings] Count resets to 3 tries after 3 fails at sim unlock
Changed in ubuntu-ux:
assignee: nobody → Olga Kemmet (olga-kemmet)
importance: Undecided → High
status: New → Triaged
assignee: Olga Kemmet (olga-kemmet) → nobody
assignee: nobody → Matthew Paul Thomas (mpt)
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Oops, I never got as far as designing the case where you use up all your chances to enter the correct PIN.

Revision history for this message
Olga Kemmet (olga-kemmet) wrote :

Matthew, it is documented in the Greeter spec, if it helps. :)

Bill Filler (bfiller)
Changed in ubuntu-system-settings (Ubuntu):
assignee: Bill Filler (bfiller) → Jonas G. Drange (jonas-drange)
Changed in ubuntu-system-settings (Ubuntu):
assignee: Jonas G. Drange (jonas-drange) → Ken VanDine (ken-vandine)
Revision history for this message
Ken VanDine (ken-vandine) wrote :

I've opened bug 1438323 to add support for entering the PUK

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20150401.2-0ubuntu1

---------------
ubuntu-system-settings (0.3+15.04.20150401.2-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Ken VanDine ]
  * Fixed handling of pinRetries Improved dbusmock template for ofono to
    support testing LockPin, UnlockPin, ChangePin and EnterPin (LP:
    #1415850)
 -- CI Train Bot <email address hidden> Wed, 01 Apr 2015 18:30:16 +0000

Changed in ubuntu-system-settings (Ubuntu):
status: New → Fix Released
Bill Filler (bfiller)
Changed in canonical-devices-system-image:
status: Confirmed → Fix Released
no longer affects: ubuntu-ux
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.