Bug 924013

Summary: [abrt] transmission-gtk-2.77-1.fc18: fileset_close_torrent: Process /usr/bin/transmission-gtk was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jeff <jeff.mccausland>
Component: transmissionAssignee: Rahul Sundaram <metherid>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: abdulkarimmemon, charles, jspaleta, kumarpraveen.nitdgp, metherid, raghusiddarth, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:44c7a2f8b68334d46cd9fc2eab323c28becce9fc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:09:11 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: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jeff 2013-03-20 22:44:26 UTC 
Description of problem:
I tried to add an, apparently, duplicate torrent.  

Version-Release number of selected component:
transmission-gtk-2.77-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        transmission-gtk magnet:?xt=urn:btih:18a55705f0c44d85eb1260948d59f0480cfb2049&dn=doomwar+issues+1-6&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Ftracker.istole.it%3A6969&tr=udp%3A%2F%2Ftracker.ccc.de%3A80
crash_function: fileset_close_torrent
executable:     /usr/bin/transmission-gtk
kernel:         3.9.0-0.rc3.git0.5.fc20.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 fileset_close_torrent at fdlimit.c:448
 #1 tr_fdTorrentClose at fdlimit.c:611
 #2 tr_torrentRecheckCompleteness at torrent.c:2066
 #3 torrentRecheckDoneImpl at torrent.c:1714
 #4 readFromPipe at trevent.c:192
 #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:248

Potential duplicate: bug 871633
Comment 1 Jeff 2013-03-20 22:44:29 UTC 
Created attachment 713506 [details]
File: backtrace
Comment 2 Jeff 2013-03-20 22:44:31 UTC 
Created attachment 713507 [details]
File: build_ids
Comment 3 Jeff 2013-03-20 22:44:32 UTC 
Created attachment 713508 [details]
File: cgroup
Comment 4 Jeff 2013-03-20 22:44:34 UTC 
Created attachment 713509 [details]
File: core_backtrace
Comment 5 Jeff 2013-03-20 22:44:35 UTC 
Created attachment 713510 [details]
File: dso_list
Comment 6 Jeff 2013-03-20 22:44:37 UTC 
Created attachment 713511 [details]
File: environ
Comment 7 Jeff 2013-03-20 22:44:39 UTC 
Created attachment 713512 [details]
File: limits
Comment 8 Jeff 2013-03-20 22:44:40 UTC 
Created attachment 713513 [details]
File: maps
Comment 9 Jeff 2013-03-20 22:44:42 UTC 
Created attachment 713514 [details]
File: open_fds
Comment 10 Jeff 2013-03-20 22:44:43 UTC 
Created attachment 713515 [details]
File: proc_pid_status
Comment 11 Jeff 2013-03-20 22:44:45 UTC 
Created attachment 713516 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2013-12-21 12:20:11 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 13 Fedora End Of Life 2014-02-05 20:09:11 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.