Bug 549993 - transmission-1.76-1.fc12 crashed in trackerPulse()
Summary: transmission-1.76-1.fc12 crashed in trackerPulse()
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: transmission
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b0c9094a84b6efa519cd72f25fb...
: 551811 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-23 07:57 UTC by Sergey Kurtsev
Modified: 2013-03-13 05:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-11 22:09:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (7.57 KB, text/plain)
2009-12-23 07:57 UTC, Sergey Kurtsev
no flags Details

Description Sergey Kurtsev 2009-12-23 07:57:00 UTC
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: transmission /home/sk/.opera/temporary_downloads/[RuTor.Org]Bandslam.2009.DVDRip.avi.torrent
component: transmission
executable: /usr/bin/transmission
kernel: 2.6.31.6-166.fc12.i686.PAE
package: transmission-1.76-1.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Sergey Kurtsev 2009-12-23 07:57:03 UTC
Created attachment 379986 [details]
File: backtrace

Comment 2 Rahul Sundaram 2010-01-11 22:09:41 UTC

*** This bug has been marked as a duplicate of bug 539820 ***

Comment 3 Charles Kerr 2010-04-19 16:38:33 UTC
Hi Sergey,

I think this ticket is not a duplicate of bug 539820 after all.  It looks like it was a crash in trackerPulse() that crashed your copy of Transmission.

Since trackerPulse() was been wholly rewritten between 1.76 and 1.80 to allow for parallel tracker announces, I'm marking this ticket as NEXTRELEASE since Transmission version 1.92, which will ship in Fedora 13, fixes the issue.

Comment 4 Charles Kerr 2010-04-19 17:31:06 UTC
*** Bug 551811 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.