1064270 - Unabelled icons showing up on homescreen (empty collections?) when building/flashing with NOFTU=1

Status: RESOLVED WONTFIX

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

Description

[Kartikaya Gupta (email:[e-mail])]

I did a local build of the latest master code for Flame and when I boot it up I see three icons on the homescreen that have no labels. I believe they are empty collections or something, because when I click on them I get a collections-like screen except the collection has no name or icons in it. Clicking the "X" close button on that screen brings me back to the main homescreen.

Comment 1

[Kartikaya Gupta (email:[e-mail])]

Attachment: Screenshot

Comment 2

[Kartikaya Gupta (email:[e-mail])]

Hm, doing a |make reset-gaia| seems to have fixed this. Maybe there was non-backwards-compatible change made recently? I'll reopen if I see this again.

Comment 3

[Botond Ballo [:botond]]

I've sometimes seen this kind of behaviour when my Gaia gets too out of sync with my Gecko. Pulling both Gaia and Gecko and the same time and rebuilding tends to fix it.

Comment 4

[Kartikaya Gupta (email:[e-mail])]

I see this again after doing a full flash of a local build on top of whatever I had before (a build from a few days ago). Kevin, have you seen this too?

Comment 5

[Kevin Grandon :kgrandon]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #4)
> I see this again after doing a full flash of a local build on top of
> whatever I had before (a build from a few days ago). Kevin, have you seen
> this too?

Are you just doing a ./build.sh and a ./flash.sh? If so this should totally work.

The only thing that I can think of is if you've skipped FTU with some build flag, or maybe FTU has some bug.

Comment 6

[Kartikaya Gupta (email:[e-mail])]

Yeah, I'm doing ./build.sh && ./flash.sh. I do have export NOTFTU=1 in my .userconfig though.

Comment 7

[Kevin Grandon :kgrandon]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #6)
> Yeah, I'm doing ./build.sh && ./flash.sh. I do have export NOTFTU=1 in my
> .userconfig though.

Our current solution is to trigger the process from FTU, so this is what's causing it I believe =(

A better solution is probably to move this into the system app anyway. I don't think we'd get that into 2.1, but we can track that work here, or in another bug.

Comment 8

[Kartikaya Gupta (email:[e-mail])]

Might as well do it here. Thanks for explaining!

Comment 9

[Kevin Grandon :kgrandon]

Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.