unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Zhu Zihao <all_but_last@163.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 54297@debbugs.gnu.org
Subject: bug#54297: Qutebrowser failed to render local fonts.
Date: Mon, 02 May 2022 22:15:43 +0800	[thread overview]
Message-ID: <86k0b43tnn.fsf@163.com> (raw)
In-Reply-To: <Ym+dkI9GKy1STc6T@noor.fritz.box>

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


Yes, this issue should be a duplicate of
https://issues.guix.gnu.org/53011

But I'm not sure whether we can update qtwebengine without touching other Qt components.

Lars-Dominik Braun <lars@6xq.net> writes:

> Hi,
>
> I’ve been experiencing the same issue with RStudio (which uses
> qtwebengine under the hood)[1]. The workaround is the same, but it seems
> qtwebengine 5.15.7 has a fix for this issue[2] caused by an upgrade to
> glibc 2.33. So the solution would be to upgrade our qtwebengine package.
>
> Cheers,
> Lars
>
> [1] https://github.com/guix-science/guix-science/issues/12
> [2] https://bugreports.qt.io/browse/QTBUG-92969


-- 
Retrieve my PGP public key:

  gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F

Zihao

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

  reply	other threads:[~2022-05-02 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 13:29 bug#54297: Qutebrowser failed to render local fonts Zhu Zihao
     [not found] ` <handler.54297.B.16467475122349.ack@debbugs.gnu.org>
2022-03-08 14:42   ` bug#54297: Acknowledgement (Qutebrowser failed to render local fonts.) Zhu Zihao
2022-05-02  9:00 ` bug#54297: Qutebrowser failed to render local fonts Lars-Dominik Braun
2022-05-02 14:15   ` Zhu Zihao [this message]
2022-05-28  3:18 ` Edison Ibáñez
2022-05-28 15:41   ` bdju via Bug reports for GNU Guix

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=86k0b43tnn.fsf@163.com \
    --to=all_but_last@163.com \
    --cc=54297@debbugs.gnu.org \
    --cc=lars@6xq.net \
    /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).