aplay crashed with SIGSEGV

Bug #148815 reported by pupdawg
12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned
Declined for Gutsy by Henrik Nilsen Omma

Bug Description

Binary package hint: alsa-utils

Sound works but very often it will stop with these errors... also firefox will often freeze when playing audio eg. Youtube movies.

I have an X-Station USB sound card/synth... it has always worked well in the past with Ubuntu but since Feisty and Gutsy it have been unreliable.

Sound properties will also crash instantly when I click on the test buttons.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Oct 3 21:35:58 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/aplay
NonfreeKernelModules: fglrx
Package: alsa-utils 1.0.14-1ubuntu4
PackageArchitecture: i386
ProcCmdline: aplay /usr/share/sounds/error.wav
ProcCwd: /home/pupdawg
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: alsa-utils
StacktraceTop:
 ?? () from /usr/lib/libasound.so.2
 ?? () from /usr/lib/libasound.so.2
 ?? ()
 ?? () from /lib/ld-linux.so.2
 ?? () from /usr/lib/libasound.so.2
Title: aplay crashed with SIGSEGV
Uname: Linux pupdawg-linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
pupdawg (pupdawg) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:mix_areas3_cmov (size=1, dst=0xb7b658c3 <Address 0xb7b658c3 out of bounds>, src=0x807407b "",
snd_pcm_dmix_sync_area (pcm=0x8073228) at pcm_dmix.c:244
snd_pcm_dmix_start (pcm=0x8073228) at pcm_dmix.c:539
snd_pcm_start (pcm=0x8073228) at pcm.c:1047
snd_pcm_generic_start (pcm=0x805a7b8) at pcm_generic.c:155

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in alsa-utils:
importance: Undecided → Medium
Revision history for this message
pupdawg (pupdawg) wrote :

Seems to cause a lot of system stability issues... Web browser crashed alot when playing a flash movie with sound and Totem crashed all the time too... When sound is working it never lasts more then a few seconds but if I close and reopen the app it will play again for a few seconds. I also noticed it is slightly better when using my MB USB ports and not my PCI USB card when I use the PCI card it crashes even more. I have a nForce4 chipset

When I try to adjust the volume controls in Gnome the sliders brake apart into mono channels and do all sorts of strange things.

If there is anything I can do to help I will just give me some hints. I'll recompile a kernel with alsa debuging on etc. if needed.

Thank you

Revision history for this message
pupdawg (pupdawg) wrote :

Oh and just to let you know if I unplug my USB sound card it never crashes and everything is stable... I did have to edit my alsa-base file so the USB sound card received index 0 by commenting out options snd-usb-audio index=-2 line. I have no other sound cards in my system enabled.

I don't know what other info I can provide at this time.

Changed in alsa-utils:
status: New → Confirmed
Revision history for this message
Daniel T Chen (crimsun) wrote :

Please execute the alsa-info.sh script referenced from https://wiki.ubuntu.com/DebuggingSoundProblems and attach the URL here.

Is this symptom still reproducible in 8.10 alpha?

Changed in alsa-utils:
status: Confirmed → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.