Bug 24478

Summary:	[bisected] gwibber shows no profile image in intel 2.9.0
Product:	xorg	Reporter:	Matthias Hopf <mat>
Component:	Driver/intel	Assignee:	Chris Wilson <chris>
Status:	RESOLVED DUPLICATE	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	high
Version:	git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Matthias Hopf 2009-10-12 09:24:37 UTC

Long bug report in https://bugzilla.novell.com/show_bug.cgi?id=545499

In short:

gwibber doesn't show profile images with intel driver 2.9.0 any more.

The culprit was determined by bisecting as commit 57fc09c "Avoid fallbacks for a1 src/mask". Apparently, this adds a new rendering path that seems to break in this particular setting.

Currently we're just reverting the commit, I currently have no idea why the commit is breaking things.

Comment 1 Carl Worth 2009-10-26 11:30:21 UTC

Hi Matthias,

Thank you very much for the bug report, (particularly with a bisect result).

When a performance fix causes a rendering conformance regression that's a
problem. I'll re-assign this to Chris since the bisected commit is his.

-Carl

Comment 2 Chris Wilson 2009-10-26 14:14:55 UTC

Matthias, 2.9.1 contains a fix for that broken commit:

commit 7ccf084b7a281d8aa877f91401d3df7192da408c
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Oct 12 14:33:08 2009 +0100

    uxa: Free the ScratchPixmapHeader after its associated Picture
    
    Fixes: http://bugs.freedesktop.org/show_bug.cgi?id=24459
    Intel Driver > 2.8: Cairo rendering bug, triggered in QtCurve GTK engine
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    (cherry picked from commit 7e8f32d0a7279dce1976f87612833d9092554cfe)

Can you confirm that 2.9.1 fixes gwibber?

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

Comment 3 Matthias Hopf 2009-11-17 03:59:02 UTC

(In reply to comment #2)
> Can you confirm that 2.9.1 fixes gwibber?

I can confirm. Thanks a lot!

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.