From: Zhu Zihao <all_but_last@163.com>
To: jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: What's missing from qutebrowser for text rendering?
Date: Tue, 03 Jan 2023 11:45:50 +0800 [thread overview]
Message-ID: <864jt8z34l.fsf@163.com> (raw)
In-Reply-To: <f3e65fc509e18f4f567c9f7a04c074b7@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
This is a known bug of qtwebengine, it's not related to your font
settings. It's about glibc and the sandbox of qtwebengine.
See here for more detail:
https://bugs.chromium.org/p/chromium/issues/detail?id=1164975
It's not fixed because the open source support of Qt 5 series is end. Only
commercial support can get the patch(Qt 5.15.8).
If we want to fix this, we may give the KDE's Qt branch a look. AFAIK,
Archlinux use it.
A simple workaround for your problem is: Disable the sandbox.
"jgart" <jgart@dismail.de> writes:
> hi guixers,
>
> what am I missing from qutebrowser to render text from sites like wikipedia and g-golf documentation site?
>
> See this screenshot (will expire in a week):
>
> https://up.nixnet.services/j80xqgx7.png
>
> has anyone else run into this issue?
>
> I'm on guix system and I installed qutebrowser via my guix home profile
>
> Does qutebrowser on guix system require me to explicitly install fonts for it?
>
> all best
--
Retrieve my PGP public key:
gpg --recv-keys B3EBC086AB0EBC0F45E0B4D433DB374BCEE4D9DC
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2023-01-03 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 17:34 What's missing from qutebrowser for text rendering? jgart
2023-01-02 17:35 ` Tobias Geerinckx-Rice
2023-01-02 17:39 ` jgart
2023-01-02 17:48 ` Tobias Geerinckx-Rice
2023-01-02 18:08 ` jgart
2023-01-03 3:45 ` Zhu Zihao [this message]
2023-01-04 0:55 ` jgart
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=864jt8z34l.fsf@163.com \
--to=all_but_last@163.com \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/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.