Version-Release number of selected component: lyx-2.1.0-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: lyx crash_function: lyx::error_handler executable: /usr/bin/lyx kernel: 3.14.3-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 lyx::error_handler at LyX.cpp:692 #4 ?? #5 QFactoryLoader::instance at plugin/qfactoryloader.cpp:276 #6 QIcon::addFile at image/qicon.cpp:843 #7 QIcon::QIcon at image/qicon.cpp:565 #8 ScalableEntry::pixmap at image/qiconloader.cpp:515 #9 QIconLoaderEngine::pixmap at image/qiconloader.cpp:528 #10 QIcon::pixmap at image/qicon.cpp:684 #11 QWidgetPrivate::setWindowIcon_sys at kernel/qwidget_x11.cpp:1490 #12 QWidget::create at kernel/qwidget.cpp:1534
Created attachment 896266 [details] File: backtrace
Created attachment 896267 [details] File: cgroup
Created attachment 896268 [details] File: core_backtrace
Created attachment 896269 [details] File: dso_list
Created attachment 896270 [details] File: environ
Created attachment 896271 [details] File: limits
Created attachment 896272 [details] File: maps
Created attachment 896273 [details] File: open_fds
Created attachment 896274 [details] File: proc_pid_status
Created attachment 896275 [details] File: var_log_messages
Hi Petr, do you remember what you were doing when this bug happened? Did this problem occurred other times? I am forwarding this to the lyx mailing list.
Another user experienced a similar problem: The problem appears when I started LyX at first time after starting Linux. Next time LyX started with no problems. I used LyX many times before and never encountered this problem. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: lyx crash_function: lyx::error_handler executable: /usr/bin/lyx kernel: 3.17.6-200.fc20.x86_64 package: lyx-2.1.2-1.fc20 reason: lyx killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days