pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I plugged my headphones Logitech G933 Wireless and selected them in the audio section in the settings and then I changed the volume with my keyboard fn+function
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
CurrentDesktop: GNOME
Date: Sun Oct 22 16:56:46 2017
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2017-10-19 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_sink_
pa_sink_
?? () from /usr/lib/
pa_card_
?? () from /usr/lib/
Title: pulseaudio crashed with SIGABRT in pa_sink_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Q501LA.212
dmi.board.
dmi.board.name: Q501LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: Q
dmi.product.name: Q501LA
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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 #1556439, 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.