From: Martin via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>, 47092@debbugs.gnu.org
Subject: bug#47092: Icecat sandbox causes issues with fonts in --pure env
Date: Fri, 12 Mar 2021 11:09:58 +0000 [thread overview]
Message-ID: <08906e6f-ea39-e1c6-b16e-72a7768a5960@disroot.org> (raw)
In-Reply-To: <86im5wir0t.fsf@gmail.com>
On 3/12/21 10:51 AM, zimoun wrote:
> Indeed, the package eolie is broken; which is another issue–and BTW
> thanks for pointing this out. Back to your initial report about icecat,
> what about something like that:
>
> --8<---------------cut here---------------start------------->8---
> guix environment --preserve='^DISPLAY$' --container --network \
> --expose=/etc/machine-id \
> --expose=/etc/ssl/certs/ \
> --share=$HOME/.local/share/icecat/=$HOME/.local/share/icecat/ \
> --ad-hoc icecat nss-certs dbus -- icecat
> --8<---------------cut here---------------end--------------->8---
It's still not relevant to my issue. To run icecat using your example
you should change one parameter to
"--share=$HOME/.mozilla=$HOME/.mozilla" but again with the default
"security.sandbox.content.level=4" the fonts will be tofued. I think
once the issue could be fixed with simpler command, i.e. 'guix
environment --pure --ad-hoc icecat -- icecat' than it would be easier to
port the solution on the --container case.
Kind regards!
Martin
next prev parent reply other threads:[~2021-03-12 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 9:03 bug#47092: Icecat sandbox causes issues with fonts in --pure env Martin via Bug reports for GNU Guix
2021-03-12 9:53 ` zimoun
2021-03-12 10:15 ` Martin via Bug reports for GNU Guix
2021-03-12 10:51 ` zimoun
2021-03-12 11:09 ` Martin via Bug reports for GNU Guix [this message]
[not found] ` <d45ebb57-fed2-e77a-804e-73d8cbcf4d76@disroot.org>
2021-03-12 10:21 ` zimoun
2021-10-28 11:15 ` Martin via Bug reports for GNU Guix
2021-10-28 18:49 ` Mark H Weaver
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=08906e6f-ea39-e1c6-b16e-72a7768a5960@disroot.org \
--to=bug-guix@gnu.org \
--cc=47092@debbugs.gnu.org \
--cc=smartin@disroot.org \
--cc=zimon.toutoune@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).