#635622 messages now appearing at boot

Package:
alsa-utils
Source:
alsa-utils
Description:
Utilities for configuring and using ALSA
Submitter:
Date:
2013-12-30 18:12:23 UTC
Severity:
normal
#635622#5
Date:
2011-07-27 16:20:31 UTC
From:
To:
We now see two messages at boot about
alsactr could not restore ... 0 ... no such file or directory
alsactr could not restore ... 1 ... no such file or directory

Problems:
A. Why don't these end up in any log file? Causing me to try to remember
what I saw and type it in above.
B. Why doesn't it say what file it was trying to write to?
C. Why the error in the first place?

#635622#10
Date:
2011-08-02 23:33:04 UTC
From:
To:
I am also seeing these messages at boot time:

  udevd[299]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl
  restore 1': No such file or directory
  udevd[300]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl
  restore 2': No such file or directory
  udevd[302]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl
  restore 0': No such file or directory

I tried looking around at the udev-related scripts packaged with
'alsa-utils'; I found that they essentially do some environment setup and
then run '/etc/init.d/alsa-utils', so I thought there may be some
problem with that file failing.  That was before work this morning, and
I didn't have much time, so the only thing I found so far that looks
like a possible culprit is line 62:

	if MSG="$(alsactl restore $CARD 2>&1 >/dev/null)" && [ ! "$MSG" ] ; then

In this instance the "2>&1" redirection is not at the end of the
command, but in all other instances it is.  Was this intended, or is it
a mistake?

I have some higher priorities to attend to first -- sound is not broken
on my system, so the errors are merely disconcerting -- so I will try to
take a closer look at this by the weekend if the bug has not been
squashed before then.

#635622#15
Date:
2011-08-24 12:06:39 UTC
From:
To:
Dear Dave,


Am Dienstag, den 02.08.2011, 19:33 -0400 schrieb Dave Witbrodt:

You can also use `bts show --mbox 635622`, where `bts` is in the
`devscripts` package, to get the mbox file with all messages related to
that report and reply to it to keep the threading.

I am seeing this too. Does anyone of you remember what (version) change
caused this? I do not see anything related in the changelog entry of
1.0.24.

I tried looking at the Subversion repository for possible changes [1],
but I could not even find a link to display the commit log/history in
ViewVC.


Thanks,

Paul


[1] http://anonscm.debian.org/viewvc/pkg-alsa/trunk/alsa-utils/