Version-Release number of selected component: lyx-2.0.5.1-1.fc18 Additional info: backtrace_rating: 4 cmdline: lyx crash_function: lyx::error_handler executable: /usr/bin/lyx kernel: 3.7.2-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 lyx::error_handler at LyX.cpp:683 #4 QHash<wchar_t, int>::findNode at /usr/include/QtCore/qhash.h:886 #5 value at /usr/include/QtCore/qhash.h:620 #6 lyx::frontend::GuiFontMetrics::width at GuiFontMetrics.cpp:236 #7 lyx::TextMetrics::rowWidth at TextMetrics.cpp:975 #8 lyx::TextMetrics::redoParagraph at TextMetrics.cpp:472 #9 lyx::BufferView::updateMetrics at BufferView.cpp:2650 #10 redraw at GuiWorkArea.cpp:450 #11 lyx::frontend::GuiWorkArea::redraw at GuiWorkArea.cpp:438 #12 lyx::frontend::TabWorkArea::on_currentTabChanged at GuiWorkArea.cpp:1670
Created attachment 683045 [details] File: backtrace
Created attachment 683046 [details] File: cgroup
Created attachment 683047 [details] File: core_backtrace
Created attachment 683048 [details] File: dso_list
Created attachment 683049 [details] File: environ
Created attachment 683050 [details] File: limits
Created attachment 683051 [details] File: maps
Created attachment 683052 [details] File: open_fds
Created attachment 683053 [details] File: proc_pid_status
Created attachment 683054 [details] File: var_log_messages
I took this report to lyx-devel mailing list. Additionally is there any other information that you could add such as what was the context where the crash occurred? What were you doing when this happened? Thank you.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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.
I have not seen any signs of this error after 2.0.6 release so I am closing the bug.