Bug 2454

Summary:	Xnest can't render text if a damage monitor is active
Product:	xorg	Reporter:	Jonathan Lennox <lennox>
Component:	Server/DDX/Xnest	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED FIXED	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	high	CC:	keithp, kem, roland.mainz
Version:	6.8.1
Hardware:	x86 (IA32)
OS:	FreeBSD
Whiteboard:	2011BRB_Reviewed
i915 platform:		i915 features:

Description Jonathan Lennox 2005-02-02 13:32:03 UTC

The Xnest server doesn't seem to work correctly with the Damage extension.

When a damage monitor is active -- i.e., following a call to XDamageCreate() --
any attempt to render text on the Xnest server fails with one of the messages

  xnest warning: function xnestImageGlyphBlt not implemented
  xnest warning: function xnestPolyGlyphBlt not implemented

No text is rendered to the screen.

After DamageDestroy is called, or the client which called DamageCreate closes,
text rendering returns to normal.

I am using version 6.8.1 of the X.org monolithic server, with the patch from
revision 1.4 of xc/programs/Xserver/dix/main.c applied (to prevent Xnest from
crashing on startup).

Comment 1 Roland Mainz 2005-02-06 18:18:01 UTC

Kevin:
Any idea who can look at the issue ?

Comment 2 Kevin E. Martin 2005-02-07 07:20:29 UTC

Roland: A question like this would be better sent to the xorg mailing list.  The
person who has done the most work on the Damage extension is Keith Packard.

Comment 3 Roland Mainz 2005-02-07 07:36:36 UTC

(In reply to comment #2)
> Roland: A question like this would be better sent to the xorg mailing list.

OK.

> The person who has done the most work on the Damage extension is Keith Packard.

Oh ... (I always thought that the Damage work was done by your team...).

Comment 4 Daniel Stone 2007-02-27 01:25:18 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 5 Jeremy Huddleston Sequoia 2011-10-08 23:59:29 UTC

Is this an issue still?  Can you try with Xephyr or xf86-video-nested?  Xnest 
is hopefully going to be removed "eventually" in favor of the nested driver.

Comment 6 Adam Jackson 2013-10-07 14:21:25 UTC

commit 0f3f8e4295d4c05f33b93e0ffd2f6f8cd5759bf7
Author: Adam Jackson <ajax@redhat.com>
Date:   Wed Aug 21 11:13:11 2013 -0400

    damage: Don't rewrite Text ops to GlyphBlt ops
    
    There's no particularly good reason to, and it breaks Xnest.
    
    Bugzilla: http://bugs.freedesktop.org/2454
    Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Adam Jackson <ajax@redhat.com>

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.