Closed
Bug 944891
Opened 11 years ago
Closed 11 years ago
Firefox Metro won't get past splash screen on Windows 8.1
Categories
(Firefox for Metro Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 945829
People
(Reporter: flod, Unassigned)
Details
Nightly 28.0a1 (2013-11-29), Italian build, Win 8 Pro x64 Italian (virtualized)
Everything works fine.
Same build on my notebook with Windows 8.1 Pro x64 Italian, Firefox displays the blue "Firefox Nightly" splash screen and stop there, I can't even see it in the task manager when I go back to Desktop.
Tried with both my standard profile and a brand new one, same result (it doesn't matter if I start it from Windows Start screen or from inside Firefox desktop).
Updated•11 years ago
|
Blocks: metrov1backlog
Whiteboard: [triage]
Comment 1•11 years ago
|
||
This could be a duplicate of bug 945829 or bug 946797, or it could be something unrelated.
Do you have multiple Firefox profiles on the affected VM? If you temporarily move or rename the Mozilla folders from $HOME/AppData/Roaming and $HOME/AppData/Local and start with a fresh profile, do you get the same results?
You could also try running a debug nightly build to see if there is anything useful in the console logs.
Flags: needinfo?(francesco.lodolo)
Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Matt Brubeck (:mbrubeck) from comment #1)
> Do you have multiple Firefox profiles on the affected VM? If you
> temporarily move or rename the Mozilla folders from $HOME/AppData/Roaming
> and $HOME/AppData/Local and start with a fresh profile, do you get the same
> results?
I had 4 profiles, left only the main one and Metro starts.
Created a second profile, Metro hangs on the splash screen.
Removed check to "ask at startup" on the profile manager (keeping 2 profiles) and Metro starts, so it's definitely a dupe of bug 945829.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(francesco.lodolo)
Resolution: --- → DUPLICATE
Updated•11 years ago
|
No longer blocks: metrov1backlog
Whiteboard: [triage]
You need to log in
before you can comment on or make changes to this bug.
Description
•