On Sun, Jun 13, 2004 at 11:29:11PM -0500, Branden Robinson wrote:
> On Thu, Jun 10, 2004 at 06:17:50PM -0400, Thomas Dickey wrote:
> > On Fri, May 28, 2004 at 10:27:16PM -0500, Branden Robinson wrote:
> > > 
> > > Okay, I will be patient while you explore this.

;-)

> > > Just as a remark to myself and my fellow "debian-x"ers, if it turns out
> > > the bug is in Xt, this bug should be reassigned to libxt6.
> > 
> > As far as I can determine, the bug is in the X libraries.  Running against
> > the XFree86 4.3.0 build tree, I can reproduce the bug.  Running against
> > XFree86 4.4.0 I cannot reproduce the bug.  This is independent of the
> > version of xterm, and since it appears to have been fixed in the later
> > X libraries indicates to me that it should be reassigned to libxt6.
> 
> Are you reasonably confident that it's Xt that has been fixed upstream
> or is that just a guess?  I.e., could it be Xlib insteaad?  Which way
> would you bet?

I narrowed it down by test-builds to the end of May 2003.  There's a
changelog entry which at that point stood out, and applying the fix to
my build tree seems to fix the bug we're discussing.  Here's the URL:

        http://bugs.xfree86.org/show_bug.cgi?id=315

(it's a file in Xlib)

-- 
Thomas E. Dickey <[EMAIL PROTECTED]>
http://invisible-island.net
ftp://invisible-island.net

Attachment: signature.asc
Description: Digital signature

Reply via email to