[Pkg-alsa-devel] Bug#451244: Bug#451244: Bug#451244: alsa-utils: init script should call alsactl restore with -F option

[Frans Pop]

On Wednesday 14 November 2007, you wrote:
> What happens if you do
> # rm /var/lib/alsa/asound.state
> # alsactl store
> # alsactl restore
> ?

The thing is: I shouldn't have to.
I've seen this happen before when there have been changes in the kernel for 
my soundcard and according to upstream alsa they should be suppressed by 
default in the initscript by using -F.

Also note that these errors only happen once: when the driver changes its 
hardware support. The next boot with the same kernel, the "store" on 
shutdown will have written the correct values for the new driver.

So removing the state file is not needed; the "problem" fixes itself. We 
just need to ignore these (expected) errors when there are driver changes.

> -F is only used if alsactl restore failes and returns nonzero

If you want to discuss the appropriate or not appropriate use of the -F 
flag, please do so with the upstream alsa people.
I'm only forwarding you what they told me: the -F flag should be used by 
default in the init script to avoid such errors.

AFAICT this seems to match the text in the manpage:
       -F, --force
              Used  with restore command.  Try to restore the matching
              control elements as much as possible.

I interpret that as: if there are changes in the driver, just restore the 
settings that are still appropriate and don't complain about the rest.