Version-Release number of selected component: calibre-2.65.1-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: python2 /usr/bin/calibre --detach crash_function: QObject::disconnect executable: /usr/bin/python2.7 global_pid: 3641 kernel: 4.8.0-0.rc7.git0.1.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 QObject::disconnect at kernel/qobject.cpp:2956 #2 QDBusConnectionPrivate::closeConnection at qdbusintegrator.cpp:1133 #3 QDBusConnectionManager::run at qdbusconnection.cpp:206 #4 QThreadPrivate::start at thread/qthread_unix.cpp:344 Potential duplicate: bug 1330034
Created attachment 1203697 [details] File: backtrace
Created attachment 1203698 [details] File: cgroup
Created attachment 1203699 [details] File: core_backtrace
Created attachment 1203700 [details] File: dso_list
Created attachment 1203701 [details] File: environ
Created attachment 1203702 [details] File: exploitable
Created attachment 1203703 [details] File: limits
Created attachment 1203704 [details] File: maps
Created attachment 1203705 [details] File: mountinfo
Created attachment 1203706 [details] File: namespaces
Created attachment 1203707 [details] File: open_fds
Created attachment 1203708 [details] File: proc_pid_status
Created attachment 1203709 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
Yes. I can duplicate. It seems to occur when I shut down calibre. I do not have to do anything in it. So this really seems to be a duplicate of the previous calibre bug #1330034. But it keeps occuring even with the latest releases.
Yep. Which is in fact a QT bug.... will try and see if upstream can sort it out. Thanks. *** This bug has been marked as a duplicate of bug 1330034 ***