Bug 912062 - Newer intel drivers cause a regression on i965 where the Firefox window is black
Summary: Newer intel drivers cause a regression on i965 where the Firefox window is black
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-17 14:59 UTC by Jean-François Fortin Tam
Modified: 2015-02-17 14:46 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:46:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jean-François Fortin Tam 2013-02-17 14:59:38 UTC
On a Fedora 18 machine, applying the recent updates will trigger a frequent situation where Firefox is just a big black rectangle, you cannot see the contents nor the window decorations. The Firefox process is responsive, you can quit it normally using GNOME Shell's overview's close buttons.

doing "yum downgrade x*-intel" makes the problem go away, so I can only guess that this is caused by the recent updates to the Intel driver in Fedora 18.



From lspci:


00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
	Subsystem: Dell Device 01da
	Flags: bus master, fast devsel, latency 0, IRQ 43
	Memory at fea00000 (32-bit, non-prefetchable) [size=1M]
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at ecb8 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Kernel driver in use: i915

00:02.1 Display controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02)
	Subsystem: Dell Device 01da
	Flags: bus master, fast devsel, latency 0
	Memory at feb00000 (32-bit, non-prefetchable) [size=1M]
	Capabilities: [d0] Power Management version 2

Comment 1 Adam Jackson 2013-02-20 13:33:56 UTC
(In reply to comment #0)

> doing "yum downgrade x*-intel" makes the problem go away, so I can only
> guess that this is caused by the recent updates to the Intel driver in
> Fedora 18.

And when you did this, what did you downgrade to and from?

Comment 2 Jean-François Fortin Tam 2013-02-20 17:03:18 UTC
xorg-x11-drv-intel.x86_64   2.21.2-1.fc18  is currently the newest available version (I'm just guessing it was that one 3 days ago?), while the currently installed package that does not exhibit the bug is version 2.20.14.

Comment 3 Jean-François Fortin Tam 2013-02-20 17:05:12 UTC
Ah yes, I see that "xorg-x11-drv-intel-2.21.2-1.fc18.x86_64.rpm" is present in /var/cache/yum/x86_64/18/updates/packages/, so that was probably the version that was causing problems.

Comment 4 Fedora End Of Life 2013-12-21 11:28:56 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Christophe Kassabji 2014-01-02 09:31:12 UTC
I could reproduce the problem with a Fedora 19 and xorg-x11-drv-intel-2.21.12-2.fc19.x86_64 drivers.

Comment 6 Fedora End Of Life 2015-01-09 17:41:29 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-02-17 14:46:52 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.