Closed Bug 1163680 Opened 10 years ago Closed 10 years ago

[Windows Management] Using both a Lockscreen Passcode and SIM PIN will result in a broken / offset SIM PIN screen and homepage

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master verified)

VERIFIED FIXED
2.2 S12 (15may)
blocking-b2g 2.5+
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- verified

People

(Reporter: jmitchell, Assigned: gduan)

References

()

Details

(Keywords: regression, Whiteboard: [3.0-Daily-Testing], [systemsfe])

Attachments

(4 files)

Attached file logcat_20150511_0931.txt (deleted) —
Description: With SIM PIN and lockscreen passcode enabled - the screens become corrupted when entering in the lockscreen passcode. After entering the SIM PIN or selecting SKIP the user will find themselves at a broken homescreen. Only the top 1/5 shows correctly. There is a large blank spot in the middle of the screen and the bottom shows the Lockscreen entry and top of the keyboard (it appears that the Lockscreen entry screen did not fully dismiss. User can only interact with the top part of the screen. (See Video) Any apps launched will only show in the top 1/5th of the screen Notes: This issue (or similar) seems to have been written before in Bug 1092282 (different steps but same look from screenshot) - but that was resolved to a bug that is now verified fixed so I'm opening a new issue for this. Repro Steps: 1) Update a Flame to 20150511010202 2) Launch Settings and enable SIM PIN and Lockscreen Passcode 3) Restart the device 4) On lockscreen , slide toggle to the right and enter lockscreen passcode 5) Enter or Skip SIM PIN Actual: Homescreen is broken Expected: normal homescreen encountered Environmental Variables: Device: Flame 3.0 Build ID: 20150511010202 Gaia: 6089234ace8b294a8feef064387604bae16254e3 Gecko: d8420a541d1c Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Repro frequency: 7/7 See attached: logcat, video clip http://youtu.be/hG15OLkaLDA
This issue did NOT reproduce in Flame KK 2.2 Device: Flame 2.2 (KK - Nidghtly - Full Flash - 319mem) Build ID: 20150511002500 Gaia: 528ef60e7cda09ad43478065f5d33bda398fbeb7 Gecko: 8d04cc085cf5 Gonk: ab265fb203390c70b8f2a054f38cf4b2f2dad70a Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
blocking-b2g: --- → 3.0+
QA Contact: ychung
Attached image 2015-05-06-07-28-46.png (deleted) —
What I see is a slightly different issue. After unlocking the device with the passcode, The SIM PIN screen displays the 4 slots from the lockscreen passcode screen, and the screen remains on the screen when the user presses "skip". I think it's still the same issue as the UI breaks, and the homescreen is cut off when the user presses the home button. And here's the window I found: Central Regression Window: Last Working Environmental Variables: Device: Flame 3.0 BuildID: 20150505202942 Gaia: 3e6fd1e0a478af2c95d09ce95c2c6de2de2fec14 Gecko: ba44099cbd07 Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 First Broken Environmental Variables: Device: Flame 3.0 BuildID: 20150506024714 Gaia: eb3f82f3b947f1ed52fa4e9246bed0f0b3e49785 Gecko: 00711330027d Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Last Working Gaia First Broken Gecko: Issue does NOT reproduce Gaia: 3e6fd1e0a478af2c95d09ce95c2c6de2de2fec14 Gecko: 00711330027d First Broken Gaia Last Working Gecko: Issue DOES reproduce Gaia: eb3f82f3b947f1ed52fa4e9246bed0f0b3e49785 Gecko: ba44099cbd07 https://github.com/mozilla-b2g/gaia/compare/3e6fd1e0a478af2c95d09ce95c2c6de2de2fec14...eb3f82f3b947f1ed52fa4e9246bed0f0b3e49785 Caused by bug 1159866
Flags: needinfo?(ktucker)
QA Contact: ychung
Blocks: 1159866
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
George, can you take a look at this please? This might have been caused by the work done for bug 1159866.
Flags: needinfo?(ktucker) → needinfo?(gduan)
Comment on attachment 8605048 [details] [gaia] cctuan:1163680 > mozilla-b2g:master Hi Alive, could you review this patch? I'm not sure if it makes sense. I found out that sim_lock_manager listen to lockscreen-appclosed to show the dialog, but the lockscreen_window_manager has not yet published deactivated event to hierarchy_manager so the hierarchy cannot be updated correctly. That's why lockscreen_window_manager is still on the front when dialog shows. This fix works for this bug, but I'm not sure if any side effect.
Flags: needinfo?(gduan)
Attachment #8605048 - Flags: review?(alive)
Comment on attachment 8605048 [details] [gaia] cctuan:1163680 > mozilla-b2g:master We cannot maintain this (opened and open is equivalent, open should be deprecated.). No any good idea now, since this looks really bad, I will suggest to back out the original patch and figure out how to do that properly - or not doing that.
Attachment #8605048 - Flags: review?(alive)
ok, let's revert original patch.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Marking fixed by backout in comment 8.
Resolution: WORKSFORME → FIXED
Assignee: nobody → gduan
Target Milestone: --- → 2.2 S12 (15may)
This bug has been verified as pass on latest Nightly build of Flame v3.0 and Nexus 5 v3.0 by the STR in Comment 0. Actual results: After restarting device and inputing passcode, both SIM PIN screen and Homescreen display normally. See attachment: verified_v3.0.mp4 Reproduce rate: 0/10 -------------------------------------------------------------- Device: Flame v3.0 build(Pass) Build ID 20150526160204 Gaia Revision 8ca93673869a64e09ed6153c5402896822dfb253 Gaia Date 2015-05-26 19:31:37 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/1e4e369822ac Gecko Version 41.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150526.195035 Firmware Date Tue May 26 19:50:45 EDT 2015 Bootloader L1TC000118D0 Device: Nexus 5 v3.0 build(Pass) Build ID 20150526160204 Gaia Revision 8ca93673869a64e09ed6153c5402896822dfb253 Gaia Date 2015-05-26 19:31:37 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/1e4e369822ac Gecko Version 41.0a1 Device Name hammerhead Firmware(Release) 5.1 Firmware(Incremental) eng.cltbld.20150526.195039 Firmware Date Tue May 26 19:50:56 EDT 2015 Bootloader HHZ12f
Status: RESOLVED → VERIFIED
Attached video verified_v3.0.mp4 (deleted) —
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][MGSEI-Triage+]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: