Bug 709890

Summary: [abrt] audacity-1.3.13-0.4.beta.fc14: GetData: Process /usr/bin/audacity was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: chuck elliot <chuck.elliot>
Component: audacityAssignee: Manuel F Martinez <manpaz>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dtimms, manpaz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c34e38088ebc5418c12e76a5c3aa5b33bb99a335
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-14 11:52:10 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 chuck elliot 2011-06-01 21:05:55 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 30337 bytes
cmdline: audacity
component: audacity
Attached file: coredump, 63741952 bytes
crash_function: GetData
executable: /usr/bin/audacity
kernel: 2.6.35.13-92.fc14.x86_64
package: audacity-1.3.13-0.4.beta.fc14
rating: 4
reason: Process /usr/bin/audacity was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1306961961
uid: 500

How to reproduce
-----
1. recorded and set level ready for recording.
2. stopped and deleted temp audio track.
3. crash occurred
Comment 1 chuck elliot 2011-06-01 21:06:01 UTC 
Created attachment 502385 [details]
File: backtrace
Comment 2 David Timms 2011-12-14 11:52:10 UTC 
I was unable to reproduce this issue, and since Fedora 14 is now end of life, this bug will be closed.

However, a new beta release of audacity has been released and built for Fedora 15, 16, and devel. These builds will shortly be available in the updates-testing repository for Fedora 15 and 16. Perhaps you would like to perform this test case with the new release to see if the issue is resolved ?