Bug 818977 - Incorrect rendering in F17
Incorrect rendering in F17
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Ben Skeggs
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2012-05-04 09:57 EDT by Mathieu Chouquet-Stringer
Modified: 2013-08-01 12:55 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 12:55:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
corrupted firefox screen (102.86 KB, image/png)
2012-05-04 09:57 EDT, Mathieu Chouquet-Stringer
no flags Details
Corrupted desktop (40.47 KB, image/png)
2012-05-04 10:01 EDT, Mathieu Chouquet-Stringer
no flags Details
Corrupted bugzilla output (rendered by firefox) (118.62 KB, image/png)
2012-05-10 12:17 EDT, Mathieu Chouquet-Stringer
no flags Details

  None (edit)
Description Mathieu Chouquet-Stringer 2012-05-04 09:57:34 EDT
Created attachment 582125 [details]
corrupted firefox screen

Description of problem:
On F17, I have rendering issues with the nouveau driver.

Corruptions are apparent on the desktop and also in firefox (cf attached picture).

Smolt profile is http://www.smolts.org/client/show/pub_7058659f-701c-45f0-9188-e9fa203e6d24

My graphic card is a NV37GL (nVidia Corporation NV37GL [Quadro PCI-E Series] (rev a2)) connected to a dual head config.

Version-Release number of selected component (if applicable):

How reproducible:
Strangely chromium doesn't have the problem.
Comment 1 Mathieu Chouquet-Stringer 2012-05-04 10:01:34 EDT
Created attachment 582127 [details]
Corrupted desktop
Comment 2 Mathieu Chouquet-Stringer 2012-05-09 04:37:06 EDT
Nevermind, I had forgotten I was running a Linus' kernel, I cannot reproduce this with the standard Fedora kernel.

So it is a kernel issue not a X11 one.
Comment 3 Mathieu Chouquet-Stringer 2012-05-10 12:16:43 EDT
Never mind, I get it too while on plain Fedora kernel (cf attached image).

I'm on 3.3.4-3.fc17.x86_64 but just saw there's a 3.3.4-4.fc17 available, I'll be trying it...
Comment 4 Mathieu Chouquet-Stringer 2012-05-10 12:17:54 EDT
Created attachment 583630 [details]
Corrupted bugzilla output (rendered by firefox)
Comment 5 Fedora End Of Life 2013-07-04 01:42:55 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 6 Fedora End Of Life 2013-08-01 12:55:27 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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.