Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 597806 - [abrt] crash in transmission-gtk-1.93-1.fc13: tr_torrent_open_folder: Process /usr/bin/transmission was killed by signal 11 (SIGSEGV)
[abrt] crash in transmission-gtk-1.93-1.fc13: tr_torrent_open_folder: Process...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: transmission (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Rahul Sundaram
Fedora Extras Quality Assurance
abrt_hash:c6bbde956757872bf73ecead9cd...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-30 11:21 EDT by A Muslic
Modified: 2010-06-17 14:22 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-17 14:22:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (20.31 KB, text/plain)
2010-05-30 11:21 EDT, A Muslic
no flags Details

  None (edit)
Description A Muslic 2010-05-30 11:21:14 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: transmission
component: transmission
crash_function: tr_torrent_open_folder
executable: /usr/bin/transmission
global_uuid: c6bbde956757872bf73ecead9cd77bd5cf97c2f7
kernel: 2.6.33.4-95.fc13.x86_64
package: transmission-gtk-1.93-1.fc13
rating: 4
reason: Process /usr/bin/transmission was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 A Muslic 2010-05-30 11:21:17 EDT
Created attachment 418045 [details]
File: backtrace
Comment 2 Charles Kerr 2010-05-30 18:47:45 EDT
Upstream ticket: https://trac.transmissionbt.com/ticket/3245

This is fixed now in trunk.  When 2.00 is released, it will have this fix.

If/when 1.94 is released, it will have this fix too.

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