Re: Xnest crashes

[Alexander Gottwald <alexander dot gottwald at s1999 dot tu-chemnitz dot de>]

On Fri, 17 Sep 2004, Maarten Boekhold wrote:

> Hi all,
> 
> Xnest crashes for me directly after I try to start the first application 
> that connects to the specific display:
> 
> $ Xnest :1.0 -ac +kb
> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
> XFree86-Bigfont extension local-client optimization disabled due to lack 
> of shared memory support in the kernel
> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
> from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, 
> removing from list!
> cat: /home/Maarten/.Xauthority: No such file or directory
> XFree86-Bigfont extension local-client optimization disabled due to lack 
> of shared memory support in the kernel
> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
> from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, 
> removing from list!
> Segmentation fault (core dumped)

Unfortunatly not. I've just tried with 6.8.0 Xnest and remote xterm and had no
crash on client connect.

Maybe the colordepth is important. I'm running on 16 bit.

If I can not reproduce the bug the only solution is to use gdb and debug into 
Xnest and see where it crashes

bye
	ago 
-- 
 Alexander.Gottwald@s1999.tu-chemnitz.de 
 http://www.gotti.org           ICQ: 126018723