Bug 53630

Summary: compiz + glamor = screen corruptions
Product: DRI Reporter: Thomas Rohloff <v10lator>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg ouput while compiz loads
none
Desktop without glamor (good rendering)
none
Desktop with glamor (bad rendering)
none
Compiz loading none

Description Thomas Rohloff 2012-08-17 07:37:29 UTC
Created attachment 65668 [details]
dmesg ouput while compiz loads

I get screen corruptions when starting compiz while GLAMOR acceleration is enabled. The desktop shows random white bars at the desktop right after loading. These bars can be removed by refreshing the desktop (re-setting the desktop background in XFCE).
While compiz loads the attached log shows up in dmesg.
Comment 1 Thomas Rohloff 2012-08-17 09:53:47 UTC
Created attachment 65683 [details]
Desktop without glamor (good rendering)
Comment 2 Thomas Rohloff 2012-08-17 09:55:05 UTC
Created attachment 65685 [details]
Desktop with glamor (bad rendering)
Comment 3 Thomas Rohloff 2012-08-17 09:58:29 UTC
Created attachment 65687 [details]
Compiz loading

As you see here (and at the screenshots) the colors are wrong, too (red to blue, for example).
I tried to get the same corruption I described earlier, but was unable to do so (well, it's basically the same but without the wrong colors).
Comment 4 Michel Dänzer 2012-08-17 10:10:45 UTC
Does this still occur with the kernel fix from bug 45018?
Comment 5 Thomas Rohloff 2012-08-17 10:25:00 UTC
(In reply to comment #4)
> Does this still occur with the kernel fix from bug 45018?
Yes.
Comment 6 Michel Dänzer 2012-09-19 12:43:15 UTC
Mesa Git commit 73dd82061e7a5242c88b529c274784731462e039 ('winsys/radeon: create only one winsys for each fd') and/or kernel commit http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-3.7-wip&id=ac266e8d6065383d1c1b71bfae1a87474af760c2 might help at least for the messages in dmesg.
Comment 7 Thomas Rohloff 2013-12-04 18:39:24 UTC
I guess this is fixed (but can't tell for sure as I'm no longer using compiz).

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.