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 alsactl daemon is always started on boot and can only prevent
this via "systemctl mask alsa-state" currently.
It looks like this was done intentionally, to fix #925455. The changelog
entry is written:
* Introduce Fix-alsactl-to-restore-config.patch. Don't rely on undocumented
/etc/alsa/state-daemon.conf to start alsa-state.service. alsa-restore.service
now will have an error code 99 the first time it runs. But after an reload of
the service or just a reboot both services will run smoothly.
[closes: #925455]
But that introduces exactly this issue; like you, I want one service or
the other running, not both!
There is a 1.1.8-3 version pending in git, with what looks to me like a
better solution (commit d8e09154), unfortunately not uploaded yet...
