From: Martin via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 47092@debbugs.gnu.org
Subject: bug#47092: Icecat sandbox causes issues with fonts in --pure env
Date: Fri, 12 Mar 2021 09:03:57 +0000 [thread overview]
Message-ID: <984f327f-c850-1a41-cfd5-367918d18f23@disroot.org> (raw)
Hello,
whenever I'm trying to run 'guix environment --pure --ad-hoc icecat --
icecat' or similar commands in a --container I'm ending up with some
tofu ugly font fallback box glyphs in the app. However everything works
fine running 'guix environment --ad-hoc icecat -- icecat'. Moreover I've
noticed that when I edit the default value of
"security.sandbox.content.level" from 4 to 2 in "about:config" then the
problem disappear and the fonts are properly displayed in --pure and
--container env. I was trying to install all possible fonts, running
'fc-cache -rfv' and analyze the icecat logs with "MOZ_SANDBOX_LOGGING=1"
to include blocking paths into the
"security.sandbox.content.read_path_whitelist" but still I couldn't fix
this issue with the icecat default sandbox level. Any ideas how to solve
it in Guix System and what are the side effects of using
"security.sandbox.content.level=2" in --pure env?
Kind regards!
Martin
security.sandbox.content.read_path_whitelist
next reply other threads:[~2021-03-12 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 9:03 Martin via Bug reports for GNU Guix [this message]
2021-03-12 9:53 ` bug#47092: Icecat sandbox causes issues with fonts in --pure env 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
[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=984f327f-c850-1a41-cfd5-367918d18f23@disroot.org \
--to=bug-guix@gnu.org \
--cc=47092@debbugs.gnu.org \
--cc=smartin@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 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).