On Oct 19, 2015, at 10:12 AM, <to...@tuxteam.de> <to...@tuxteam.de> wrote:
> What lets you think you need a package (or file) named alsa-lib? >>> root@sbox:~# alsamixer >>> ALSA lib dlmisc.c:254:(snd1_dlobj_cache_get) Cannot open shared library >>> /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_ctl_pulse.so >>> cannot open mixer: No such device or address >> >> Going down that series of directories with 'ls <tab>', I don't seem to have >> alsa-lib. I looked on the web, and all I could find was source code for it. >> I doubt that compiling the code is required for such a (seemingly) common >> library. That running alsamixer says it can't run because of the above error message, and that the directory /usr/lib/x86_64-linux-gnu/alsa-lib/ doesn't exist on my machine. > There's no package alsa-lib; That would certainly explain why I couldn't find it :-) > apt-file (recommended) shows a couple of > packages having directories with that name, I didn't know about apt-file, but it does find alsa-lib (and the module alsamixer was looking for) -- in libasound2-plugins, so I installed it. Now: > root@sbox:~# alsamixer > ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: > Connection refused > > cannot open mixer: Connection refused Do I need to do something about pulsaAudio? I think I've read that it's possible to deal with just alsa. No? (I haven't done any audio work on Debian since the Lenny days.) -- Glenn English