Bug 1035055

Summary: [abrt] transmission-gtk-2.80-2.fc19: tr_sessionLock: Process /usr/bin/transmission-gtk was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Hamza Lazaar <brice2k5>
Component: transmissionAssignee: Rahul Sundaram <metherid>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: abdulkarimmemon, charles, jspaleta, kumarpraveen.nitdgp, metherid, raghusiddarth, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9365d90a9b45b4d79049f4d630d442a48ae0ce28
Whiteboard: abrt_hash:aa46e0b28c1ae95488549a765d930d8acfce03f9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:25:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup none

Description Hamza Lazaar 2013-11-27 00:41:53 UTC 
Version-Release number of selected component:
transmission-gtk-2.80-2.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/transmission-gtk magnet:?xt=urn:btih:SJOHVVNE62AA5YJDQOXEM2JHIVW6SBEE&dn=Sons.of.Anarchy.S06E11.720p.HDTV.x264-2HD&tr=udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80&tr=udp://open.demonii.com:80&tr=udp://tracker.coppersurfer.tk:80
crash_function: tr_sessionLock
executable:     /usr/bin/transmission-gtk
kernel:         3.11.8-200.fc19.i686
runlevel:       N 5
type:           CCpp
uid:            1801

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 tr_sessionLock at session.c:1072
 #1 tr_torrentLock at torrent.h:314
 #2 tr_torrentRecheckCompleteness at torrent.c:2126
 #3 onVerifyDoneThreadFunc at torrent.c:1777
 #4 readFromPipe at trevent.c:193
 #5 event_process_active_single_queue at event.c:1340
 #6 event_process_active at event.c:1407
 #7 event_base_loop at event.c:1604
 #8 event_base_dispatch at event.c:1435
 #9 libeventThreadFunc at trevent.c:249

Potential duplicate: bug 799658
Comment 1 Hamza Lazaar 2013-11-27 00:42:11 UTC 
Created attachment 829551 [details]
File: backtrace
Comment 2 Hamza Lazaar 2013-11-27 00:42:16 UTC 
Created attachment 829552 [details]
File: cgroup
Comment 3 Fedora End Of Life 2015-01-09 20:42:33 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.
Comment 4 Fedora End Of Life 2015-02-17 19:25:15 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.