Bug 770463 - [abrt] audacity-1.3.13-0.4.beta.fc14: nanosleep: Process /usr/bin/audacity was killed by signal 11 (SIGSEGV)
Summary: [abrt] audacity-1.3.13-0.4.beta.fc14: nanosleep: Process /usr/bin/audacity wa...
Keywords:
Status: CLOSED ERRATA
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:517764ed72972cb73b7fb92e5fd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-26 20:19 UTC by Stefanvde
Modified: 2012-04-02 23:27 UTC (History)
2 users (show)

Fixed In Version: audacity-2.0.0-1.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-02 23:27:08 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (824 bytes, text/plain)
2011-12-26 20:19 UTC, Stefanvde
no flags Details

Description Stefanvde 2011-12-26 20:19:18 UTC
abrt version: 1.1.18
architecture: i686
cmdline: audacity
component: audacity
Attached file: coredump, 45035520 bytes
crash_function: nanosleep
executable: /usr/bin/audacity
kernel: 2.6.35.14-106.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: 1324930074
uid: 500

backtrace
-----
[New Thread 8801]
[New Thread 8792]
[New Thread 8791]
[Thread debugging using libthread_db enabled]
Core was generated by `audacity'.
Program terminated with signal 11, Segmentation fault.
#0  GetData (this=0x8d21a78) at WaveClip.h:57
57	WaveClip.h: No such file or directory.
	in WaveClip.h

Thread 3 (Thread 0xb77c0860 (LWP 8791)):
#0  __kernel_vsyscall () at arch/x86/vdso/vdso32/int80.S:16
No locals.
#1  0x00c17bc6 in nanosleep () at ../sysdeps/unix/syscall-template.S:82
No locals.
#2  0x07745449 in wxMicroSleep (microseconds=50000) at src/unix/utilsunx.cpp:191
        tmReq = {tv_sec = 0, tv_nsec = 50000000}
#3  0x07745472 in wxMilliSleep (milliseconds=50) at src/unix/utilsunx.cpp:212
No locals.
#4  0x0812c15c in AudioIO::StopStream (this=0x8ad9aa8) at AudioIO.cpp:1687

Timeout exceeded: 60 second, killing gdb

How to reproduce
-----
1.
2.
3.
Beim Beenden stürzt Audacity ab,vorher Aufnahme abgehackt

Comment 1 Stefanvde 2011-12-26 20:19:21 UTC
Created attachment 549620 [details]
File: backtrace

Comment 2 David Timms 2011-12-27 01:58:51 UTC
(In reply to comment #0)
> Beim Beenden stürzt Audacity ab,vorher Aufnahme abgehackt
Google translates as:
Audacity crashes on exit, before recording choppy

Could you provide a short audio sample of how the "choppy recording" sounds ?

Were any errors written to /var/log/messages while the choppy recording was occurring ?

Did you have audacity still recording when you chose exit ?

The upstream audacity project has released a new beta: 1.3.14 beta. This is currently available in updates-testing:
yum --enablerepo=*testing list audacity*

Any chance that you could try to reproduce the issue you saw with the -testing version ?
If so, please provide comments to:
https://admin.fedoraproject.org/updates/audacity-1.3.14-0.5.fc16

Comment 3 Fedora Update System 2012-03-15 21:59:00 UTC
audacity-2.0.0-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/audacity-2.0.0-1.fc16

Comment 4 Fedora Update System 2012-03-17 23:46:33 UTC
Package audacity-2.0.0-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing audacity-2.0.0-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-4050/audacity-2.0.0-1.fc16
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-04-02 23:27:08 UTC
audacity-2.0.0-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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