Found here https://github.com/Arkq/bluez-alsa > Starting from ALSA library 1.1.2, it is possible to enable thread-safe API functions. It is a noble change, but the implementation leaves a lot to be desired. This "minor" change does not affect hardware audio devices (because for hardware devices, this change is disabled), but it affects A LOT all software plug-ins. Random deadlocks are inevitable. My personal advice is to disable it during alsa-lib configuration step (./configure --disable-thread-safety - of course, if one is compiling alsa-lib from source) Since Gentoo Linux is source-based distribution, would be awesome to disable thread safety for alsa-lib. At least it can be done with optional USE-flag which one can use with care. Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=229a3a3bdcdf5c1f568f0d5280681de7d6ffab26 commit 229a3a3bdcdf5c1f568f0d5280681de7d6ffab26 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2018-04-04 08:02:15 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2018-04-04 08:45:55 +0000 media-libs/alsa-lib: Bump to version 1.1.6 Added thread-safety USE flag. Closes: https://bugs.gentoo.org/640588 Package-Manager: Portage-2.3.28, Repoman-2.3.9 media-libs/alsa-lib/Manifest | 1 + media-libs/alsa-lib/alsa-lib-1.1.6.ebuild | 81 +++++++++++++++++++++++++++++++ media-libs/alsa-lib/metadata.xml | 1 + 3 files changed, 83 insertions(+)
