Hi,

I am also experiencing the same issue.

It looks like a build issue. Here is the interesting part from an strace
of alsamixer:

stat64("/home/jordi/svn/pkg-alsa/trunk/build-area/alsa-lib-1.0.11//share/alsa/alsa.conf",
0xbf9f494c) = -1 ENOENT (No such file or directory)
write(2, "ALSA lib control.c:816:(snd_ctl_"..., 47ALSA lib
control.c:816:(snd_ctl_open_noupdate) ) = 47
write(2, "Invalid CTL default", 19Invalid CTL default)     = 19
write(2, "\n", 1
)                       = 1

It's trying to use
"/home/jordi/svn/pkg-alsa/trunk/build-area/alsa-lib-1.0.11//share/alsa/alsa.conf"
by the looks of things.

I have proved this further with an "mkdir -p
/home/jordi/svn/pkg-alsa/trunk/build-area/alsa-lib-1.0.11//share/alsa"
and then copying /usr/share/alsa/alsa.conf to this location.

alsamixer will then run but there are other references to this incorrect
location.

Should the severity of this be changed to "grave" as ALSA doesn't give
any sound due to the above problem?

David.
-- 
 .''`.     David Ramsden <david_|at|_hexstream.co.uk>
: :'  :    http://david.hexstream.co.uk/
`. `'`     PGP key ID: 507B379B on subkeys.pgp.net
  `-  Debian - Because it works (tm).

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to