Version-Release number of selected component: calibre-2.52.0-3.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre --detach crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 15146 kernel: 4.6.0-0.rc1.git0.3.fc25.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 QObject::disconnect at kernel/qobject.cpp:2949 #2 QDBusConnectionPrivate::closeConnection at qdbusintegrator.cpp:1126 #3 QDBusConnectionManager::run at qdbusconnection.cpp:191 #4 QThreadPrivate::start at thread/qthread_unix.cpp:340
Created attachment 1145367 [details] File: backtrace
Created attachment 1145368 [details] File: cgroup
Created attachment 1145369 [details] File: core_backtrace
Created attachment 1145370 [details] File: dso_list
Created attachment 1145371 [details] File: environ
Created attachment 1145372 [details] File: exploitable
Created attachment 1145373 [details] File: limits
Created attachment 1145374 [details] File: maps
Created attachment 1145375 [details] File: mountinfo
Created attachment 1145376 [details] File: namespaces
Created attachment 1145377 [details] File: open_fds
Created attachment 1145378 [details] File: proc_pid_status
Created attachment 1145379 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
I've also seen this crash (100% reproducible) since updating to Qt 5.6 with my PyQt application. I've now reported it upstream: https://bugreports.qt.io/browse/QTBUG-52988
Similar problem has been detected: I tried to close calibre after using it a few minutes reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre --detach crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 5499 kernel: 4.6.0-1.fc25.x86_64 package: calibre-2.56.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python2.7 killed by SIGSEGV reproducible: The problem is reproducible runlevel: N 5 type: CCpp uid: 1000
I can reproduce this now easily: 1) start calibre 2) quit calibre -> crash
Can you try: https://bodhi.fedoraproject.org/updates/FEDORA-2016-89ded4dc6a and see if it changes anything?
Still crashes with calibre-2.58.0-1.fc24
This seems to be the same thing as 1330034 but I have no idea why I am not seeing it here. ;(
Similar problem has been detected: After importing a few epub documents, updating the metadata, and converting them to mobi Calibre was sitting inactive in the background when it crashed without interaction. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre --detach crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 20131 kernel: 4.5.6-300.fc24.x86_64 package: calibre-2.58.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python2.7 killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: tried starting pdf shuffler before. there pyton complained about a missing library. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre-parallel crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 383 kernel: 4.5.5-300.fc24.x86_64 package: calibre-2.56.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python2.7 killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Possibly related: When Calibre crashed with the same error, it was also reporting MTP errors. I had USB devices attached that weren't mounted (Tablet in debug mode) Calibre does scan USB devices to look for ebook readers.
*** Bug 1358774 has been marked as a duplicate of this bug. ***
Similar problem has been detected: closed ebook viewer reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: python2 /usr/bin/ebook-viewer /home/newman/Documents/ebooks/nietzche-f_antikrist.mobi crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 8545 kernel: 4.6.4-301.fc24.x86_64 package: calibre-2.60.0-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python2.7 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1342296 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Read a text file and quit. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: python2 /usr/bin/ebook-viewer --detach /tmp/.fr-xSGjj2/libmypaint-1.3.0-beta.1/CODE_OF_CONDUCT.md crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 23944 kernel: 4.6.4-301.fc24.x86_64 package: calibre-2.60.0-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python2.7 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Appeared when I opened document (book) in E-book viewer. Application didn't crash, just this error appeared. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: python2 /usr/bin/ebook-viewer --detach '/home/zdenek/Documents/Funky.Koval/Funky-Koval-4---Wrogie-Przej\xc3\x84\xe2\x84\xa2cie---KOLOROWY-ALBUM---DODATKI-(2011).cbr' crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 21810 kernel: 4.6.4-301.fc24.x86_64 package: calibre-2.60.0-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python2.7 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: closing calibre reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 25948 kernel: 4.6.4-301.fc24.x86_64 package: calibre-2.60.0-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python2.7 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1404009 has been marked as a duplicate of this bug. ***
I've the same problem with calibre-3.1.1-1.fc26 and python 2.7.13-11. Since it is a duplicate, I'wont send a special bug report until someone will ask for this (the report was prepared but could not send, because I had no account in bugzilla at the occurence of the problem). I suggest the problem may be in the calibre program itself (e.g. using the wrong signal when cleaning subprocesses on exiting the program) and will try to contact the author of calibre too.
This is not a calibre bug - it's a Qt bug affecting many PyQt applications and fixed in Qt 5.9: https://bugreports.qt.io/browse/QTBUG-52988
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.