pulseaudio crashed with SIGSEGV in avahi_client_get_state()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
A crash that requires further investigation.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-2ubuntu2
ProcVersionSign
Uname: Linux 4.8.0-19-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D7p: bonnaudl 24365 F...m pulseaudio
/dev/snd/
CurrentDesktop: KDE
Date: Sat Oct 1 17:38:11 2016
ExecutablePath: /usr/bin/pulseaudio
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7faf1d2103c5 <avahi_
PC (0x7faf1d2103c5) ok
source "0x14(%rdi)" (0x757575757575
destination "%eax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pulseaudio
StacktraceTop:
avahi_
?? () from /usr/lib/
?? () from /usr/lib/
pa_mainloop_
pa_mainloop_
Title: pulseaudio crashed with SIGSEGV in avahi_client_
UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare staff
dmi.bios.date: 03/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: HM77-HT
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
information type: | Private → Public |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1583840, 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.