Closed Bug 1020628 Opened 11 years ago Closed 11 years ago

[B2G][Settings]Double tap left blue arrow in Keyboard Settings causes black screen to appear

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3T+, b2g-v1.3 unaffected, b2g-v1.3T fixed, b2g-v1.4 fixed, b2g-v2.0 fixed)

RESOLVED FIXED
2.0 S4 (20june)
blocking-b2g 1.3T+
Tracking Status
b2g-v1.3 --- unaffected
b2g-v1.3T --- fixed
b2g-v1.4 --- fixed
b2g-v2.0 --- fixed

People

(Reporter: mclemmons, Assigned: timdream)

References

()

Details

(Keywords: regression, Whiteboard: [tarako-exploratory])

Attachments

(5 files)

User taps Settings App then Keyboards and Built-in Keyboard. User double taps left blue arrow on line with Keyboard Settings and the screen goes black with only the time, battery life, and connection status. The user's only options are to restart the device, take a screenshot (power + home screen), or double tap the device screen and hold down the homescreen button to activate card view. From there, the user can return to normal operations. Repro Steps: 1) Update a Tarako to BuildID: 20140604014021 2) Tap Settings, scroll to keyboards and tap it 3) Tap Built-in Keyboard and to the left of Keyboard Settings double tap the blue arrow 4) Observe device behavior Actual: Screen goes black with only the time, battery life, and connection status. Expected: Screen returns to Keyboards Notes: Repro frequency: (5/5, 100%) See attached: (video clip = https://www.youtube.com/watch?v=86ZCxLy8vTo, logcat, firewatch) 1.3T Environmental Variables: Device: Tarako 1.3T BuildID: 20140604014021 Gaia: 41a763154fbac34bef6baf17a201e50f52f2b72a Gecko: fed0b4e6da6c Version: 28.1 Firmware Version: sp6821a-gonk-4.0-5-12 User Agent: Mozilla/5.0 (Mobile; rv:28.1) Gecko/28.1 Firefox/28.1
Attached file Firewatch Log
This doesn't quite happen on 1.3 For a brief moment the screen does turn black and then the Keyboards page w/ Build-in Keyboard bounces back in. Gaia 2408c2238254776b0d3716753b7bf917883c9915 Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/560138f48a17 BuildID 20140603024001 Version 28.0 ro.build.version.incremental=324 ro.build.date=Thu Dec 19 14:04:55 CST 2013 Buri I suspect that this might be a regression from the keyboard fix in the settings area that was done earlier ( about a month or two ago ) for Tarako.
blocking-b2g: --- → 1.3T?
Possibly bug 988782? Need to check if that's the regression window.
Keywords: qawanted
This issue does reproduce on 1.4 Flame following the STR from Comment 0. A black screen appears and the user's only option around this 1) restart device, 2) take a screenshot, 3) or double tap the screen and hold the homescreen button. This is similar to the 1.3 Tarako. 1.4F Environmental Variables: Device: Flame 1.4F BuildID: 20140604000202 Gaia: 0c16adced7c51f795ef250aebe184f60b6a9b987 Gecko: 04216748e6c1 Version: 30.0 Firmware Version: v10G-2 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Keywords: qawantedregression
Whiteboard: [tarako-exploratory] → [tarako-exploratory][1.4-approval-needed]
Tarako Regression Window Last working Environmental Variables: Device: Tarako 1.3T Build ID: 20140425014208 Gaia: 440cbdb5c7fec10e424985e7844ae4cbedc38808 Gecko: 4a7efaf4b596 Version: 28.1 (1.3T) Firmware Version: SP6821a-Gonk-4.0-5-12 First Broken Environmental Variables: Device: Tarako 1.3T Build ID: 20140425021808 Gaia: 8f0886c459667df1896361e4b2f94a49fd5a01b1 Gecko: 612a5616a1b6 Version: 28.1 (1.3T) Firmware Version: SP6821a-Gonk-4.0-5-12 Last working gaia / First broken gecko - Issue does not occur Gaia: 440cbdb5c7fec10e424985e7844ae4cbedc38808 Gecko: 612a5616a1b6 First broken gaia / Last working gekko - Issue occurs - indicates gaia issue Gaia: 8f0886c459667df1896361e4b2f94a49fd5a01b1 Gecko: 4a7efaf4b596 Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/440cbdb5c7fec10e424985e7844ae4cbedc38808...8f0886c459667df1896361e4b2f94a49fd5a01b1
Broken by bug 988782. If that's the case, then I don't think comment 5 is correct, since bug 988782 only landed on master & 1.3T. QA Wanted to double check 1.4 here again. Tim - Can you investigate?
Blocks: 988782
Flags: needinfo?(timdream)
Keywords: qawanted
This issue occurs on 1.4 Flame. The steps to getting the bug to reproduce is exactly the same, however, instead of a black screen, Flame displays an empty homescreen as the attached image. Tested on: Device: Flame Build ID: 20140605000203 Gaia: 1f238df7ac68a73a4ceb27391a204c800f38ab1c Gecko: a7b7f1b579cc Version: 30.0 Firmware Version: v10G-2 I then also tested on Buri 1.4, and Buri exhibits the issue exactly the same as on Flame.
This is a fun bug. We could just block the second click event.
Assignee: nobody → timdream
Status: NEW → ASSIGNED
Flags: needinfo?(timdream)
Interestingly, I cannot repro this on master today :-/
Comment on attachment 8435574 [details] [review] mozilla-b2g:v1.3t PR#20124 Fix 1.3T first because this is the first branch reproducible to me.
Attachment #8435574 - Flags: review?(rlu)
master patch https://github.com/mozilla-b2g/gaia/pull/20126 we would need this on 1.4t too but first bug 988782 needs to be uplifted to it.
Comment on attachment 8435574 [details] [review] mozilla-b2g:v1.3t PR#20124 Simple enough, r+. Thanks for handling this issue. -- Seems like we have an issue in v1.3t window/activity management?
Attachment #8435574 - Flags: review?(rlu) → review+
1.3t: waiting for blocking decision. 1.4: waiting for bug 988782 to be uplifted first. master: https://github.com/mozilla-b2g/gaia/commit/4b40c62b759b20d94c69b66a5dae3263cc1607ad I am seeing a v2.0 branch on Github but no MERGE_DAY tag so I don't know if this commit will reach 2.0 or not. I am leave-open this bug until I could figure out this (and, maybe correct the flag.)
Keywords: leave-open
bug 988782 uplifted and this can be uplifted too.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Keywords: leave-open
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S4 (20june)
Can I land it on v1.3t? It's review+ and green.
let's take this for 1.3T James, can you team please merge it? thanks
blocking-b2g: 1.3T? → 1.3T+
Hi Tim, Can we have a 1.4 patch to be landed on to the 1.4 branch here? Once you have that please set 1.4 approval request to :preeti. Thanks!
Flags: needinfo?(timdream)
Attached file master patch
[Approval Request Comment] [Bug caused by] (feature/regressing bug #): N/A [User impact] if declined: The STR remain reproducible on 1.4 [Testing completed]: No known regression on master for 2 weeks [Risk to taking this patch] (and alternatives if risky): should be small. [String changes made]: None
Attachment #8445678 - Flags: review+
Attachment #8445678 - Flags: approval-gaia-v1.4?(praghunath)
Flags: needinfo?(timdream)
Comment on attachment 8445678 [details] [review] master patch Taking on 1.4 per Dolphin requirements
Attachment #8445678 - Flags: approval-gaia-v1.4?(praghunath) → approval-gaia-v1.4+
Whiteboard: [tarako-exploratory][1.4-approval-needed] → [tarako-exploratory]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: