Red Hat Bugzilla – Bug 289891
'random' seg fault during audio capture
Last modified: 2008-04-04 10:04:51 EDT
Description of problem:
I've been using audacity heavily 'ripping' old LPs.
I got this sort of random seg fault:
Sep 13 12:04:13 localhost kernel: audacity: segfault at 0caff204 eip
008af932 esp b7a3cf64 error 4
Bugbuddy seemed to capture information (didn't forward, complaining it doesn't
know about audacity).
But I saved the output: I attach it below.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 195131 [details]
Bug report output from audacity crash
1. When exactly do you get that?
[I notice references of wxConvBrokenFileNames()]
2. With development/test releases it is important to install
as many relevant -debuginfo packages as necessary to fill the
missing details in backtraces:
At least helpful would be:
1. I had audacity 'running' recording input from a USB input (actually, a USB
turntable....). Audacity window was exposed and was drawing the 'track waves'
2. Yeah, I will install now. Unfortunately, hard to go back in time. ;)
Now have debuginfo packages installed for:
[Had older debuginfo packages installed for some of these. Now updated. I've
enabled the debuginfo repo so these 'keep up' going forward, in case this faults
In case this is reproducible with Fedora 8, we need more
Also, there's a test-build of Audacity 1.3.4-beta built
with wxGTK 2.8.x:
I'm running off of Rawhide, but I'll install the beta and see how it goes.
Haven't seen this again, but pulseaudio has reduced my usage of late ;)
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.
If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)
Thanks for your help and we apologize for the interruption.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Haven't been able to reproduce this.