Bug 559729 - Screen corruptions due to mesa update
Summary: Screen corruptions due to mesa update
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa-libGLw
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-28 20:41 UTC by António Lima
Modified: 2010-12-03 23:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:40:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg.conf (1022 bytes, application/octet-stream)
2010-01-28 20:42 UTC, António Lima
no flags Details
lspci-v (16.83 KB, text/plain)
2010-01-28 20:43 UTC, António Lima
no flags Details

Description António Lima 2010-01-28 20:41:55 UTC
Description of problem:

With the recent update to mesa 7.7.3 I started to have some screen corruptions when, for example, moving or resizing windows in my 22'' external monitor.

There are couple of conditions to make this happen with this screen:

1 - It only happens with KMS enabled;
2- Even with KMS enabled, if the laptop screen is also turned on, there are no corruptions;
3 - The screen resolution must be set to maximum: 1920x1080, otherwise I have no screen corruptions once more.

So, this happens with KMS + Full res + laptop screen OFF.

Note that I also have mesa-dri-drivers-experimental installed.

The screen is a Compaq Q2159.

I'm attaching xorg.conf and lspci -v.

Comment 1 António Lima 2010-01-28 20:42:28 UTC
Created attachment 387424 [details]
xorg.conf

Comment 2 António Lima 2010-01-28 20:43:02 UTC
Created attachment 387425 [details]
lspci-v

Comment 3 António Lima 2010-01-28 20:47:51 UTC
Forgot I had compiz running, disabling it made corruptions go away. This should be closed then? or moved to compiz?

Comment 4 António Lima 2010-01-28 20:55:55 UTC
Sorry about that, but with metacity with composite there are still some corruptions (some little black line while scrolling, with compiz the lines are much thicker and visible). With no composite they are apparently gone.

Comment 5 António Lima 2010-05-30 11:56:55 UTC
This is fixed in F13.

Comment 6 Bug Zapper 2010-11-03 23:40:13 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2010-12-03 23:40:19 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.