Bug 1378433

Summary: [abrt] calibre: QObject::disconnect(): python2.7 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mikko Tiihonen <mikko.tiihonen>
Component: calibreAssignee: Kevin Fenzi <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: chkr, david, helio, info, kevin, mithrial, nobody+PNT0342590-1, nushio, pzeppegno, ral, rosset.filipe, sysoutfran, thanosk, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d01a281cde4188733c69d69ef803beb6c71119b6
Whiteboard: abrt_hash:76e3289c3b30541a3f9cc51b123e3be1458d8441;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-25 00:21:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mikko Tiihonen 2016-09-22 12:09:07 UTC 
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
Comment 1 Mikko Tiihonen 2016-09-22 12:09:15 UTC 
Created attachment 1203697 [details]
File: backtrace
Comment 2 Mikko Tiihonen 2016-09-22 12:09:17 UTC 
Created attachment 1203698 [details]
File: cgroup
Comment 3 Mikko Tiihonen 2016-09-22 12:09:18 UTC 
Created attachment 1203699 [details]
File: core_backtrace
Comment 4 Mikko Tiihonen 2016-09-22 12:09:20 UTC 
Created attachment 1203700 [details]
File: dso_list
Comment 5 Mikko Tiihonen 2016-09-22 12:09:22 UTC 
Created attachment 1203701 [details]
File: environ
Comment 6 Mikko Tiihonen 2016-09-22 12:09:23 UTC 
Created attachment 1203702 [details]
File: exploitable
Comment 7 Mikko Tiihonen 2016-09-22 12:09:24 UTC 
Created attachment 1203703 [details]
File: limits
Comment 8 Mikko Tiihonen 2016-09-22 12:09:26 UTC 
Created attachment 1203704 [details]
File: maps
Comment 9 Mikko Tiihonen 2016-09-22 12:09:28 UTC 
Created attachment 1203705 [details]
File: mountinfo
Comment 10 Mikko Tiihonen 2016-09-22 12:09:29 UTC 
Created attachment 1203706 [details]
File: namespaces
Comment 11 Mikko Tiihonen 2016-09-22 12:09:31 UTC 
Created attachment 1203707 [details]
File: open_fds
Comment 12 Mikko Tiihonen 2016-09-22 12:09:32 UTC 
Created attachment 1203708 [details]
File: proc_pid_status
Comment 13 Mikko Tiihonen 2016-09-22 12:09:33 UTC 
Created attachment 1203709 [details]
File: var_log_messages
Comment 14 Kevin Fenzi 2016-09-22 16:43:07 UTC 
What were you doing when this happened?

Can you duplicate the crash?
Comment 15 Mikko Tiihonen 2016-09-22 17:08:25 UTC 
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.
Comment 16 Kevin Fenzi 2016-09-25 00:21:10 UTC 
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 ***