Bug 216297

Summary: Compiz on AIGLX causes blue screen
Product: [Fedora] Fedora Reporter: Troels Just <tsuroerusu>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6CC: mcepl, wmirror
Target Milestone: ---Keywords: Patch
Target Release: ---   
Hardware: powerpc   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-27 15:23:01 UTC Type: ---
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
Patch that should fix this problem, which I ran into while researching this problem on different distros' bug-trackers.
none
My X.Org configuration file
none
My X.Org log file none

Description Troels Just 2006-11-18 23:45:59 UTC
Description of problem:
Because of an endianness bug in the AIGLX GLX_EXT_texture_from_pixmap
implementation, when running Compiz or Beryl the screen gets all blue.
This bug is fixed upstream.

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

How reproducible:
very easy to reproduce.

Steps to Reproduce:
1. Install the final version of Fedora Core 6 on a PowerPC machine.
2. Use the simple Desktop Effects tool to enable Compiz.
  
Actual results:
The screen gets a layer of blue added to it, which causes parts it to also get
pink and purple.

Expected results:
Compiz to just function normally, as it does on x86 and AMD64.

Additional info:
I ran into this problem on my PowerPC G4-based Mac mini, which uses a Radeon
9200 graphics chip. I know people with iBooks, also using the 9200 chip, have
also run into this problem.

Comment 1 Troels Just 2006-11-18 23:45:59 UTC
Created attachment 141572 [details]
Patch that should fix this problem, which I ran into while researching this problem on different distros' bug-trackers.

Comment 2 Matěj Cepl 2006-11-21 12:57:27 UTC
Thanks for the bug report.  We have reviewed the information you
have provided above, and there is some additional information we
require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X
server log file (/var/log/Xorg.*.log) to the bug report as individual
uncompressed file attachments using the bugzilla file attachment link
below.

We will review this issue again once you've had a chance to attach
this information.

Thanks in advance.

Comment 3 Troels Just 2006-11-21 13:24:42 UTC
Created attachment 141761 [details]
My X.Org configuration file

Comment 4 Troels Just 2006-11-21 13:25:59 UTC
Created attachment 141762 [details]
My X.Org log file

Comment 5 Troels Just 2006-11-21 13:37:05 UTC
(In reply to comment #2)
> Thanks for the bug report.  We have reviewed the information you
> have provided above, and there is some additional information we
> require that will be helpful in our diagnosis of this issue.
> 
> Please attach your X server config file (/etc/X11/xorg.conf) and X
> server log file (/var/log/Xorg.*.log) to the bug report as individual
> uncompressed file attachments using the bugzilla file attachment link
> below.
> 
> We will review this issue again once you've had a chance to attach
> this information.
> 
> Thanks in advance.

I have posted the files you requrested, I hope to have this fixed relatively
soon, because what's a presentation using a projector worth without a properly
working Compiz? :P

Comment 6 Francesco Ugolini 2006-12-04 21:18:55 UTC
I've the same problem with both iBook and Mac Mini with compiz and AIGLX too. I
hope that this problem can be solved (if you want i can attach myxorg confifg
and log).

Comment 7 Edward Rudd 2007-01-08 04:58:13 UTC
duplicate of #210760

Comment 8 Lionel H. 2007-01-14 18:42:35 UTC
I'm experiencing the same problem here on a mac mini.
I suppose that anyone running compiz on a ppc is facing this bug.

Comment 9 Adam Jackson 2007-03-27 15:23:01 UTC

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