I did some type of file conversion using Windows LyX 1.1.5 and I noticed an error message at the Dos prompt saying SIGSEGV signal caught; this is a LyX bug read helpfile. Later when I tried to bring up LyX it would not load. An error message something like display localhost:0.0 ; the descriptor is a file not a socket. I think this was caused by the SIGSEGV because when I did a search on sockets and errors there was a post relating this to SIGSEGV calls to the local x-server(x-win32) From: Kayvan A. Sylvan Subject: Re: Lyx just core dumped - how I fixed it Date: Mon, 20 Mar 2000 12:33:48 -0800 ---------------------------------------------------------------------------- ---- On Mon, Mar 20, 2000 at 08:04:32PM +0100, Enrique Perez-Terron wrote: > > A while ago I installed lyx-1.1.2-1.i386.rpm on my RedHat 6.0 or 6.1 (I do not > remember. Now I have replaced most, if not all the redhat rpms with the 6.1 > version.) Since then I could not start lyx, it just said "Segmentation fault > (core dumped)". It is almost certain, based on what you stated that your xforms version was a bad one for your libc version. As a general rule, a lyx core dump on startup is nearly always a system library problem (including the possibilites of bad xforms version, problems with the C library or X11 library problems). The xforms on ftp.sylvan.com works with RH 6.0 and RH 6.1, so you installed the right version for your system (which is why it now works). It seems to me some path or link has been broken because this was working fine. I did no configuration. Just this error message about SIGSEGV and now it sees a file not a socket. I dont know how to re-establish the linking originally setup. I have no LyX, no happiness. Regards, Stephen
