Bug 445064 - Windows map as cyan with compiz/i965
Summary: Windows map as cyan with compiz/i965
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 9
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Kristian Høgsberg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-03 05:44 UTC by Jonathan Blandford
Modified: 2013-04-02 04:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 18:08:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot of strange cyan tint in transparent window (386.28 KB, image/png)
2008-05-03 05:44 UTC, Carl Worth (Ampere)
no flags Details

Description Carl Worth (Ampere) 2008-05-03 05:44:57 UTC
I have no idea which component might actually have the bug here, (compiz,
X server, or intel driver). But after enabling desktop effects I'm seeing
undesired cyan in several places---it looks almost like initially mapped
windows are first appearing as cyan before getting the application-painted
contents.

The most objectionable place to see the effect is by clicking on the system
menus. There's definitely a flash of cyan before the fade-in begins. I
first noticed the problem after enabling DRI2, but it appears to exist
without that as well, (though much more subtle---perhaps it's just not
lasting as long).

I wasn't able to obtain a screenshot of the objectionable cyan flash.
But perhaps compiz is putting some cyan into transparent windows intentionally?

For example, in the screenshot here, the "Appearance Preferences" window
has some regions that are given a bit of a cyan tint, (while other portions
retain their original gray color). So perhaps that's related.

Also, there is some corruption of the image thumbnails in the dialog, but
I'll open a separate bug for that.

-Carl

Comment 1 Carl Worth (Ampere) 2008-05-03 05:44:57 UTC
Created attachment 304441 [details]
Screenshot of strange cyan tint in transparent window

Comment 2 Bug Zapper 2008-05-14 10:34:40 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-06-10 00:35:46 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-07-14 18:08:25 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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