� ���, 29.06.2002, � 23:17, Michael Reinsch �������:
>
> I did some further research on this topic and realized that I got
> something wrong: it is not because of libasound.so as I said before. It
> seems to depend on /usr/share/alsa/alsa.conf which it (alsamixer in the
> case below) tries to open:
>
> stat64("/usr/share/alsa/alsa.conf", 0xbffff300) = -1 ENOENT (No such file
> or directory)
> write(2, "ALSA lib control.c:601:(snd_ctl_"..., 47ALSA lib
> control.c:601:(snd_ctl_open_noupdate) ) = 47
>
> If you install libalsa2-devel, alsamixer works. If you remove
> libalsa2-devel but keep alsa.conf, alsamixer works also. If you remove
> alsa.conf, alsamixer doesn't work.
>
That makes sense. I too was surprised because those ALSA programs I was
interested in were correctly linked with versioned libasound.
Probably we need something like alsa-common or just libalsa without
version like GNOME2 application currently do.
-andrej
