I can build LyX with the debug flag, but that will take a little while. In the meantime, here is another clue. When I run the lyx command in a terminal, it dumps a lot of text to the terminal when crashing. First, I get this repeated many times:
GuiToolbar.cpp(339): Session settings could not be found!. Defaults are used instead Then I get: Error returned from iconv EILSEQ An invalid multibyte sequence has been encountered in the input. When converting from UCS-4LE to UTF-8. Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 0x0 0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 ... lyx: SIGSEGV signal caught! Sorry, you have found a bug in LyX, hope you have not lost any data. Please read the bug-reporting instructions in 'Help->Introduction' and send us a bug report, if necessary. Thanks! Bye. Error: LyX crashed! ---------------------------------------- SIGSEGV signal caught! Sorry, you have found a bug in LyX, hope you have not lost any data. Please read the bug-reporting instructions in 'Help->Introduction' and send us a bug report, if necessary. Thanks! Bye. It dumps about 20MB of those hex codes to the terminal. When I run LyX as root or do "sudo lyx" I don't get any errors or warning messages. ________________________________ From: Pavel Sanda <[email protected]> To: [email protected] Sent: Tuesday, May 22, 2012 4:50 PM Subject: Re: LyX SEGSEGV crash just after GUI window appears Craig wrote: > Removing ~/.lyx does not change anything. It still crashes right away (note > that the window, buttons, etc are fully drawn and the file > examples/splash.lyx gets loaded before the SIGSEGV dialog box appears). Can you post backtrace when lyx is compiled with debug use flag? P
