lyx crashes with SIGSEGV signal caught

[Nico Bauer]

Binary package hint: lyx

i get the following error when i do anything in lyx

$ lyx
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/user/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
../../../../src/frontends/qt4/TocModel.cpp(268): type not found:
../../../../src/frontends/qt4/TocModel.cpp(358): type not found:
~/newfile1.lyx.emergency

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions in Help->Introduction and send us a bug report, if necessary. Thanks !
Bye.
Aborted

I am using Lyx 1.6.5 on Ubuntu 10.04 LTS and it crashes completely

ProblemType: Bug
Architecture: i386
Date: Fri Mar 19 11:30:09 2010
DistroRelease: Ubuntu 10.04
Package: lyx 1.6.5-1ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic-pae
SourcePackage: lyx
Uname: Linux 2.6.32-16-generic-pae i686

[Siméon Marijon (simeon-marijon)]

I've the same problem using ubuntu 10.04 64bit 2.6.32-21

[yeus (thomas-meschede-deactivatedaccount)]

that's right... But I only have the problem when inserting figure floats...

[Michael Curtis (michael-moltenmercury)]

This bug is also affecting me. Reproducible: always, simply create a new file and select Insert->Float->Figure. LyX will relaunch and recover with the float inserted (and is happy to copy and paste an existing float), so it seems to directly related to the GUI action.

Attached the first 24 stack frames from GDB backtrace. Also valgrind reports this:

==6244== Invalid read of size 4
==6244== at 0x819C641: lyx::TextMetrics::cursorY(lyx::CursorSlice const&, bool) const (TextMetrics.cpp:1776)

Seems like an array out of bounds or uninitialized memory bug.

[Michael Curtis (michael-moltenmercury)]

The following patch corrects the symptom (the crash itself), but not the cause (the cursor ends up in a funny position after inserting the Float, but at least LyX appears to work normally after this). I think the bounds check is important, however the real bug is elsewhere. Also this seems like it is an upstream bug (perhaps triggered by Ubuntu using the system provided Boost, rather than LyX's own).

Hopefully this helps someone triage or resolve the bug.

[Brian Thorne (hardbyte)]

I can confirm that the bug makes LyX entirely unusable. Also it doesn't exist in a recent build of LyX from SVN. Assuming patch has been applied upstream.

[karlrt (karlrt)]

Hi Thorney:

What was a recent SVN build back then? A 2.0 or still in the 1.6.* series?

@all
Perhaps you could try to reproduce in maverick with 1.6.7?

[Jean-Marc Lasgouttes (jmarc)]

AFAICS, his bug is related to Qt 4.6. It has been fixed in LyX 1.6.7 (and thus maverick meerkat)

http://www.lyx.org/trac/ticket/6680

The fix is here:
http://www.lyx.org/trac/changeset/34695

[Nico Bauer (oshelpdesk)]

yes, this is fixed in maverick with version 1.6.7.