From: Elias Kueny <elias.kueny@posteo.net>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: How to make audio devices available with guix shell --container
Date: Tue, 06 Dec 2022 17:01:17 +0000 [thread overview]
Message-ID: <878rjktozq.fsf@posteo.net> (raw)
In-Reply-To: <e79f20d6-b70f-6e31-42e4-7d4f71681d15@disroot.org>
On Mon, Dec 05 2022, kiasoc5 wrote:
> About the sound, I believe you will need to expose the pulseaudio
> and/or pipewire sockets. You can reference bubblewrap configuration
> since it also works by sharing/exposing files.
>
> https://wiki.archlinux.org/title/Bubblewrap/Examples#Chromium
Thank you, that helped me progress. I noticed there were errors about not being able to connect to DBUS, now the following got rid of those:
guix shell -C -N -P --no-cwd \
--share=/dev/ \
--preserve='^DISPLAY$' --preserve='^XAUTHORITY$' --expose="$XAUTHORITY" \
--preserve='^DBUS_.*' --expose=/var/run/dbus/system_bus_socket \
--expose="$XDG_RUNTIME_DIR/pulse" \
ungoogled-chromium -- chromium --app="https://meet.jit.si"
With this, I can use the microphone (there is no default microphone available, but my internal microphone can be selected and works), but I still have no sound.
ALSA throws the error "The field ipc_gid must be a valid group (create group audio)", and indeed /etc/group in the container doesn't contain an audio group (only users and overflow).
But `--expose=/etc/group` prevents the creation of the container with the error "guix shell: error: rename-file: Device or resource busy".
So the next question is: how does one uses groups in the container?
next prev parent reply other threads:[~2022-12-06 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 17:41 How to make audio devices available with guix shell --container Elias Kueny
2022-12-06 3:47 ` kiasoc5
2022-12-06 17:01 ` Elias Kueny [this message]
2023-01-08 11:19 ` Gabriel Wicki
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=878rjktozq.fsf@posteo.net \
--to=elias.kueny@posteo.net \
--cc=help-guix@gnu.org \
--cc=kiasoc5@disroot.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.