813900 - Cannot use the device because of a black 'mozilla' screen over the homescreen

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::System, defect, P1)

Description

[Fabien Cazenave [:kaze]]

Attachment: workaround

Latest Gaia & Gecko 18 build. When I start my Otoro, I can see the homescreen very briefly before the black 'mozilla' screen covers it, thus making the phone unusable.

A quick and dirty workaround is to hide the #initlogo element, see attachment.

Comment 1

[Gordon Brander :gordonb]

The regression appears sometime after 01dce6b0559eacbe9546f2f59105ad78c6020e30.

Comment 2

[Borja Salguero [:borjasalguero]]

I've tried 10 times in my Otoro and this bug is not happening... I've made:
- make reset-gaia (1)
- see 'mozilla logo black screen' disappears, FTU appears
- Run FTU
- Restart again
- Check that everything works properly.
- Go agan to (1)

Comment 3

[Fabien Cazenave [:kaze]]

Then please use a desktop build, it's much easier to reproduce. All our l10n contributors are complaining about that: as you can guess, it's a complete blocker for them.

Comment 4

[Staś Małolepszy :stas]

I heard about this issue as well, but I can't seem to reproduce.  I've tried gecko 18, 19 and 20 desktop builds.

Comment 5

[Borja Salguero [:borjasalguero]]

I've tried with the following:
Desktop build: b2g-20.0a1.en-US.mac64
Gaia: 61fe3087657b27dae854fc2da811c7f2092cb25f

It was impossible for me to reproduce it.

Comment 6

[Etienne Segonzac (:etienne)]

Driving me crazy, stealing the bug :)

Comment 7

[Borja Salguero [:borjasalguero]]

Thanks [:etienne], because I've tested a lot of times with B2G-18 (downloaded from http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-aurora/) and in my Mac it's impossible to reproduce :S :S :S (I've tested with B2G-19 & B2G-20 as well, and no black screen...)

Comment 8

[Etienne Segonzac (:etienne)]

Attachment: Patch proposal

Comment 9

[Etienne Segonzac (:etienne)]

https://github.com/mozilla-b2g/gaia/commit/8dc07da79c145e9b6cc417fb630954dc2f0b6e8a

Comment 11

[Misty Byrd]

This issue fixed for  device Ungia; build #20130103070201 v.1