From: Julien Lepiller <julien@lepiller.eu>
To: 43628@debbugs.gnu.org, pratheblackdiamond@gmail.com
Subject: [bug#43628] Further Info
Date: Sat, 26 Sep 2020 05:43:15 -0400 [thread overview]
Message-ID: <561466E3-006A-4460-9DEA-61A8DC16E7A8@lepiller.eu> (raw)
In-Reply-To: <CAFw+=j2tXki8ce=AQN=htY0tqp_k0CnDaPFur8UCDLyYVyy1BA@mail.gmail.com>
Hi Prafulla,
Le 26 septembre 2020 03:31:38 GMT-04:00, Prafulla Giri <pratheblackdiamond@gmail.com> a écrit :
>Another information:
>
>I have other programs on my foreign system (installed via guix) that
>produce sound well, without any issues. They include:
>espeak and kdenlive.
>
>Also, I did try making the union-build use copies instead of symlinks
>using
>(union-build ... #:symlink copy-recursively) but that didn't work out
>either.
>
>Now, I'm going to take a look at fixing the pkg-config rules, and will
>be
>updating this thread should that resolve this issue.
>
>On Sat, Sep 26, 2020 at 12:21 PM Prafulla Giri
><pratheblackdiamond@gmail.com>
>wrote:
>
>> I forgot to mention, but the union-build works. If one `guix build`s
>the
>> union package, and cd into the /gnu/store/...-union-build, one will
>see
>> that things are there as it should be (lib/normal-alsa-*.so and
>> lib/alsa-lib/*pulse*.so).
>>
>> It's just that aegisub seems to be looking from the
>> /gnu/store/normal-alsa-lib-dir instead of
>/gnu/store/union-alsa-package.
>>
I think the issue with the union-build is that it is completely ignored: alsa doesn't look in it's current directory for plugins, but in the directory where it's been configured (at build time) to look for.
On the Guix System, there is a service that creates a /etc/asound.conf, which references alsa-plugins:pulseaudio. Maybe you actually want to configure that? Maybe try to copy this to a new file .asoundrc:
pcm_type.pule {
lib "/home/foo/.guix-profile/lib/alsa-lib/libasound_module_pcm_pulse.so"
}
ctl_type.pulse {
lib"/home/foo/.guix-profile/lib/alsa-lib/libasound_module_ctl_pulse.so"
}
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
next prev parent reply other threads:[~2020-09-26 9:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 6:15 [bug#43628] Request for patch evaluation/review Prafulla Giri
2020-09-26 6:36 ` [bug#43628] Further Info Prafulla Giri
2020-09-26 7:31 ` Prafulla Giri
2020-09-26 9:43 ` Julien Lepiller [this message]
2020-09-26 9:57 ` Prafulla Giri
2020-09-26 12:07 ` Prafulla Giri
2020-09-26 14:35 ` Julien Lepiller
2020-09-26 20:46 ` Prafulla Giri
2020-09-26 21:15 ` Julien Lepiller
2020-09-27 5:56 ` Prafulla Giri
2020-09-27 11:09 ` Julien Lepiller
2020-09-28 14:43 ` Prafulla Giri
2020-09-28 15:20 ` Julien Lepiller
2020-09-26 9:51 ` [bug#43628] Progress (?) Prafulla Giri
2020-09-28 17:02 ` [bug#43628] Request for patch evaluation/review 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=561466E3-006A-4460-9DEA-61A8DC16E7A8@lepiller.eu \
--to=julien@lepiller.eu \
--cc=43628@debbugs.gnu.org \
--cc=pratheblackdiamond@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).