Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 573366 - Damage Processing issues when using compiz
Summary: Damage Processing issues when using compiz
Keywords:
Status: CLOSED DUPLICATE of bug 577142
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 577112 577473 (view as bug list)
Depends On:
Blocks: F13Target
TreeView+ depends on / blocked
 
Reported: 2010-03-14 12:47 UTC by drago01
Modified: 2018-04-11 14:33 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-20 12:53:46 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Xorg log (213.43 KB, text/plain)
2010-03-14 12:47 UTC, drago01 		no flags Details
View All

Description drago01 2010-03-14 12:47:08 UTC 
Description of problem:

When using compiz on F13 on a GM45 there are lots of weird redrawing issues.

One reproducer is the mouse configuration capplet, change to another tab seems to not have any effect, forcing a full screen redraw by switching workspaces lets it display the selected tab.

Reverting compiz to the F12 version does not fix it, so it is not a compiz issue, but a xserver / driver one.

Enabling the workarounds plugin which has an option to basically always call glxWaitX does not fix it.

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

xorg-x11-server-Xorg-1.7.99.901-8.20100223.fc13.x86_64
xorg-x11-drv-intel-2.10.0-4.fc13.x86_64
mesa-libGLU-7.8-0.18.fc13.x86_64
mesa-libGL-7.8-0.18.fc13.x86_64
mesa-dri-drivers-7.8-0.18.fc13.x86_64

How reproducible:

Always

Steps to Reproduce:
1. See above
  
Actual results:

No partial redrawing

Expected results:

No redrawing issues.
Comment 1 drago01 2010-03-14 12:47:48 UTC 
Created attachment 399975 [details]
Xorg log
Comment 2 Matěj Cepl 2010-03-19 12:32:52 UTC 
Could you elaborate please on this statement?

> Reverting compiz to the F12 version does not fix it, so it is not a compiz
> issue, but a xserver / driver one.

I don't get the same conclusion as you do apparently.

Just contrary, I see a lot of compiz issues on various drivers, so it seems to me that there could be something going on in the compiz itself.

Reassigning to compiz without a prejudice ... if compiz maintainers think this is driver issue, please, reassign to xorg-x11-drv-intel.

Thank you
Comment 3 drago01 2010-03-19 13:48:35 UTC 
(In reply to comment #2)
> Could you elaborate please on this statement?
> 
> > Reverting compiz to the F12 version does not fix it, so it is not a compiz
> > issue, but a xserver / driver one.
> 
> I don't get the same conclusion as you do apparently.
> 
> Just contrary, I see a lot of compiz issues on various drivers, so it seems to
> me that there could be something going on in the compiz itself.

Well that does not make sense at all ... 

I said reverting to a _known working_ compiz version (the one shipped in F12) does NOT fix the issue.

So how is this a bug triggered by a compiz change?

Also which issues are you referring too?

> Reassigning to compiz without a prejudice ... if compiz maintainers think this
> is driver issue, please, reassign to xorg-x11-drv-intel.

Well I doubt that the intel driver is to blame either ... because the same version is working fine on F12 (2.10.0) ... so it is either a mesa or xserver bug.
Comment 4 drago01 2010-03-19 14:29:32 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > Could you elaborate please on this statement?
> > 
> > > Reverting compiz to the F12 version does not fix it, so it is not a compiz
> > > issue, but a xserver / driver one.
> > 
> > I don't get the same conclusion as you do apparently.
> > 
> > Just contrary, I see a lot of compiz issues on various drivers, so it seems to
> > me that there could be something going on in the compiz itself.
> 
> Well that does not make sense at all ... 
> 
> I said reverting to a _known working_ compiz version (the one shipped in F12)
> does NOT fix the issue.
> 
> So how is this a bug triggered by a compiz change?
> 
> Also which issues are you referring too?
> 
> > Reassigning to compiz without a prejudice ... if compiz maintainers think this
> > is driver issue, please, reassign to xorg-x11-drv-intel.
> 
> Well I doubt that the intel driver is to blame either ... because the same
> version is working fine on F12 (2.10.0) ... so it is either a mesa or xserver
> bug.    

Reverting to F12's mesa fixes it.
Comment 5 Adel Gadllah 2010-03-26 11:30:41 UTC 
*** Bug 577112 has been marked as a duplicate of this bug. ***
Comment 6 Adel Gadllah 2010-03-27 12:04:45 UTC 
*** Bug 577473 has been marked as a duplicate of this bug. ***
Comment 7 Adel Gadllah 2010-04-17 13:24:59 UTC 
This is still present with mesa-7.8.1-1 and xorg-x11-drv-intel-2.11.0-1
Comment 8 Adel Gadllah 2010-04-20 11:17:49 UTC 
*** Bug 583904 has been marked as a duplicate of this bug. ***
Comment 9 pankaj pandey 2010-04-20 12:43:47 UTC 
This issue seems to be same as bug #577142 so probably can be marked as duplicate of that.
Comment 10 Adel Gadllah 2010-04-20 12:53:46 UTC 
(In reply to comment #9)
> This issue seems to be same as bug #577142 so probably can be marked as
> duplicate of that.    

Thanks for pointing this out, the bug you linked to also seems to have link to an upstream bug report with a proposed fix.

*** This bug has been marked as a duplicate of bug 577142 ***
Note You need to log in before you can comment on or make changes to this bug.