Bug 1251659

Summary: [abrt] transmission-gtk: __pthread_mutex_lock(): transmission-gtk killed by SIGSEGV
Product: [Fedora] Fedora Reporter: icywind90
Component: transmissionAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: abdulkarimmemon, bartoszmarc, charles, gwync, helio, jspaleta, kumarpraveen.nitdgp, raghusiddarth, sanjay.ankur, teddyg0
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8fac37a72ee5f8ff72048a0fa3d9adc1afdd47c8
Whiteboard: abrt_hash:310b83f12e8d7ca04b5ed63563375877329749e2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:25:05 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description icywind90 2015-08-08 13:13:18 UTC 
Version-Release number of selected component:
transmission-gtk-2.84-7.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        transmission-gtk magnet:?xt=urn:btih:828e86180150213c10677495565baef6b232dbdd&dn=archlinux-2015.08.01-dual.iso&tr=udp://tracker.archlinux.org:6969&tr=http://tracker.archlinux.org:6969/announce
crash_function: __pthread_mutex_lock
executable:     /usr/bin/transmission-gtk
global_pid:     5860
kernel:         4.1.3-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:67
 #1 tr_lockLock at platform.c:187
 #2 tr_sessionLock at session.c:1071
 #3 tr_torrentLock at torrent.h:308
 #4 tr_torrentRecheckCompleteness at torrent.c:2149
 #5 onVerifyDoneThreadFunc at torrent.c:1779
 #6 readFromPipe at trevent.c:190
 #7 event_process_active_single_queue at event.c:1350
 #8 event_process_active at event.c:1420
 #9 event_base_loop at event.c:1621

Potential duplicate: bug 895160
Comment 1 icywind90 2015-08-08 13:13:22 UTC 
Created attachment 1060575 [details]
File: backtrace
Comment 2 icywind90 2015-08-08 13:13:24 UTC 
Created attachment 1060576 [details]
File: cgroup
Comment 3 icywind90 2015-08-08 13:13:25 UTC 
Created attachment 1060577 [details]
File: core_backtrace
Comment 4 icywind90 2015-08-08 13:13:27 UTC 
Created attachment 1060578 [details]
File: dso_list
Comment 5 icywind90 2015-08-08 13:13:28 UTC 
Created attachment 1060579 [details]
File: environ
Comment 6 icywind90 2015-08-08 13:13:30 UTC 
Created attachment 1060580 [details]
File: limits
Comment 7 icywind90 2015-08-08 13:13:32 UTC 
Created attachment 1060581 [details]
File: maps
Comment 8 icywind90 2015-08-08 13:13:33 UTC 
Created attachment 1060582 [details]
File: mountinfo
Comment 9 icywind90 2015-08-08 13:13:34 UTC 
Created attachment 1060583 [details]
File: namespaces
Comment 10 icywind90 2015-08-08 13:13:36 UTC 
Created attachment 1060584 [details]
File: open_fds
Comment 11 icywind90 2015-08-08 13:13:37 UTC 
Created attachment 1060585 [details]
File: proc_pid_status
Comment 12 Fedora End Of Life 2016-07-19 17:25:05 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.