pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After running a checkbox on Unity 8/Mir, I came back to Unity 7 and the first sound I heard was horrible (and loud). It was a popup from Firefox.
Then the report bug dialog appeared.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-2ubuntu2
ProcVersionSign
Uname: Linux 4.8.0-19-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDesktop: Unity:Unity8
Date: Sat Oct 8 12:45:05 2016
ExecutablePath: /usr/bin/pulseaudio
ExecutableTimes
InstallationDate: Installed on 2016-10-08 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcCwd: /
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=fr_FR
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_alsa_
?? () from /usr/lib/
pa_source_
?? () from /usr/lib/
?? () from /usr/lib/
Title: pulseaudio crashed with SIGABRT in pa_alsa_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/08/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.20
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.27
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP EliteBook 8530p
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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 #1539209, 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.