Version-Release number of selected component: calibre-1.9.0-4.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre crash_function: g_main_context_check executable: /usr/bin/python2.7 kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (10 frames) #0 g_main_context_check at gmain.c:3603 #2 g_main_context_iteration at gmain.c:3774 #3 QEventDispatcherGlib::processEvents at kernel/qeventdispatcher_glib.cpp:425 #4 QGuiEventDispatcherGlib::processEvents at kernel/qguieventdispatcher_glib.cpp:207 #5 QEventLoop::processEvents at kernel/qeventloop.cpp:149 #6 QEventLoop::exec at kernel/qeventloop.cpp:204 #7 QCoreApplication::exec at kernel/qcoreapplication.cpp:1221 #8 QApplication::exec at kernel/qapplication.cpp:3823 #9 meth_QApplication_exec_ at sipQtGuiQApplication.cpp:2232 #10 call_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4098
Created attachment 857717 [details] File: backtrace
Created attachment 857718 [details] File: cgroup
Created attachment 857719 [details] File: core_backtrace
Created attachment 857720 [details] File: dso_list
Created attachment 857721 [details] File: environ
Created attachment 857722 [details] File: exploitable
Created attachment 857723 [details] File: limits
Created attachment 857724 [details] File: maps
Created attachment 857725 [details] File: open_fds
Created attachment 857726 [details] File: proc_pid_status
Created attachment 857727 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
Absolutely nothing - calibre wasn't even in foreground when this happened. An no, I cannot reproduce this at will though this isn't the first crash that happened to me with calibre in similar circumstances....
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.