Closed Bug 911171 Opened 6 years ago Closed 6 years ago

Booting up unagi with latest master returns JavaScript Error: "TypeError: elem is null" {file: "app://"


(Firefox OS Graveyard :: General, defect, critical)

Gonk (Firefox OS)
Not set


(Not tracked)



(Reporter: Bebe, Unassigned)



(Keywords: regression, smoketest)


(2 files)

1. Flash latest build
2. start a logcat and boot up the device

2. The device boots up as expected

2: The device returns 
E/GeckoConsole(  110): [JavaScript Error: "TypeError: elem is null" {file: "app://" line: 67}]

Gaia  407fbfb6a9de68ec4db2f0f3dc6c67463e293f47
BuildID 20130830040204
Version 26.0a1
This is blocking Gaia-UI automation

All our tests are failing because of this issue
Changing the bug to critical
Severity: normal → critical
Exact logcat issue:

E/Profiler(  328): Registering start signal
I/InputReader(  110): Reconfiguring input devices.  changes=0x00000004
I/InputReader(  110): Device reconfigured: id=7, name='atmel-touchscreen', surface size is now 320x480, mode is 1
E/GeckoConsole(  110): [JavaScript Error: "TypeError: elem is null" {file: "app://" line: 67}]
I/Gecko   (  110): -*- WifiWorker component: detected SDK version 15
E/GeckoConsole(  110): [JavaScript Error: "callback is undefined" {file: "jar:file:///system/b2g/omni.ja!/components/RILContentHelper.js" line: 1760}]
I/Gecko   (  110): -*- WifiWorker component: State change: INITIALIZING -> INACTIVE
I/Gecko   (  110): -*- WifiWorker component: Connected to supplicant
I/Gecko   (  110): -*- WifiWorker component: Got mac: 48:28:2f:f9:be:07
Summary: Booting up unagi with latest master returns JavaScript Error: "TypeError: elem is null" → Booting up unagi with latest master returns JavaScript Error: "TypeError: elem is null" {file: "app://"
The last know good build is:

Gaia   98b82e7574d52ba331add18c617e08d8784ccf4a
BuildID 20130829040202
Version 26.0a1
The JS error is coming from changes seen in bug 900838.

John - Can you backout the above commit?

Note - Apparently I don't have access to bug 900838, so I can't comment in that bug.
Flags: needinfo?(jhford)
There also seems to be a problem with the desktop build. I am not getting any JavascriptExceptions, but when the b2g app launches nothing appears on the monitor. Tests still pass, but nothing appears on the screen.
I replicated the issue with the B2G desktop client and attach a screenshot (I was unable to copy/paste for for some reason). This is not the same error but may be related.
Backed out in

Closing as fixed by backout. Leaving needinfo though on Rex, cause I need him to reopen the associated bug in question per the backout (I don't have access). Could you cc me on that bug also?
Closed: 6 years ago
Flags: needinfo?(jhford)
Resolution: --- → FIXED
Also - Can you cc jhford on the associated bug?
CC'ed Jason and John on bug 900838.

The bug is still waiting for landing Gecko part, but seems the error message
is unrelated with that. I guess the error message should be some cases
I didn't considered..

I did reproduced the error message, but I can still boot normally. So I'll
first try to eliminate the error, but since I'm not sure whether just
eliminating the error solves the problem, is there any document or instruction
that I can ensure after finishing the patch?
Flags: needinfo?(rexboy)
updated the patch.
This should be fine I guess.. I'll merge it after confirming it doesn't cause
regression again.
This was fixed with build:

Thanks for the help all
I've raised bug 911751 for the desktop client issue, which I believe to be unrelated.
You need to log in before you can comment on or make changes to this bug.