Bug 693730

Summary: [abrt] libtorrent 0.14.? (deluge-daemon-1.3.1-2.fc14) policy::find_connect_candidate (SIGABRT)
Product: [Fedora] Fedora Reporter: Jonathan Pritchard <jonathanr.pritchard+bugzilla>
Component: rb_libtorrentAssignee: Rahul Sundaram <metherid>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: calumlind, ggillies, leigh123linux, metherid, shnurapet
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7abedb313811da227fcc52586c7eea9143c503c0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 14:36:52 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

Description Jonathan Pritchard 2011-04-05 13:04:25 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 83539 bytes
cmdline: /usr/bin/python /usr/bin/deluged --port=58846 --config=/home/Jon/.config/deluge
comment: Seems to be related to the strain of file checking, as this happens often with Deluge in both present and past versions.
component: deluge
Attached file: coredump, 152297472 bytes
crash_function: boost::throw_exception<std::bad_cast>
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.i686.PAE
package: deluge-daemon-1.3.1-2.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1302007672
uid: 500

How to reproduce
-----
1. Restarted Deluge daemon, and connected to it.
2. It was checking the integrity of around 100 torrents.
3. Daemon crashed, and reported by ABRT
Comment 1 Jonathan Pritchard 2011-04-05 13:04:28 UTC 
Created attachment 489976 [details]
File: backtrace
Comment 2 Calum 2011-11-28 23:16:55 UTC 
This sounds like a libtorrent issue. 

You could try either manually upgrading to rb_libtorrent 0.15.8 or upgrade to F15
Comment 3 Calum 2011-11-29 16:57:24 UTC 
*** Bug 659913 has been marked as a duplicate of this bug. ***
Comment 4 Fedora End Of Life 2012-08-16 14:36:55 UTC 
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping