Created attachment 30269 [details]
Problem with Intel driver 2.9 and QtCurve with cairo for arrows
As already reported to the Developer of the QtCurve Qt3/Qt4/GTK+ Engine, there is a bug in the intel driver > 2.8 causing rendering bugs together with cairo: Usually the arrows (used for submenus, scrollbars, ...) are drawn with cairo, using non anti-aliased lines. In that case the arrows are not drawn with intel > 2.9, but they are with Intel up to 2.8 or nvidia drivers. As soon as the lines are either antialiased or the arrows are drawn with GDK, this problem does not occur.
You can read a bit of discussion about it here:
or contact the QtCurve developer for additional information.
Steps to reproduce:
- Install and use the QtCurve GTK+ Engine < 0.69 (as 0.69 has a workaround)
- Install intel drivers > 2.8
- Restart X
- Open a GTK+ Application using arrows (almost every one)
Everything is drawn correctly.
All arrows (submenus, drop down lists, drop down boxes, scrollbar buttons, ...) are missing
Ubuntu Karmic (unfortunately all I have on a intel GPU machine)
2.6.31 Kernel on an x86 machine (Acer Aspire D150 netbook)
Intel driver 2.9 out of XSwat / Edgers PPA (which includes current git)
Intel Corporation Mobile 945GME
There is a screenshot attached. (problem with QtCurve, Intel 2.9)
I am quite sure that this is a intel driver bug, not a problem of QtCurve, as
1) It does not occur with Intel drivers up to (including) 2.8
2) It does not occur on different drivers (nvidia)
and not a Karmic problem, as it was reported on Debian as well.
If you need further information, just ask.
(As I am new to the freedesktop bugtracker, I might have missed something even though I read instructions)
Fixed with commit 7e8f32d0a7279dce1976f87612833d9092554cfe
Author: Chris Wilson <email@example.com>
Date: Mon Oct 12 14:33:08 2009 +0100
uxa: Free the ScratchPixmapHeader after its associated Picture
Intel Driver > 2.8: Cairo rendering bug, triggered in QtCurve GTK engine
Signed-off-by: Chris Wilson <firstname.lastname@example.org>
Thank you for the bug report.
That was quick.
Thanks for the quick reaction, I'll inform the QtCurve maintainer that he can remove the workaround for further QtCurve versions as major distributions provide updated drivers.
Thanks for the good support, kind regards
What about backporting it to 2.9 branch?
This fix was included with the 2.9.1 maintenance release - thanks.
*** Bug 24478 has been marked as a duplicate of this bug. ***