From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Mike Gerwitz <mtg@gnu.org>,
Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Documenting current state of isolating icecat
Date: Thu, 27 Jun 2019 12:18:44 +0200 [thread overview]
Message-ID: <87h88b1gcb.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87ef3f67ql.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
Thanks for bringing this back up.
Regarding the audio, there was this discussion more recently:
https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00340.html
Which led to the implementation of some changes around user IDs.
With that patch, I still wasn't able to get around sound to work, as
explained in the thread.
Apparently it's possible to get sound to work with Docker.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-06-27 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 16:58 Documenting current state of isolating icecat Christopher Lemmer Webber
2019-06-27 3:13 ` Mike Gerwitz
2019-06-27 10:18 ` Pierre Neidhardt [this message]
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=87h88b1gcb.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=mtg@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.
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).