If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Blue Firefox splash screen is not appearing upon start up

NEW
Unassigned

Status

Firefox OS
Gaia::System
2 years ago
2 years ago

People

(Reporter: Johnt, Unassigned)

Tracking

({regression})

unspecified
ARM
Gonk (Firefox OS)
regression

Firefox Tracking Flags

(blocking-b2g:2.6?, b2g-v2.5 unaffected, b2g-master affected)

Details

(Whiteboard: [2.6-Daily-Testing][Spark], URL)

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8715454 [details]
logcat_20160203_1135.txt

Description:
When starting or restarting device the blue Firefox OS splash screen is not appearing. 


Repro Steps:
1) Update a Flame to 20160203030235
2)Start OR Restart Flame device.

Actual:
A blank / black screen appears.

Expected:
It is expected that the blue Firefox OS screen will appear while the device is booting up.

Environmental Variables:
Device: Flame KK 2.6 [Full Flash] (512mb)
BuildID: 20160203030235
Gaia: 4f0e2a1a42a2d049b6fe8f4f095cdcdf0fd5465c
Gecko: f2f8fc172f4c62334e9a92bcf10e00fe877387d5
Gonk: 8a066f7fa7410e32b58def35f322aa33f03db283
Version: 46.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

Repro frequency: 4/4
See attached: Logcat & Video

Video: https://youtu.be/_yg0rPuq5nA
(Reporter)

Comment 1

2 years ago
This issue does NOT occur on Aries 2.6 or Flame 2.5.
Result: Blue Firefox OS splash screen DOES appear successfully during start up.

Environmental Variables:
Device: Aries KK 2.6
BuildID: 20160203105933
Gaia: 4f0e2a1a42a2d049b6fe8f4f095cdcdf0fd5465c
Gecko: f2f8fc172f4c62334e9a92bcf10e00fe877387d5
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 46.0a1 (2.6) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

Environmental Variables:
Device: Flame KK 2.5 [Full Flash] (512mb)
BuildID: 20160203175457
Gaia: 8c68247e3045cde7445141e94e94104d617de03b
Gecko: 80f03882ea5ee138dcccc7e7e7c2263ac862a0fa
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 44.0 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.5: --- → unaffected
status-b2g-master: --- → affected
Flags: needinfo?(ktucker)
Keywords: regression
Whiteboard: [2.6-Daily-Testing][Spark]
blocking-b2g: --- → 2.6?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][severe]
QA Contact: jmercado
Mozilla-inbound Regression Window

Last Working 
Environmental Variables:
Device: Flame 2.6
BuildID: 20160120005921
Gaia: 43852628a9d506c65525cceb5789b257cc939fe8
Gecko: c6424d5ba52216b34c517a6bcc1df62844edf92f
Version: 46.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

First Broken 
Environmental Variables:
Device: Flame 2.6
BuildID: 20160120011321
Gaia: 43852628a9d506c65525cceb5789b257cc939fe8
Gecko: 7333e869b2846ea2b71c11b8ecb7916a088c60eb
Version: 46.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

Last Working gaia / First Broken gecko - Issue DOES occur
Gaia: 43852628a9d506c65525cceb5789b257cc939fe8
Gecko: 7333e869b2846ea2b71c11b8ecb7916a088c60eb

First Broken gaia / Last Working gecko - Issue does NOT occur
Gaia: 43852628a9d506c65525cceb5789b257cc939fe8
Gecko: c6424d5ba52216b34c517a6bcc1df62844edf92f

Gecko Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c6424d5ba52216b34c517a6bcc1df62844edf92f&tochange=7333e869b2846ea2b71c11b8ecb7916a088c60eb
QA Whiteboard: [QAnalyst-Triage+][severe] → [QAnalyst-Triage?][severe]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
The removals in Bug 1188321 seem to have caused this issue.  Joel can you please take a look?
Blocks: 1188321
Flags: needinfo?(jmaher)
Thanks for looking into this Jayme.  The removals are testing only code.  Looking at the other commits, I would start with one of these two:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7333e869b284
https://hg.mozilla.org/integration/mozilla-inbound/rev/b5147ec24a77
Flags: needinfo?(jmaher)
QA Whiteboard: [QAnalyst-Triage?][severe] → [QAnalyst-Triage+][severe]
Flags: needinfo?(ktucker)
You need to log in before you can comment on or make changes to this bug.