Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
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)
Summary: [abrt] crash in transmission-gtk-1.93-1.fc13: tr_torrent_open_folder: Process...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: transmission
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c6bbde956757872bf73ecead9cd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-30 15:21 UTC by A Muslic
Modified: 2010-06-17 18:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-17 18:22:11 UTC


Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-30 15:21 UTC, A Muslic
no flags Details

Description A Muslic 2010-05-30 15:21:14 UTC
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 15:21:17 UTC
Created attachment 418045 [details]
File: backtrace

Comment 2 Charles Kerr 2010-05-30 22:47:45 UTC
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.