From: Leo Famulari <leo@famulari.name>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 40832@debbugs.gnu.org
Subject: bug#40832: alsa-lib cannot find its plugins
Date: Tue, 13 Oct 2020 12:02:59 -0400 [thread overview]
Message-ID: <20201013160259.GA1702@jasmine.lan> (raw)
In-Reply-To: <20200728125241.4ff41418@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
Upstream has implemented (but not yet released) a potential solution:
https://github.com/alsa-project/alsa-lib/commit/8580c081c25678d11278efcb61bd15cf44d0a225
I haven't tested it yet but my understanding is that it supports
specifying a single plugin directory via the ALSA_PLUGIN_DIR environment
variable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-13 16:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 21:37 bug#40832: Audacity does not work with PulseAudio Leo Famulari
2020-04-24 23:15 ` Leo Famulari
2020-04-25 4:03 ` Leo Famulari
2020-04-26 20:03 ` bug#40832: alsa-lib cannot find its plugins Leo Famulari
2020-04-28 21:25 ` bug#40832: Audacity does not work with PulseAudio Ludovic Courtès
2020-04-28 22:39 ` Leo Famulari
2020-05-08 22:45 ` Leo Famulari
2020-05-09 5:24 ` Leo Famulari
2020-05-16 19:33 ` bug#40832: [PATCH 0/2] Help alsa-lib find its plugins Leo Famulari
2020-05-16 19:34 ` bug#40832: [PATCH 1/2] gnu: alsa-plugins: Add GUIX_ALSA_PLUGIN_DIRS search path specification Leo Famulari
2020-05-16 19:34 ` bug#40832: [PATCH 2/2] gnu: Help alsa-lib find its plugins on foreign distros Leo Famulari
2020-05-17 18:19 ` bug#40832: [PATCH 0/2] Help alsa-lib find its plugins Leo Famulari
2020-07-28 10:52 ` bug#40832: alsa-lib cannot " Danny Milosavljevic
2020-07-28 10:56 ` Danny Milosavljevic
2020-07-28 23:56 ` Leo Famulari
2020-07-28 23:56 ` Leo Famulari
2020-07-29 11:18 ` Danny Milosavljevic
2020-10-13 16:02 ` Leo Famulari [this message]
2021-02-01 20:51 ` Leo Famulari
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=20201013160259.GA1702@jasmine.lan \
--to=leo@famulari.name \
--cc=40832@debbugs.gnu.org \
--cc=dannym@scratchpost.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.