Bug 4862 - i815 driver mispaints KDE icons at 24 bpp - probably RENDER acceleration bug
Summary: i815 driver mispaints KDE icons at 24 bpp - probably RENDER acceleration bug
Status: RESOLVED DUPLICATE of bug 4152
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other other
: high normal
Assignee: Alan Hourihane
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-24 10:23 UTC by Bernhard Rosenkraenzer
Modified: 2005-10-24 08:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Screenshot demonstrating the problem (368.60 KB, image/png)
2005-10-24 10:25 UTC, Bernhard Rosenkraenzer 		no flags Details
View All

Description Bernhard Rosenkraenzer 2005-10-24 10:23:20 UTC 
On i815 w/ 24 bits per pixel, KDE's icons get misrendered.  
(Attaching a screenshot demonstrating the problem) 
 
Switching to 16 bits per pixel "fixes" the problem.
Comment 1 Bernhard Rosenkraenzer 2005-10-24 10:25:12 UTC 
Created attachment 3612 [details]
Screenshot demonstrating the problem
Comment 2 Alan Hourihane 2005-10-24 11:00:28 UTC 

*** This bug has been marked as a duplicate of 4152 ***
Comment 3 Bernhard Rosenkraenzer 2005-10-25 01:09:27 UTC 
This is not a dup of 4152:  
4152 is about the composite extension, which is turned off in the case of  
4862.  
4152 applies to all graphics cards, 4862 only to i815 (and possibly i810,  
don't have any to test); the same xorg that triggers 4152 here works perfectly  
on an ATI Radeon 9200 and 9600 with the same xorg.conf (with s/Driver 
"i810"/Driver "ati"/).
Comment 4 Alan Hourihane 2005-10-25 01:46:21 UTC 
you are wrong. Try starting the radeon with...

startx -- -pixmap24

and you'll see the same problem.

It's not the COMPOSITE extension either it's RENDER's use of it's own Composite
function.

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

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.