Bug 963878 - [abrt] audacity-2.0.3-1.fc18: Terminate: Process /usr/bin/audacity was killed by signal 6 (SIGABRT)
[abrt] audacity-2.0.3-1.fc18: Terminate: Process /usr/bin/audacity was killed...
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: audacity (Show other bugs)
18
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Manuel F Martinez
Fedora Extras Quality Assurance
abrt_hash:e019ff2c573df0abb0b30476a29...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-16 13:29 EDT by fitoflos
Modified: 2013-05-20 05:11 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-05-20 05:11:01 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)

  None (edit)
Description fitoflos 2013-05-16 13:29:37 EDT
Version-Release number of selected component:
audacity-2.0.3-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        audacity
crash_function: Terminate
executable:     /usr/bin/audacity
kernel:         3.8.11-200.fc18.x86_64
uid:            1000
ureports_counter: 1
xsession_errors: 

Truncated backtrace:
Thread no. 1 (8 frames)
 #4 Terminate at src/hostapi/jack/pa_jack.c:816
 #5 TerminateHostApis at src/common/pa_front.c:147
 #6 Pa_Terminate at src/common/pa_front.c:358
 #7 AudioIO::~AudioIO at AudioIO.cpp:622
 #8 DeinitAudioIO at AudioIO.cpp:487
 #9 AudacityApp::OnExit at AudacityApp.cpp:1857
 #10 ~CallOnExit at src/common/init.cpp:442
 #11 wxEntry at src/common/init.cpp:448

Potential duplicate: bug 710631
Comment 1 Hans de Goede 2013-05-20 05:11:01 EDT
Hi,

Audacity in Fedora 17 and later has been upgraded the upstream 2.0.3 bugfix release, which includes a lot of bugfixes, and hopefully also fixes this bug.

Please upgrade audacity to the 2.0.3 release and try again. If it crashes again, please let abrt file a new bug with the 2.0.3 release, which may have a different backtrace / issue.

Thanks & Regards,

Hans

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