Bug 215667 - Compiz (and Beryl) on PowerPC turn screen wonky-colored
Summary: Compiz (and Beryl) on PowerPC turn screen wonky-colored
Status: CLOSED DUPLICATE of bug 210760
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server (Show other bugs)
(Show other bugs)
Version: 6
Hardware: powerpc Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL: https://bugs.freedesktop.org/show_bug...
Depends On:
TreeView+ depends on / blocked
Reported: 2006-11-15 03:40 UTC by Jarod Wilson
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-15 06:22:08 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fix for wonky colors w/Compiz on PPC (406 bytes, patch)
2006-11-15 03:40 UTC, Jarod Wilson
no flags Details | Diff

Description Jarod Wilson 2006-11-15 03:40:37 UTC
Description of problem:
On PowerPC systems, enabling Compiz or Beryl turns the screen all wonky-colored (I'm told that's a 
technical term). Looks like a CRT with one of its color guns out. This has been reported upstream as 
well, complete with a patch to fix it:


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

I've got a test build underway with the attached patch (applied as #110), will report back when its built 
and tested...

Comment 1 Jarod Wilson 2006-11-15 03:40:37 UTC
Created attachment 141217 [details]
Fix for wonky colors w/Compiz on PPC

Comment 2 Jarod Wilson 2006-11-15 04:42:38 UTC
Okay, test build with this patch added fixes the wonky colors on my PowerBook G4.

Comment 3 Frank Arnold 2006-11-15 06:22:08 UTC
Thank you for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.

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

Note You need to log in before you can comment on or make changes to this bug.