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

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

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

You are right, the change was reverted (partly) which is the reason why I couldn't find the bug on Git. Indeed the other issue is that, if the state-daemon.conf exists, none of the two services starts. The initial bug that caused this "bad" fix is also something I recognise on e.g. Stretch

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

On Tue, Jul 16, 2019 at 05:12:59PM +0200, sch0r...@arcor.de wrote: Expected behaviour: - alsa-state.service starts, if state-daemon.conf exists. - alsa-restore.service starts, if state-daemon.conf does NOT exist. Actual behaviour: - Both systemd units start if state-daemon.conf exists. - So

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

Package: alsa-utils Version: 1.1.8-2 Expected behaviour: - alsa-state.service starts, if state-daemon.conf exists. - alsa-restore.service starts, if state-daemon.conf does NOT exist. Actual behaviour: - Both systemd units start if state-daemon.conf exists. - So alsactl daemon is always started