[Pkg-alsa-devel] Bug#976895: libasound2: regression (stops working): Alsa_driver: recover: pcm_status(): Broken pipe

Thorsten Glaser tg at mirbsd.de
Wed Dec 9 05:10:06 GMT 2020


Package: libasound2
Version: 1.2.4-1
Severity: important
X-Debbugs-Cc: tg at mirbsd.de, debian-multimedia at lists.debian.org
Control: notfound -1 1.2.3.2-1+b1

The latest libasound2 introduced a severe regression:


Starting musescore3 and loading a score, e.g. like this…

	$ musescore3 /usr/share/mscore3-3.2/demos/Reunion.mscz

… quickly brings the whole system down because it spits tons of lines…

	Alsa_driver: recover: pcm_status(): Broken pipe

… to the xterm in which it was invoked.


Running it without output…

	$ musescore3 /usr/share/mscore3-3.2/demos/Reunion.mscz >/dev/null 2>&1

… just results in…

  PID USER      NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                           
24181 tglase     0  871224 218944  73920 D 100.0   2.7   0:06.67 musescore3 /usr/share/mscore3-3.2+

… and the user has to kill the offending program by ^Cing in the terminal
(as killing when in “D” state cannot work).


This is where I started:

ii  alsa-utils                                    1.2.4-1                         amd64        Utilities for con>
ii  libasound2:amd64                              1.2.4-1                         amd64        shared library fo>
ii  libasound2:i386                               1.2.4-1                         i386         shared library fo>
ii  libasound2-data                               1.2.4-1                         all          Configuration fil>
ii  libatopology2:amd64                           1.2.4-1                         amd64        shared library fo>

Downgrading to…

ii  libasound2:amd64                              1.2.3.2-1+b1                    amd64        shared library fo>
ii  libasound2:i386                               1.2.3.2-1+b1                    i386         shared library fo>
ii  libasound2-data                               1.2.3.2-1                       all          Configuration fil>
ii  libatopology2:amd64                           1.2.3.2-1+b1                    amd64        shared library fo>

… allowed this to work again, and libatopology2:amd64 (which could be
individually upgraded) quickly turned out to be unconnected. So this
is clearly something in libasound2 and/or libasound2-data.

Playing music with mpg123 _does_ work with 1.2.4-1 so this is tricky.
I’m not filing it with RC severity as it doesn’t impact “all” use, but
this is, very much, a showstopper IMHO.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libasound2 depends on:
ii  libasound2-data  1.2.4-1
ii  libc6            2.31-5

libasound2 recommends no packages.

Versions of packages libasound2 suggests:
pn  libasound2-plugins  <none>

-- no debconf information


More information about the Pkg-alsa-devel mailing list