Closed Bug 813230 Opened 12 years ago Closed 12 years ago

B2G desktop is busted

Categories

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

x86_64
Linux
defect

Tracking

(blocking-basecamp:+)

RESOLVED WORKSFORME
B2G C3 (12dec-1jan)
blocking-basecamp +

People

(Reporter: khuey, Assigned: dougt)

References

Details

Attachments

(1 file)

B2G desktop from the latest tip Gecko/Gaia boots up to a black screen, even after fixing bug 813045. This blocks me fixing Bug 811784 :-/
Fabrice and Chris, if you have some workaround for this, or know who can fix it, please let me know. This is making it really difficult for me to
Severity: normal → blocker
Priority: -- → P1
This makes it really difficult to do platform work specific for B2G (work for things that don't work on desktop, like bug 772365), especially since B2G emulator is broken too (based on khuey's recent attempts and my recent attempts). I talked to khuey and he said that he was trying it on Linux (not Windows as the bug metadata indicates), which is also what I'm using (Ubuntu 12.04 in VMWare, in my case). I did a bisect and the 2012-11-30 mozilla-central B2G desktop nightly works, and the 2012-12-02 desktop nightly doesn't work. I checked that the pre-built nightlies from the last few nights also don't work. Neither of my builds from mozilla-central nor mozilla-beta this weekend worked (tried several times). I always get the "mozilla" splash screen fading to a black screen. I think jduell said he was a getting a white screen.
OS: Windows 7 → Linux
Component: Gaia::Homescreen → General
If it's blocking dev work we might need to block on this.
blocking-basecamp: --- → ?
For packaged app signing, we're going to just do the testing manually and forgo the automated tests until I can get them working on the actual device or until we have a solution to this or the emulator bustage, so this is no longer blocking bug 772365.
No longer blocks: sign-packaged-apps
We need to fix this since it's killing developer productivity.
blocking-basecamp: ? → +
Progress! mozilla-inbound revision b1212b861665 (include patch in bug 819714) + gaia master revision cb1d3b76e39f9901b8cd5b4f002ab572842c39fe + gaia patch from bug 820554 + Ubuntu 12.04 (with system updates applied) + the following mozconfig: GAIADIR=/home/hacker/gaia mk_add_options MOZ_OBJDIR=../b2g-desktop mk_add_options MOZ_MAKE_FLAGS="-j6" ac_add_options --enable-application=b2g ac_add_options --disable-libjpeg-turbo ac_add_options --enable-tests = B2G desktop starts up and things mostly work. However, after some inactivity, the "screen" turns black and I could not figure out how to get it to stop being black. Restarting B2G desktop, this repeats over and over. I will now try an --enable-debug build.
Depends on: 820554
Presumably the progress came from bug 816957.
(In reply to Brian Smith (:bsmith) from comment #6) > Restarting B2G desktop, this repeats over and over. To clarify: I can boot to the unlock screen, unlocking the phone and navigating between pages and using the browser works, but after some inactivity the b2g desktop "screen" turns black and I have to restart the phone, which gets things working again starting at the unlock screen.
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #7) > Presumably the progress came from bug 816957. I built gaia without DEBUG=1 to avoid that bug.
(In reply to Brian Smith (:bsmith) from comment #9) > I built gaia without DEBUG=1 to avoid that bug. I did rm -Rf profile && DEBUG=1 make && ~/path/to/b2g-desktop-objdir/dist/bin/b2g-bin -profile $PWD/profile and that also is working with the same behavior.
Brian, if the screen turns black due to inactivity, just hit the [Home] key on your keyboard!
Attached image Strange iframe on top of everything (deleted) —
(In reply to Brian Smith (:bsmith) from comment #6) > I will now try an --enable-debug build. --enable-debug works too ... (In reply to Fabrice Desré [:fabrice] from comment #11) > Brian, if the screen turns black due to inactivity, just hit the [Home] key > on your keyboard! ... and this works too (silly me) ... and in the debug, after I used the [home] key to wake up the sleeping device, I experienced this strange iframe which is on top of all the content. Perhaps this is a feature too?
FWIW I'm seeing desktop working OK when built off on inbound, but hosed on beta (can't see any icons on screen after unlocking. Clicking in blank space where browser icon should be does launch browser, but screen still blank when I then hit "home". Right swipe also doesn't show apps.
(In reply to Jason Duell (:jduell) from comment #13) > FWIW I'm seeing desktop working OK when built off on inbound, but hosed on > beta (can't see any icons on screen after unlocking. Clicking in blank space > where browser icon should be does launch browser, but screen still blank > when I then hit "home". Right swipe also doesn't show apps. First, not b2g us using http://hg.mozilla.org/releases/mozilla-b2g18/ for the stable branch, not mozilla-beta. Second, I am not sure if the patches in the bugs that this bug depends on were uplifted to mozilla-b2g18 yet.
Is this still broken on beta?
Flags: needinfo?(jduell.mcbugs)
Yes. The fix has not been uplifted to b2g18. We need help tracking not-uplifted work.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #16) > Yes. The fix has not been uplifted to b2g18. What's the fix? Bug 816957? If so, that should really be blocking-basecamp+ (not this bug) since it has an owner, in which case the assignee/sheriff performs uplift once resolved. That's the only tracking issue I see here.
Flags: needinfo?(jduell.mcbugs)
(In reply to Alex Keybl [:akeybl] from comment #17) > (In reply to Chris Jones [:cjones] [:warhammer] from comment #16) > > Yes. The fix has not been uplifted to b2g18. > > What's the fix? Bug 816957? If so, that should really be blocking-basecamp+ > (not this bug) since it has an owner, in which case the assignee/sheriff > performs uplift once resolved. That's the only tracking issue I see here. bug 819714, bug 820554, and bug 816957 should all be uplifted.
Depends on: 816957
(In reply to Brian Smith (:bsmith) from comment #19) > (In reply to Alex Keybl [:akeybl] from comment #17) > > (In reply to Chris Jones [:cjones] [:warhammer] from comment #16) > > > Yes. The fix has not been uplifted to b2g18. > > > > What's the fix? Bug 816957? If so, that should really be blocking-basecamp+ > > (not this bug) since it has an owner, in which case the assignee/sheriff > > performs uplift once resolved. That's the only tracking issue I see here. > > bug 819714, bug 820554, and bug 816957 should all be uplifted. Bug 820554 is Gaia-side, the other two have checkin-needed on them. I'll see if these bugs would get picked up in our normal uplifts by sheriffs.
Depends on: 822088
Target Milestone: --- → B2G C3 (12dec-1jan)
Assignee: nobody → doug.turner
I can not reproduce w/ today's nightly build and a recent pull of gaia on the Mac. I ran the following commands: cd /Users/dougt/Desktop/B2G.app/Contents/MacOS ./b2g-bin -profile /Users/dougt/builds/gaia/profile nsm said he has a recent linux build and there isn't any problem. Marking WFM. Please reopen w/ str if this is still a problem.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: