Package: libasound2 Version: 1.1.0-1 Severity: important I don't know whether this bug lies in libasound2, libasound2-plugins, or alsa-utils; reporting it here because it seems like the most likely candidate.
I just upgraded the following packages: [UPGRADE] alsa-utils:amd64 1.0.29-1+b1 -> 1.1.0-1 [UPGRADE] libasound2:amd64 1.0.29-1 -> 1.1.0-1 [UPGRADE] libasound2-data:amd64 1.0.29-1 -> 1.1.0-1 [UPGRADE] libasound2-plugins:amd64 1.0.29-1 -> 1.1.0-1 Immediately after doing so, pulseaudio started logging the following error: Feb 01 20:14:28 x pulseaudio[583]: [alsa-sink-ALC3232 Analog] alsa-sink.c: Error opening PCM device front:1: Invalid argument Feb 01 20:14:28 x pulseaudio[583]: [alsa-sink-ALC3232 Analog] alsa-sink.c: Error opening PCM device front:1: Invalid argument Feb 01 20:14:30 x pulseaudio[583]: [alsa-sink-ALC3232 Analog] alsa-sink.c: Error opening PCM device front:1: Invalid argument Feb 01 20:14:30 x pulseaudio[583]: [alsa-sink-ALC3232 Analog] alsa-sink.c: Error opening PCM device front:1: Invalid argument And attempting to play any audio via pulse (for instance, using mpv) would fail to play audio, and stall out. (The audio didn't just go silent; pulseaudio didn't accept audio, breaking applications and causing them to not progress.) Restarting my session did not fix that problem, because pulseaudio stuck around and got reused by the next session. I had to kill pulseaudio so it would respawn, at which point audio started working again. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libasound2 depends on: ii libasound2-data 1.1.0-1 ii libc6 2.21-7 libasound2 recommends no packages. Versions of packages libasound2 suggests: ii libasound2-plugins 1.1.0-1 -- no debconf information
