Closed
Bug 956454
Opened 11 years ago
Closed 11 years ago
[B2G][Settings][SIM Security] SIM Security menu is unable when toggle Airplane mode on/off
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:1.3+, b2g-v1.2 unaffected, b2g-v1.3 fixed)
RESOLVED
FIXED
blocking-b2g | 1.3+ |
Tracking | Status | |
---|---|---|
b2g-v1.2 | --- | unaffected |
b2g-v1.3 | --- | fixed |
People
(Reporter: sarsenyev, Assigned: jaoo)
References
Details
(Keywords: regression, Whiteboard: dogfood1.3)
Attachments
(1 file)
(deleted),
image/png
|
Details |
Description:
SIM Security menu is grayed out and unable when switching "Airplane mode" on and then off when a SIM PIN is previously set on
Prerequisites:
SIM PIN is set on the device
Repro Steps:
1) Updated Buri to BuildID: 20140103004001
2) Go to "Settings" from the home screen
3) Toggle "Airplane mode " on and then off
4) Observe the "Security PIN" menu
5) Press the "Power" button twice
6) When the "SIM passcode" screen opens type a correct PIN code
7) Observe the "Security PIN" menu
Actual:
The SIM Security menu is grayed out and not available
Expected:
When the SIM PIN is enabled the settings info shows "Enabled"
When the SIM PIN is disabled the settings info shows "Disabled"
Environmental Variables:
Device: Buri 1.3 COM
BuildID: 20140103004001
Gaia: ae7d05689b6b9ac4ec6182217dfdef06be28e886
Gecko: d9226a660d52
Version: 28.0a2
RIL Version: 01.02.00.019.102
Firmware Version: v1.2_20131115
Notes:
Repro frequency: 100%
See attached: video clip
It doesn't reproduce on the latest 1.2
"SIM Security" doesn't gray out when airplane mode is on, just a message is changed for "SIM card not ready"
Device: Buri 1.2 MOZ
BuildID: 20140106004001
Gaia: 8441587c3b352e052fee07665c21fd192540f19f
Gecko: d552c08a72d0
Version: 26.0
Firmware Version: v1.2_20131115
Keywords: qawanted
status-b2g-v1.2:
--- → unaffected
status-b2g-v1.3:
--- → affected
Keywords: regression,
regressionwindow-wanted
Updated•11 years ago
|
blocking-b2g: --- → 1.3?
Updated•11 years ago
|
QA Contact: bzumwalt
Comment 3•11 years ago
|
||
Triage: regression
EJ, this is caused by the bug you are fixing right now? Could you dup this if your patch on that bug fix this issue?
Flags: needinfo?(ejchen)
Updated•11 years ago
|
blocking-b2g: 1.3? → 1.3+
Comment 4•11 years ago
|
||
Hi Jose,
I checked the code in settings.js about this part and it seems that this bug is related to bug 928297.
I asked Arthur about that bug and it seems that you had a refactor plan about it. (which is also related to this bug)
Any further news/ideas about it ?
Thanks :)
Flags: needinfo?(ejchen) → needinfo?(josea.olivera)
Comment 5•11 years ago
|
||
Confirming regression. Jose, could you either provide a quick fix to this bug or roll your refactor plan (bug ?) to 1.3?
Depends on: 928297
Keywords: regressionwindow-wanted
Assignee | ||
Comment 6•11 years ago
|
||
Too many changes have been added to the setting app due the support added for multi ICC card devices. Bug 945150 is about disabling/enabling the menu items (such as call setting, cellular an data, SIM security, etc) in the root panel correctly so I'll handle this issue in bug 945150. See https://bugzilla.mozilla.org/show_bug.cgi?id=945150#c14 for more information about what is going on bug 945150 please. Should we resolve (somehow) this bug as a duplicate of bug 945150?
Flags: needinfo?(josea.olivera)
Comment 7•11 years ago
|
||
Update based on comment 6.
Thanks José!
Assignee: nobody → josea.olivera
Depends on: 945150
Assignee | ||
Comment 8•11 years ago
|
||
Bug already landed 945150 so this issue should not happen. I'll request QA to verify it.
Flags: needinfo?(sarsenyev)
Keywords: qawanted
Yes, the fix is landed on master build,
So it doesn't reproduce on master build 1.4
"SIM Security" option is accessible after entering a correct SIM PIN
Device: Buri 1.4 MOZ
BuildID: 20140117041037
Gaia: ef8bb31b462f364b57432a0724c78034d3f4f303
Gecko: b53589696cf8
Version: 29.0a1
Firmware Version: v1.2-device.cfg
Flags: needinfo?(sarsenyev)
Comment 10•11 years ago
|
||
Marking fixed then & leaving 1.3 affected until the dependency gets uplifted.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•