pulseaudio crashed with SIGSEGV in strcmp()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pulseaudio
Crash occurred immediately after pairing with a Motorola H500 headset over bluetooth. Crash is readily reproducible by removing bluetooth device and repairing.
ProblemType: Crash
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,
Controls : 35
Simple ctrls : 20
Card1.Amixer.info:
Card hw:1 'CX8801'/'Conexant CX8801 at 0xfb000000'
Mixer name : 'CX88'
Components : ''
Controls : 3
Simple ctrls : 2
Card2.Amixer.info:
Card hw:2 'CMI8738'/'C-Media CMI8738 (model 55) at 0xce00, irq 23'
Mixer name : 'CMedia PCI'
Components : ''
Controls : 41
Simple ctrls : 22
CrashCounter: 1
Date: Mon Sep 28 22:07:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pulseaudio
NonfreeKernelMo
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: 0x7fef95b89e20 <strcmp>: mov (%rdi),%al
PC (0x7fef95b89e20) ok
source "(%rdi)" (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/libc.so.6
module_
pa_module_load ()
?? ()
pa_hook_fire () from /usr/lib/
Title: pulseaudio crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-11-generic x86_64
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.