Broken alsa-utils?

Broken alsa-utils?

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]


Since about a week or two ago, the alsa-utils tools such as amixer and
alsamixer fail to start:

--8<---------------cut here---------------start------------->8---
> amixer
ALSA lib dlmisc.c:292:(snd1_dlobj_cache_get) Cannot open shared library /gnu/store/5cbff8yc8f8qgcjrikmdf32pg4jy7inp-alsa-lib-1.1.6/lib/alsa-lib/libasound_module_ctl_pulse.so ((null): /gnu/store/5cbff8yc8f8qgcjrikmdf32pg4jy7inp-alsa-lib-1.1.6/lib/alsa-lib/libasound_module_ctl_pulse.so: cannot open shared object file: No such file or directory)
amixer: Mixer attach default error: No such device or address
--8<---------------cut here---------------end--------------->8---

And the aforementioned file is missing indeed.

I see that in commit 2101cc3fb691f443b830fdf5f846ded5fa018739 Julien
patched alsa-lib to use ALSA_PLUGIN_DIR.  Could be the culprit?

-- 
Pierre Neidhardt

Luck, that's when preparation and opportunity meet.
		-- P.E. Trudeau

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Broken alsa-utils?

[Kei Kebreau]

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

Pierre Neidhardt <ambrevar@gmail.com> writes:

> Since about a week or two ago, the alsa-utils tools such as amixer and
> alsamixer fail to start:
>
>> amixer
> ALSA lib dlmisc.c:292:(snd1_dlobj_cache_get) Cannot open shared library /gnu/store/5cbff8yc8f8qgcjrikmdf32pg4jy7inp-alsa-lib-1.1.6/lib/alsa-lib/libasound_module_ctl_pulse.so ((null): /gnu/store/5cbff8yc8f8qgcjrikmdf32pg4jy7inp-alsa-lib-1.1.6/lib/alsa-lib/libasound_module_ctl_pulse.so: cannot open shared object file: No such file or directory)
> amixer: Mixer attach default error: No such device or address
>
> And the aforementioned file is missing indeed.
>
> I see that in commit 2101cc3fb691f443b830fdf5f846ded5fa018739 Julien
> patched alsa-lib to use ALSA_PLUGIN_DIR.  Could be the culprit?

Hi Pierre,

I just noticed that there are some commits on the staging branch that
might take care of this issue (specifically commits 1e3861eb and 3272bcfd).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: Broken alsa-utils?

[Charlie Ritter]

Pierre Neidhardt <ambrevar@gmail.com> writes:

> Since about a week or two ago, the alsa-utils tools such as amixer and
> alsamixer fail to start:
>
>> amixer
> ALSA lib dlmisc.c:292:(snd1_dlobj_cache_get) Cannot open shared library /gnu/store/5cbff8yc8f8qgcjrikmdf32pg4jy7inp-alsa-lib-1.1.6/lib/alsa-lib/libasound_module_ctl_pulse.so ((null): /gnu/store/5cbff8yc8f8qgcjrikmdf32pg4jy7inp-alsa-lib-1.1.6/lib/alsa-lib/libasound_module_ctl_pulse.so: cannot open shared object file: No such file or directory)
> amixer: Mixer attach default error: No such device or address
>
> And the aforementioned file is missing indeed.
>
> I see that in commit 2101cc3fb691f443b830fdf5f846ded5fa018739 Julien
> patched alsa-lib to use ALSA_PLUGIN_DIR.  Could be the culprit?

Put this in your ~/.asoundrc:

    pcm.!default {
      type hw
      card 0
    }

    ctl.!default {
      type hw
      card 0
    }

Re: Broken alsa-utils?

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 195 bytes --]


It worked!

Can you explain the workaround?

-- 
Pierre Neidhardt

My doctor told me to stop having intimate dinners for four.  Unless there
are three other people.
		-- Orson Welles

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Broken alsa-utils?

[Ricardo Wurmus]

Pierre Neidhardt <ambrevar@gmail.com> writes:

> It worked!
>
> Can you explain the workaround?

IIUC this just overrides the settings in /etc/asound.conf, which
configure the pcm default to go through the pulseaudio plugin.

I don’t recommend changing this with ~/.asoundrc.  If you really want
this changed it’s better to change the Guix system service that
generates /etc/asound.conf.  I also don’t recommend changing that
service, though, because applications do spawn pulseaudio automatically,
and that will block your audio hardware.  With the asoundrc override you
force other applications to use the blocked audio hardware.

--
Ricardo