Bug 11938 - Text is drawn with red and blue channels swapped on ABGR hardware
Summary: Text is drawn with red and blue channels swapped on ABGR hardware
Status: RESOLVED DUPLICATE of bug 5212
Alias: None
Product: cairo
Classification: Unclassified
Component: xlib backend (show other bugs)
Version: 1.4.10
Hardware: SPARC NetBSD
: medium normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-10 22:08 UTC by Michael Lorenz
Modified: 2008-10-10 13:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Michael Lorenz 2007-08-10 22:08:31 UTC 
Text is drawn with red and blue channels swapped on ABGR hardware, like Sun ffb2+ graphics boards. I filed a bug report about that against Cairo 1.0 and it's been fixed - apparently it's back now.
Comment 1 Michael Lorenz 2007-08-10 22:53:44 UTC 
After some experimentation I found this:
- with anti-aliasing disabled text colours are right
- with anti-aliasing and sub-pixel hinting enabled colours are right too
- with anti-aliasing enabled but sub-pixel hinting disabled colours are wrong
Comment 2 Chris Wilson 2008-10-10 06:48:55 UTC 

*** This bug has been marked as a duplicate of bug 5112 ***
Comment 3 Mikhail Zabaluev 2008-10-10 08:14:39 UTC 
(In reply to comment #2)
> 
> *** This bug has been marked as a duplicate of bug 5112 ***

You most probably meant some other bug.
Comment 4 Michael Lorenz 2008-10-10 08:19:20 UTC 
Indeed.
By the way, I found that the problem may not be in cairo after all - there are still plenty of RGB vs. BGR problems in the Xserver's XRENDER code - half of it ( like rgb32 x a8 -> rgb32 )  assumes that source and destination pixmap always use the same pixel format which is clearly bogus.
Comment 5 Chris Wilson 2008-10-10 13:51:10 UTC 
I meant bug 5212, of which the cairo portion is a dup of. XRender only operates on surfaces of identical format and if cairo feed in argb32 x a8, then that would be a serious bug in cairo.

Thanks for checking.

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

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.