Bug 1727906

Summary: Graphics corruption with compiz and xorg-x11-server-*-1.20.5-3
Product: [Fedora] Fedora Reporter: M. Kristall <mkpdev>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 29CC: bskeggs, caillon+fedoraproject, jglisse, john.j5live, ofourdan, rhughes, rstrode, sandmann, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-08 14:16:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
This shows this graphics corruption with compiz (also shows bug #1725413) none

Description M. Kristall 2019-07-08 13:36:42 UTC 
Created attachment 1588362 [details]
This shows this graphics corruption with compiz (also shows bug #1725413)

Description of problem:
There is graphics corruption with compiz after updating to xorg-x11-server-*-1.20.5-3. This does not happen with xorg-x11-server-*-1.20.4-3

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

How reproducible:
100%

Steps to Reproduce:
1. dnf update -y
2. Log in

Actual results:
Graphics corruption

Expected results:
No graphics corruption

Additional info:
This only happens with compiz. The attached screenshot also shows bug #1725413 but I see the same graphics corruption with compiz-0.8.16.1-1
Comment 1 Olivier Fourdan 2019-07-08 13:59:57 UTC 
Which hardware/ driver?

There is a good chance this is a dupe of bug 1725499
Comment 2 M. Kristall 2019-07-08 14:16:53 UTC 
Oops, I didn't think to say about hardware or driver. I think you're right that it's a duplicate. I'm not sure why I couldn't find that one.

*** This bug has been marked as a duplicate of bug 1725499 ***