abrt version: 1.1.17 architecture: i686 Attached file: backtrace, 43895 bytes cmdline: audacity component: audacity Attached file: coredump, 78229504 bytes crash_function: DeviceName executable: /usr/bin/audacity kernel: 2.6.35.12-88.fc14.i686 package: audacity-1.3.12-0.6.beta.fc14 rating: 4 reason: Process /usr/bin/audacity was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1303485411 uid: 500 How to reproduce ----- 1.play a recording, 2. open tool bar 3. select input device Jack...
Created attachment 494251 [details] File: backtrace
It seems thread 1, 5 and 4 are relevant. (In reply to comment #0) From what I can see, I assume you missed: 0. install jack 0.1 run jackd > 1.play a recording, 1b: stop the playback > 2. open tool bar 2 View|Toolbars|Device Toolbar: check > 3. select input device Jack... What type of IO were you using to start ? I guess you dropped down the list, and clicked from that IO to Jack ? Was the crash immediate, or after attempting playback ? What version of JACK is installed ? Which jackd are you running ? (eg rt etc) Is this the same as if jack dies eg: ps aux|grep jack kill <value> from above Is it reproducible ?
audacity-1.3.13-0.3.beta.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/audacity-1.3.13-0.3.beta.fc14
Package audacity-1.3.13-0.3.beta.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing audacity-1.3.13-0.3.beta.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/audacity-1.3.13-0.3.beta.fc14 then log in and leave karma (feedback).
audacity-1.3.13-0.4.beta.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/audacity-1.3.13-0.4.beta.fc14
audacity-1.3.13-0.4.beta.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.