Closed Bug 594055 Opened 14 years ago Closed 14 years ago

After Installation, Firefox GUI is black

Categories

(Core :: Graphics, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Trevor.McAlear, Assigned: joe)

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b6pre) Gecko/20100907 Firefox/4.0b6pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b6pre) Gecko/20100907 Firefox/4.0b6pre

After I install the update, when Firefox reopens; the GUI (I think that is what it is called) is all black because of this I am not able to use the new build. I don't however get this problem when I install it on my PC, which has XP installed.

I have found away to make it usable again. My method is to reinstall an old Mindfield build and update it again. After doing so run your mouse until you find the 'organize your tabs' button and click on that. After doing so just click on the tab you wish to open and everything is back to normal.

Reproducible: Always

Steps to Reproduce:
1.Install
2.update
3.re-open
Actual Results:  
Check the steps 

Expected Results:  
Mindfield window is all black, showing nothing
I see this too, as does shaver.

When my minefield build starts up I get a black profile chooser window.  Never draws the window contents.

If I explicitly pick a profile (using -P <profile name>) it draws after a couple of seconds of being totally black.

Here's what I have in about:support

Adapter Description Mobile Intel(R) 4 Series Express Chipset Family
Vendor ID8086
Device ID2a42
Adapter RAM UnknownAdapter
Drivers igdumd64 igd10umd64 igdumdx32 igd10umd32
Driver Version 8.15.10.2119
Driver Date 4-21-2010
Direct2D Enabled false
DirectWrite Enabled false
GPU Accelerated Layers Enabled 2/2 Direct3D 9
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: General → Graphics
Product: Firefox → Core
QA Contact: general → thebes
I can reproduce this on Beltzner's Intel laptop. Currently installing some debugging tools on it.
Assignee: nobody → joe
I am also experiencing this: "-P" triggers this always (regardless of layers.accelerate-all).

"safe-mode" works around this.

about:support shows something odd:

  Graphics

        Adapter Description

        Vendor ID
        0000

        Device ID
        0000

        Adapter RAM
        Unknown

        Adapter Drivers
        Unknown

        Driver Version

        Driver Date

        Direct2D Enabled
        false

        DirectWrite Enabled
        false

      GPU Accelerated Windows
      0/1


This is Windows XP and a Intel(R) Q45/Q43 Express Chipset.
Driver version 6.14.10.5039

There is a newer driver available according to http://www.intel.com/support/graphics/detect.htm: 14.42.5.5284 (6.14.10.5284) - have/can not try it though.
Is this a DUPE of bug 594959?
Could also be a dupe of 593858
This is fixed for me since a long time already, and I suppose that it's fixed for the reporter, too?!
@Trevor: do you still have this problem?
(In reply to comment #6)
> This is fixed for me since a long time already, and I suppose that it's fixed
> for the reporter, too?!
> @Trevor: do you still have this problem?

That is correct, sorry, it is fixed for me as well; Thank you.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.