Red Hat Bugzilla – Bug 862408
[abrt] lyx-2.0.4-1.fc17: lyx::Paragraph::getInset: Process /usr/bin/lyx was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-24 13:46:56 EDT
Description of problem:
Not sure how the crash happened (unable to reproduce). I was spellchecking a fairly simple document (language was Norwegian), and after ~20 replacements Lyx crashed when I double-clicked the correct suggestion.
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: lyx Rapport.lyx
:Thread no. 1 (10 frames)
: #0 lyx::Paragraph::getInset at Paragraph.cpp:3294
: #1 lyx::ParagraphMetrics::singleWidth at ParagraphMetrics.cpp:216
: #2 lyx::TextMetrics::cursorX at TextMetrics.cpp:1734
: #3 lyx::BufferView::coordOffset at BufferView.cpp:2783
: #4 lyx::BufferView::getPos at BufferView.cpp:2806
: #5 lyx::BufferView::cursorPosAndHeight at BufferView.cpp:2829
: #6 lyx::frontend::GuiWorkArea::showCursor at GuiWorkArea.cpp:583
: #7 QMetaObject::activate at kernel/qobject.cpp:3547
: #8 QObject::event at kernel/qobject.cpp:1157
: #9 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4551
Created attachment 620467 [details]
Created attachment 620468 [details]
Created attachment 620469 [details]
Created attachment 620470 [details]
Created attachment 620471 [details]
Created attachment 620472 [details]
Created attachment 620473 [details]
Created attachment 620474 [details]
Created attachment 620475 [details]
Created attachment 620492 [details]
Second, slightly different backtrace
Crashed again under the same circumstances (but different words, document position etc.), so I guess it is at least somewhat reproducible. Attached backtrace from second crash which is different, with the exception of frames 1 (lyx::ParagraphMetrics::singleWidth) and 2 (lyx::TextMetrics::cursorX).
Thanks for the report.
I will forward this report to lyx-devel in order to be fixed.
This bug seems to have been reported into lyx bugs:
I will track that bug and report as I have further details.
lyx-2.0.5 is in the testing-updates for F16, F17 and F18.
Please test if and see if the problem persists. Thank you.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.