unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tirifto <tirifto@posteo.cz>
To: help-guix@gnu.org
Subject: Icecat with Firejail (on a non-Guix system)
Date: Fri, 6 Dec 2019 14:56:55 +0100	[thread overview]
Message-ID: <20191206145655.18764319@posteo.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

Hello all!

I've used Guix on Parabola GNU+Linux-libre to install Icecat, but I'm
having trouble running Icecat in the sandboxing tool Firejail [1]. The
problem is that whenever I start Icecat via firejail, the fonts are
completely broken and the browser only displays tofu in place of every
character. I'm sending some error messages as an attachment, which look
like they are related. In case the attachment doesn't make it through,
here is a sample:

> (/gnu/store/20622y5w8ixlh6zbrbzv5934wcshvi64-icecat-68.2.0-guix0-
> preview3/lib/icecat/.icecat-real:46):
> Pango-WARNING **: 13:17:17.854: scaled_font status is: file not found

Does anyone happen to have experience with a similar problem, or some
idea how it may be fixed? There's an open issue on Firejail's bug
tracker [2]. I think what I need to do with Icecat is to figure out
which files/directories it needs to access, and for Firejail it's to
figure out how to grant the access. Advice for either would be
appreciated.

Best wishes
// Tirifto

-----------------------------------------------------------------------
1. https://firejail.wordpress.com/
2. https://github.com/netblue30/firejail/issues/3020

[-- Attachment #2: icecaterr.txt.gz --]
[-- Type: application/gzip, Size: 498 bytes --]

             reply	other threads:[~2019-12-06 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 13:56 Tirifto [this message]
2019-12-06 16:07 ` Icecat with Firejail (on a non-Guix system) david larsson

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=20191206145655.18764319@posteo.cz \
    --to=tirifto@posteo.cz \
    --cc=help-guix@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).