all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kei Kebreau <kkebreau@posteo.net>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Broken alsa-utils?
Date: Wed, 27 Jun 2018 10:08:19 -0400	[thread overview]
Message-ID: <87tvpogw4s.fsf@posteo.net> (raw)
In-Reply-To: <87fu19lsf2.fsf@gmail.com> (Pierre Neidhardt's message of "Tue, 26 Jun 2018 13:05:05 +0200")

[-- 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 --]

  reply	other threads:[~2018-06-27 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 11:05 Broken alsa-utils? Pierre Neidhardt
2018-06-27 14:08 ` Kei Kebreau [this message]
2018-06-27 19:57 ` Charlie Ritter
2018-06-27 21:22   ` Pierre Neidhardt
2018-06-27 21:57     ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tvpogw4s.fsf@posteo.net \
    --to=kkebreau@posteo.net \
    --cc=ambrevar@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.