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).
Any idea who can look at the issue ?
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.
(In reply to comment #2)
> 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.
Oh ... (I always thought that the Damage work was done by your team...).
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
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.
Author: Adam Jackson <email@example.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.
Reviewed-by: Chris Wilson <firstname.lastname@example.org>
Reviewed-by: Eric Anholt <email@example.com>
Signed-off-by: Adam Jackson <firstname.lastname@example.org>