Frank Schmitt wrote:
Sasha Vasko <[EMAIL PROTECTED]> writes:
Frank Schmitt wrote:
Marc Lehmann <[EMAIL PROTECTED]> writes:
So I think this really looks like some AfterImage bug.
Yeah, there have been similar issues in the past, but multi-display mode
isn't exercised much, and the codepaths used by rxvt-unicde have probably
been fixed.
Yes, I think I found the bug in libAfterImage (at some point dpy instead
of asv->dpy is accessed, where asv is the asvisual struct and dpy the
global variable)
Now that 9.06 is released with that patch, could you maybe notify the
fedora maintainer of this issue?
Yes, I'll do. I also reported the bug to the libAfterImage maintainer
yesterday, if he agrees that I indeed found the bug, the patch is a
trivial two liner.
Frank,
I did not get anything from you. Where was that bug that you found?
I was not able to reproduce the crash with the current CVS of libAfterImage.
I send the following mail to [EMAIL PROTECTED] and the logs of my
mail server say that it went out correctly. I also didn't get a bounce.
Maybe you don't have "HAVE_GLX" set?
<snip>
I use libAfterImage-1.18, dynamically linked, unchanged Fedora 9 packages.
The corresponding lines in asvisual.c reads
#ifdef HAVE_GLX
if( asv->glx_scratch_gc_direct )
glXDestroyContext(dpy, asv->glx_scratch_gc_direct );
if( asv->glx_scratch_gc_indirect )
glXDestroyContext(dpy, asv->glx_scratch_gc_indirect );
#endif
and I guess this should really be
#ifdef HAVE_GLX
if( asv->glx_scratch_gc_direct )
glXDestroyContext(asv->dpy, asv->glx_scratch_gc_direct
);
if( asv->glx_scratch_gc_indirect )
glXDestroyContext(asv->dpy,
asv->glx_scratch_gc_indirect );
#endif
Yours,
Frank
Ok, the mistery's solved. Fedora package maintainers did something silly
and enabled experimental support for GLX, which is useless and does not
work, and I'll probably remove it altogether.
It is disabled by default.
Sasha Vasko
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode