Bug 711627 - [abrt] audacity-1.3.13-0.4.beta.fc14: Meter::IsMeterDisabled: Process /usr/bin/audacity was killed by signal 11 (SIGSEGV)
Summary: [abrt] audacity-1.3.13-0.4.beta.fc14: Meter::IsMeterDisabled: Process /usr/bi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: audacity
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Manuel F Martinez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:be869e592b2c5dd27380c753c33...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-08 00:46 UTC by Greg
Modified: 2011-12-14 11:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-14 11:52:30 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (50.46 KB, text/plain)
2011-06-08 00:46 UTC, Greg
no flags Details

Description Greg 2011-06-08 00:46:41 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 51673 bytes
cmdline: audacity
component: audacity
Attached file: coredump, 65425408 bytes
crash_function: Meter::IsMeterDisabled
executable: /usr/bin/audacity
kernel: 2.6.35.13-91.fc14.i686
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: 1307493852
uid: 500

How to reproduce
-----
1. Open Audacity
2. Click on arrow below input monitor
3. Click on "start monitoring"
4. Audacity crashes

Comment 1 Greg 2011-06-08 00:46:45 UTC
Created attachment 503594 [details]
File: backtrace

Comment 2 Roger Berg 2011-09-02 12:52:18 UTC
Package: audacity-1.3.13-0.4.beta.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
Crash during startup

Comment 3 David Timms 2011-09-08 23:48:12 UTC
(In reply to comment #0)
> 3. Click on "start monitoring"
> 4. Audacity crashes
Hi, can you tell me whether audacity is working normally otherwise, eg, if you do not access that menu item, does playback, record and so forth work ok ?

Also, the trace seems to involve JACK audio server. Would this be your audacity IO setting, or is this audacity testing the various IO methods, to determine which should be used/available for selection 

ps. Same question to other reporters of this bug.

Comment 4 David Timms 2011-12-14 11:52:30 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 ?


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