Closed
Bug 1046325
Opened 10 years ago
Closed 7 years ago
"./run-emulator.sh" just produces a white screen
Categories
(Firefox OS Graveyard :: Emulator, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: botond, Unassigned)
Details
Attachments
(1 file)
(deleted),
text/x-log
|
Details |
I'm having a problem with the B2G emulator where it just shows a white screen after I run it with "./run-emulator.sh".
Running reftests via "./mach reftest-remote" works fine.
Attached is the logcat from the emulator.
One thing that's suspicious is that "adb shell b2g-ps" shows:
APPLICATION SEC USER PID PPID VSIZE RSS WCHAN PC NAME
b2g 0 root 44 1 124100 58064 ffffffff 400713c0 S /system/b2g/b2g
Mochitest 2 app_143 143 44 79720 31192 ffffffff 400713c0 S /system/b2g/plugin-container
even though I never asked it to run mochitests.
Any suggestions for how to diagnose the problem further are appreciated.
Reporter | ||
Updated•10 years ago
|
Attachment #8464941 -
Attachment description: emulator-whitescreen.log → adb logcat
Comment 1•10 years ago
|
||
I had the black screen for a while, while trying to run the B2G emulator.
I used an Ubuntu12 VM image, when I started using an Ubuntu 14 image, I didn't have that problem anymore.
Some time ago, I posted this problem also on dev-b2g, I got 1 response from Armen Zambrano:
"
I think I had this same issue a while ago.
I'm not sure that this is what it fixed it but what I did is to switch
from the open source drivers to the Nvidia proprietary drivers.
To get there (on Ubuntu 13.10):
* System Settings
* Software & Updates
* Additional drivers
I hope it was this what I did to make it work and it helps you.
"
I also made a mention in that thread, that closing the emulator window, while running mochitest-remote, seems to cause problems rerunning mochitest-remote. Doing a ./build.sh seemed to fix the problem.
Anyhow, maybe one of these things might help you.
Comment 2•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•