Closed Bug 1173165 Opened 10 years ago Closed 10 years ago

[SHB] A 2-pixel gray line of artifact appears on top edge of screen after doing some actions

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.1 unaffected, b2g-v2.2 affected, b2g-master affected)

RESOLVED DUPLICATE of bug 1161549
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: pcheng, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [3.0-Daily-Testing][shb-enabled][spark])

Attachments

(1 file)

Description: I don't have an 100% reproduction STR for this issue, but I've seen it enough times and it has been bothering me so I decided to write it up. With SHB enabled, sometimes returning to Homescreen from an app will cause a gray line to show on top edge of screen. It looks kind of like the blue notification bar after it has been collapsed to a thin line, except for this line it is gray. STR (not 100% repro, and can be encountered in other ways): 1) Enable Software Home Button in Settings 2) Press Power & Volume Down buttons to create a screenshot 3) Pull down the notification tray, and pull it up again, to make the blue line on top of screen go away 4) Open Clock app, switch to Timer tab, and start a 1 minute timer 5) Press Home button Expected: Nothing weird shows up on top edge of screen Actual: Sometimes a gray line will appear on top edge. If not, go back to Clock app and return Home again. See screenshot of issue. The line will remain on screen until you open another app. There is another way to tell whether the bug will occur which seems to have a much higher repro rate: substitute step 5 to long pressing Home button to enter card view. If a gray line appears as you long-press the Home button, the bug will occur. Device: Flame (KK, full flashed, 319MB) BuildID: 20150609081840 Gaia: ea27c4ed5b6083c9e21d233d4804372ac4d5d353 Gecko: e10e2e8d8bf2 Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 41.0a1 (3.0 Master) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
I have also seen this issue on Aries, adding tag. 2.2 is also affected. Device: Flame 2.2 BuildID: 20150609081832 Gaia: 06edb0f8db7c2f45cde54401a8593663059861a4 Gecko: 239c59921129 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 ---------- 2.1 is unaffected. I can't get the gray line to appear no matter what I do. Device: Flame 2.1 BuildID: 20150609081402 Gaia: f8b848c82d1ed589f7a1eb5cc099830c867ff1d4 Gecko: 35e91d3657f5 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regression
Whiteboard: [3.0-Daily-Testing][shb-enabled][spark]
Note: Steps 1 to 3 are more like prerequisites/preconditions of this bug.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Contact: bzumwalt
B2G-Inbound Regression Window: Last working B2G-Inbound build: Device: Flame 3.0 Build ID: 20150409045834 Gaia: af26b7b017c3d727233da1abc916923af75454ef Gecko: b534d2562e78 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 B2G-Inbound build: Device: Flame 3.0 Build ID: 20150409065332 Gaia: eaf69e651e19b98c096f8e63b9829fb31df50927 Gecko: 6af4dd60911b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Working Gaia with Broken Gecko issue does NOT reproduce: Gaia: af26b7b017c3d727233da1abc916923af75454ef Gecko: 6af4dd60911b Working Gecko with Broken Gaia issue DOES reproduce: Gaia: eaf69e651e19b98c096f8e63b9829fb31df50927 Gecko: b534d2562e78 B2G-Inbound Pushlog: https://github.com/mozilla-b2g/gaia/compare/af26b7b017c3d727233da1abc916923af75454ef...eaf69e651e19b98c096f8e63b9829fb31df50927 Issue appears to have been caused by changes made in bug 1100332
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Alberto, can you take a look at this please? This looks to have been caused by the work done for bug 1100332.
Blocks: 1100332
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(apastor)
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(apastor)
Resolution: --- → DUPLICATE
NI myself to check whether 1172050 actually fixed this bug.
Flags: needinfo?(pcheng)
I can no longer see this on today's Flame or Aries.
Flags: needinfo?(pcheng)
I am seeing this issue again on recent builds on Aries. Haven't gotten around to figure out an STR though...
Filed bug 1196827 for what I observed at comment 8
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: