On Sat, Mar 24, 2007 at 04:29:23PM +0100, Julien Cristau wrote: > So you're saying the remaining problem is in graphicsmagick, not Xlib?
I recommend further testing and investigation by others. My analysis showed a clear bug in graphicsmagick, and I posted a fix for it. When I retested, only broken.xwd was fixed by that patch. So this bug may need to be cloned again, to separate broken.xwd and broken2.xwd. Either that, or someone can quickly come up with a proper fix to broken2.xwd, and close the pair out together. But I don't yet know whether that fix belongs in libx11 or graphicsmagick. - Larry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
