[Pkg-alsa-devel] Bug#932209: [ALSA] alsa-state.service starts daemon due to wrong ConditionPathExists

[MichaIng]

Package: alsa-utils
Version: 1.1.8-2
Severity: important

In short:
Please release 1.1.8-3 it to Debian Buster!

1.1.8-3 indeed solves the issue from what I can see for Debian Bullseye. 
Also the original issue has been solved, the currently available 
alsa-utils package (on Bullseye) does not contain the faulty 
"ConditionPathExists=/var/lib/alsa/asound.state" in alsa-restore.service 
that was introduced basically here: 
https://salsa.debian.org/alsa-team/alsa-utils/-/commit/f1eba0b5deb6c3988d6dd7317ccc931c09792843

What I don't understand now is that this code is still present on every 
Git repository in https://salsa.debian.org/alsa-team/alsa-utils.
Even more strange is that, while this code has been committed in end of 
2017, it has been identified as faulty (patch that time) already at the 
beginning of 2017 where the patch has been skipped in v1.1.3-1: 
https://metadata.ftp-master.debian.org/changelogs//main/a/alsa-utils/alsa-utils_1.1.3-1_changelog

So since for me how all this back and forth did not work well and caused 
quite major issues, I opened a merge request to remove/revert the faulty 
commit: https://salsa.debian.org/alsa-team/alsa-utils/-/merge_requests/4
I can only guess that there is currently some patch which removes it but 
since this didn't survive in the past, I think it's better to have it 
clear and transparent in the repo code base.

Last but not least what I can absolutely not understand is that while 
1.1.8-2 causes a major issue and 1.1.8-3 fixed it over a year ago, why 
this has not been merged into Buster until now. The changelog shows 
1.1.8-2 and 1.1.8-2 timestamps only 23 seconds apart: 
https://metadata.ftp-master.debian.org/changelogs//main/a/alsa-utils/alsa-utils_1.2.3-1_changelog
So it seems that the issue has been immediately identified (makes sense, 
as it is so obvious) and merged moreless in the same run, at least into 
changelog. But for some strange reason that fix was never merged into 
Buster and I cannot even see a Git branch for 1.1.8-3. Has it somehow 
been lost as last minute commit, coming too late? There was been some 
back and forth when merging to "unstable" that time, see the history: 
https://salsa.debian.org/alsa-team/alsa-utils/-/tree/0dee89e615d5bdba8c5f573aad0162b8354ad710

=> Please release 1.1.8-3 it to Debian Buster!

Best regards,

Micha