pulseaudio crashed with SIGSEGV in strcmp() +while trying to connect a headset via bluetooth
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pulseaudio
Using the beta 9.10 liveCD, i was trying to connect a bluetooth headset, while the pairing completed successfully, pulse audio crashed
ProblemType: Crash
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xf9ff8000 irq 22'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,
Controls : 40
Simple ctrls : 22
CurrentDmesg:
Error: command ['sh', '-c', 'dmesg | comm -13 /var/log/dmesg -'] failed with exit code 1: [ 69.940111] eth0: no IPv6 routers present
[ 71.543177] lp0: using parport0 (interrupt-driven).
comm: file 2 is not in sorted order
[ 218.964552] pulseaudio[2781]: segfault at 0 ip 00ba79b8 sp bff6aafc error 4 in libc-2.
Date: Mon Oct 5 13:19:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pulseaudio
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Beta i386 (20090929.2)
Package: pulseaudio 1:0.9.18-0ubuntu3
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/false
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xba79b8 <strcmp+8>: mov (%ecx),%al
PC (0x00ba79b8) ok
source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pulseaudio
StacktraceTop:
strcmp () from /lib/tls/
module_
pa_module_load () from /usr/lib/
?? ()
pa_hook_fire () from /usr/lib/
Title: pulseaudio crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-11-generic i686
UserGroups:
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #437293, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.