Closed
Bug 978997
Opened 10 years ago
Closed 10 years ago
[B2G] Stuck on FTE screen after flashing or reset - "Next" button is unresponsive. Multiple reboots can fix the issue.
Categories
(Core :: Layout, defect)
Tracking
()
People
(Reporter: nkot, Assigned: botond)
References
Details
(Keywords: regression, smoketest)
Attachments
(2 files)
170.15 KB,
text/plain
|
Details | |
1.97 KB,
patch
|
tnikkel
:
review+
|
Details | Diff | Splinter Review |
Description: Stuck on FTE screen after flashing to the master build or after resetting device. Pulling the battery out or restarting device from reboot menu fixes the issue. Have to restart multiple times - up to 10-12 times. Repro Steps: 1) Flash Buri to BuildID: 20140303114510 2) Run FTE Actual: Stuck on first FTE page, "Next" is unresponsive Expected: Able to run through FTE after flashing (or resetting) Environmental Variables: Buri master (1.4) build, Mozilla RIL BuildID: 20140303114510 Gaia: dfae3744607257206e37483dc3f431108baf70fb Gecko: c8bea55437c1 Version: 30.0a1 Firmware Version: v1.2-divices.cfg Repro frequency: 100%
Updated•10 years ago
|
blocking-b2g: --- → 1.4?
Keywords: regression,
regressionwindow-wanted
Reporter | ||
Comment 1•10 years ago
|
||
seems like it's not just FTE - even after passing FTE we're getting stuck in any apps (camera, clock) - buttons are unresponsive!
Updated•10 years ago
|
QA Contact: pbylenga
Comment 2•10 years ago
|
||
I was getting this yesterday - my logcat looked like: https://pastebin.mozilla.org/4452051 But TBPL buri runs aren't broken (afaict) so I thought it was just me. I tried earlier nightly builds - I had to go back to 20140228160203 which is the latest build that worked for me.
Comment 3•10 years ago
|
||
Also I constantly getting notifications that "App X has crashed", are you seeing this too?
Comment 4•10 years ago
|
||
Logcat attached. Note that once the phone restarts and I am in FTU the device disconnects so I cannot get a logcat. What is posted here is when the phone has finished flashing and is starting up.
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Paul Theriault [:pauljt] from comment #3) > Also I constantly getting notifications that "App X has crashed", are you > seeing this too? I guess you're hitting bug 978450 here, I don't see it on today's build.
Comment 6•10 years ago
|
||
(In reply to Natalya Kot [:nkot] from comment #5) > (In reply to Paul Theriault [:pauljt] from comment #3) > > Also I constantly getting notifications that "App X has crashed", are you > > seeing this too? > > I guess you're hitting bug 978450 here, I don't see it on today's build. I think you mean today's respun build. This was reproducing on the first build of the day.
Reporter | ||
Comment 7•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #6) > (In reply to Natalya Kot [:nkot] from comment #5) > > (In reply to Paul Theriault [:pauljt] from comment #3) > > > Also I constantly getting notifications that "App X has crashed", are you > > > seeing this too? > > > > I guess you're hitting bug 978450 here, I don't see it on today's build. > > I think you mean today's respun build. This was reproducing on the first > build of the day. Correct. BuildID: 20140303114510 Gaia: dfae3744607257206e37483dc3f431108baf70fb Gecko: c8bea55437c1 Version: 30.0a1
mozilla-central, mozilla-inbound, and b2g-inbound (but not fx-team) are now closed for this as of 2014-03-03T15:35:13 This really needs to be figured out and dealt with ASAP. :)
Severity: normal → blocker
Comment 9•10 years ago
|
||
Note: this is most likely a gecko regression. If I flash gaia master with BuildID 20140221160204, I push "Next" in the FTU with no problems.
Updated•10 years ago
|
Severity: blocker → normal
Updated•10 years ago
|
Severity: normal → blocker
Comment 10•10 years ago
|
||
We've confirmed this is reproducing on the March 1st build. There's some intermittent behavior seen on 2/28, so we're still trying to determine when it failed in that timeframe.
Comment 11•10 years ago
|
||
We've narrowed the issue down between two 2/28 tinderbox builds. Still working on getting more info. 20140228054330 first broken 20140228053232 last working
Comment 12•10 years ago
|
||
What tree are you bisecting on? On m-c, in that range, the following gonk changes also occurred: { "repo": "http://git.mozilla.org/?p=external/caf/quic/lf/b2g/build.git", "/home/jgriffin/newer.xml": "6d90df25658d59dfcfd34f83e74e75c3af3901af", "/home/jgriffin/older.xml": "43829d56fab6ad16883f1ac9f55ffb9aa5863543", "commits": [ { "commit": "Merge \"gecko: widget: gonk: Add ro.sf.lcd_density DPI... ", "author": "Linux Build Servic... ", "revision": "6d90df25658d59dfcfd34f83e74e75c3af3901af" }, { "commit": "gecko: bluetooth: Update callbacks to match bluetooth.h", "author": "Greg Grisco", "revision": "313237de894ffd0bfb18c7342e7e2cee74f0355a" }, { "commit": "gecko: widget: gonk: Add ro.sf.lcd_density DPI override", "author": "Michael Vines", "revision": "41a840b405485babc19851b276cd6987d94dfe96" }, { "commit": "Allow linting of js files without including them in... ", "author": "Philippe Gravel", "revision": "43829d56fab6ad16883f1ac9f55ffb9aa5863543" } ] },
Comment 13•10 years ago
|
||
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5acf5aefe27a&tochange=53dbf19f2f8d
Comment 14•10 years ago
|
||
Found the cause - it's bug 959847.
Updated•10 years ago
|
Component: General → Layout
Product: Firefox OS → Core
Version: unspecified → Trunk
Assignee | ||
Comment 15•10 years ago
|
||
Attachment #8384999 -
Flags: review?(tnikkel)
Updated•10 years ago
|
Attachment #8384999 -
Flags: review?(tnikkel) → review+
Comment 16•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f1c7a2d5545e
Assignee: nobody → botond
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Reporter | ||
Comment 18•10 years ago
|
||
Verified Fixed. The issue no longer reproduces on the 03/04 master build - "Next" button works in FTU. BuildID: 20140304040200 Gaia: 6df4533f14ec2645bb13d8a803a5151583ca13a8 Gecko: 529b86b92b1d Version: 30.0a1 v1.2-devices.cfg
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
status-b2g-v1.4:
--- → fixed
status-firefox28:
--- → wontfix
status-firefox29:
--- → wontfix
status-firefox30:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•