FS#61436 - alsa-restore.service fails on unmet condition

Attached to Project: Arch Linux
Opened by Martin L. (wuestengecko) - Wednesday, 16 January 2019, 22:36 GMT
Last edited by David Runge (dvzrv) - Sunday, 08 September 2019, 21:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

During boot, alsa-restore.service is started too early, before the corresponding device nodes were created. `systemctl status` tells that it was skipped because `ConditionPathExistsGlob=/dev/snd/control*` was not met. Manually starting the service after logging in succeeds.

Additional info:

* package version(s)
linux-ck 4.20.1-1
systemd 240.34-3
alsa-lib 1.1.8-1
* config and/or log files etc.

$ systemctl status alsa-restore.service
● alsa-restore.service - Save/Restore Sound Card State
Loaded: loaded (/usr/lib/systemd/system/alsa-restore.service; static; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2019-01-16 23:16:33 CET; 33s ago
└─ ConditionPathExistsGlob=/dev/snd/control* was not met

Jan 16 23:16:33 tiah systemd[1]: Condition check resulted in Save/Restore Sound Card State being skipped.


Steps to reproduce:

1. Make sure `/etc/alsa/state-daemon.conf` does not exist.
2. Boot the system.
3. Login and run `systemctl status alsa-restore.service`.
This task depends upon

Closed by  David Runge (dvzrv)
Sunday, 08 September 2019, 21:27 GMT
Reason for closing:  Upstream
Comment by loqs (loqs) - Thursday, 17 January 2019, 00:32 GMT
The case of the device not being present will be handled by udev using /usr/lib/udev/rules.d/90-alsa-restore.rules when the device is detected.
/usr/lib/systemd/system/alsa-restore.service is supplied by upstream. Have you contacted upstream about the issue?
Other than the service not being executed is there any other impact on the system?
Comment by Martin L. (wuestengecko) - Thursday, 17 January 2019, 18:02 GMT
I haven't contacted upstream yet.
Since the service as systemd sees it is never started, its ExecStop= won't update /var/lib/asound.state on system shutdown. Other than that, everything works as it should.

I just installed and tested with the vanilla Arch kernel, and it doesn't show this problem - the service starts fine there. So it seems this is actually an issue with the ck kernel?
Is this even the right place for this bug then?
Comment by loqs (loqs) - Thursday, 17 January 2019, 18:24 GMT
AUR packages and custom repositories are not covered by the bug tracker.

Loading...