[Pkg-alsa-devel] Bug#848395: Bug#848395: udev rule fails with exit code 99

[Elimar Riesebieter]

Control: tags -1 +moreinfo

* Paul Menzel <pmenzel at molgen.mpg.de> [2016-12-17 11:03 +0100]:

> Package: alsa-utils
> Version: 1.1.2
> Severity: normal
> 
> 
> Dear Debian folks,
> 
> 
> I see the message below on a Debian Sid/unstable system.
> 
> ```
> $ sudo journalctl -u systemd-udevd
> […]
> […] systemd-udevd[323]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
> ```

We do have users running sysvinit as #1

> 
> If I am not mistaken, this is from the udev rule file [1].
> 
> ```
> ACTION=="add", SUBSYSTEM=="sound", KERNEL=="controlC*", KERNELS!="card*", TEST=="@sbindir@", TEST=="@mydatadir@", GOTO="alsa_restore_go"
> GOTO="alsa_restore_end"
> 
> LABEL="alsa_restore_go"
> TEST!="@daemonswitch@", TEST=="/usr/sbin/alsactl", RUN+="@sbindir@/alsactl -E HOME=@alsactlhome@ restore $attr{device/number}"
> TEST=="@daemonswitch@", TEST=="/usr/sbin/alsactl", RUN+="@sbindir@/alsactl -E HOME=@alsactlhome@ nrestore $attr{device/number}"
> 
> LABEL="alsa_restore_end"
> ```
> 
> Manually running this command shows that `/var/lib/alsa/asound.state` is
> missing.
> 
> ```
> $ sudo /usr/sbin/alsactl -E HOME=/run/alsa restore 0
> /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
> /usr/sbin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid

Could you please try as root:
alsactl init

[...]```
> 
> Is the udev rule still needed?

yes

> I don’t really know, how it’s supposed to
> work, and what I don’t have that file `asound.state`.

Create it as mentioned above

> It would be nice to not run `alsactl` during startup, if it’s failing,
> to get rid of the error message.

What do you think: Is it an error or just a message?

Elimar
-- 
  Alles was viel bedacht wird ist bedenklich!;-)
         Friedrich Nietzsche