Closed Bug 1175910 Opened 9 years ago Closed 9 years ago

[Settings] Lockscreen panel doesn't take a new password into account (set to 0000 on a freshly flashed device)

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::Settings
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:2.5+, b2g-master fixed)

Status:
VERIFIED FIXED
Milestone:
FxOS-S1 (26Jun)
Project Flags:
blocking-b2g 2.5+
Tracking Flags:
Tracking Status
b2g-master --- fixed

People

(Reporter: njpark, Assigned: freddy)

References

Details

(Keywords: regression, smoketest, Whiteboard: fbimage)

STR: Go to settings, set lockscreen code to 1234. Press the power button twice to turn off / on the phone Unlock the phone and enter 1234. Expected: Screen unlocks Actual: Screen rejects the lockscreen code. only takes 0000 as valid lockscreen. Checked that I properly changed the lockscreen by going to Settings -> Lockscreen. I had to type in 1234 to change the lockscreen. Version Info: Build ID 20150618010201 Gaia Revision b404c41c5471c31610e64defb74ec066b411e724 Gaia Date 2015-06-17 17:01:15 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/a3f280b6f8d5 Gecko Version 41.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150618.043514 Firmware Date Thu Jun 18 04:35:26 EDT 2015 Bootloader L1TC000118D0
Whiteboard: fbimage
ni?ed Gerry FYI.
Flags: needinfo?(gchang)
[Blocking Requested - why for this release]: Reproduced on a freshly flashed Aries. Build ID 20150618035728 Gaia Revision b404c41c5471c31610e64defb74ec066b411e724 Gaia Date 2015-06-17 17:01:15 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/a3f280b6f8d5 Gecko Version 41.0a1 Device Name aries Firmware(Release) 4.4.2 Firmware(Incremental) eng.worker.20150618.034225 Firmware Date Thu Jun 18 03:42:33 UTC 2015 Bootloader s1
blocking-b2g: --- → spark?
Keywords: smoketest
On my dogfood aries that I OTA'd to 20150618035728, I just notice that I have to type the opposite of my passcode. For instance: I set 1234 in settings, I have to type 4321 on the lockscreen to enable it.
Works on gaia revision fc9cb65bfe557063792e0cf10f7939f03f0532e5, but not on b404c41c5471c31610e64defb74ec066b411e724, with the same gecko each time. This is a gaia regression, bisecting.
The regression window pointed bug 1123325. Resolved by backout. (In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #3) > For instance: I set 1234 in settings, I have to type 4321 on the lockscreen to enable it. After doing it, I noticed that actually, the new password wasn't taken into account. 4321 might have been a password I set previously for testing purpose.
Blocks: 1123325
Status: NEW → RESOLVED
Closed: 9 years ago
Component: Gaia::System::Lockscreen → Gaia::Settings
Keywords: qaurgent, regressionwindow-wanted
Resolution: --- → FIXED
Summary: Flame: lockscreen only takes 0000 to unlock, even with the lockscreen code set → [Settings] Lockscreen panel doesn't take a new password into account (set to 0000 on a freshly flashed device)
I was able to unlock the phone with a passcode other than 0000. This issue is verified fixed. Device: Flame 3.0 (Full Flash) BuildID: 20150619010205 Gaia: a0df9c367a68764bdcf2e2e1c4d27f0d6ee165b8 Gecko: 2694ff2ace6a Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 41.0a1 (3.0) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Status: RESOLVED → VERIFIED
status-b2g-master: affected → fixed
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Per comment #6, remove ni.
Flags: needinfo?(gchang)
blocking-b2g: spark? → 2.5?
Was a smoketest blocker.
blocking-b2g: 2.5? → 2.5+
blocking-b2g: 2.5+ → spark+
blocking-b2g: spark+ → 2.5+
Assignee: nobody → fbraun
status-b2g-v2.5: --- → fixed
Target Milestone: --- → FxOS-S1 (26Jun)
You need to log in before you can comment on or make changes to this bug.