Description of problem: This bug happens randomly after calibre is closed. Version-Release number of selected component: calibre-2.23.0-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre --detach crash_function: QNetworkConfigurationManagerPrivate::pollEngines executable: /usr/bin/python2.7 kernel: 3.18.7-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1002 var_log_messages: [System Logs]:\n-- Logs begin at Fri 2015-04-17 15:31:28 CST, end at Tue 2015-04-21 19:46:29 CST. -- Truncated backtrace: Thread no. 1 (10 frames) #0 QNetworkConfigurationManagerPrivate::pollEngines at bearer/qnetworkconfigmanager_p.cpp:489 #1 QNetworkConfigurationManagerPrivate::qt_static_metacall at .moc/moc_qnetworkconfigmanager_p.cpp:128 #2 QMetaObject::activate at kernel/qobject.cpp:3716 #4 QTimer::timeout at .moc/moc_qtimer.cpp:192 #5 QTimer::timerEvent at kernel/qtimer.cpp:247 #6 QObject::event at kernel/qobject.cpp:1267 #7 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3720 #8 QApplication::notify at kernel/qapplication.cpp:3503 #9 sipQApplication::notify at sipQtWidgetsQApplication.cpp:349 #10 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:935
Created attachment 1016898 [details] File: backtrace
Created attachment 1016899 [details] File: build_ids
Created attachment 1016900 [details] File: cgroup
Created attachment 1016901 [details] File: core_backtrace
Created attachment 1016902 [details] File: dso_list
Created attachment 1016903 [details] File: environ
Created attachment 1016904 [details] File: exploitable
Created attachment 1016905 [details] File: limits
Created attachment 1016906 [details] File: maps
Created attachment 1016907 [details] File: open_fds
Created attachment 1016908 [details] File: proc_pid_status
Interesting. Does it happen right after you quit? Or takes a while?
As far as I can tell, it's about several seconds when ABRT appears after I close Calibre. I guess this can be called 'right after'.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.