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. ** Patch added: "lyx_cursor_bounds_check.patch" http://launchpadlibrarian.net/45637849/lyx_cursor_bounds_check.patch -- lyx crashes with SIGSEGV signal caught https://bugs.launchpad.net/bugs/541787 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
