unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Florian Bruhin <me@the-compiler.org>
To: 53011@debbugs.gnu.org
Subject: bug#53011: Possible to Update qtbase-5 to v5.15.8?
Date: Tue, 4 Jan 2022 21:32:10 +0100	[thread overview]
Message-ID: <20220104203210.s4b52rccx2xrzexm@aragog> (raw)
In-Reply-To: <28974452.1530175.1641317754644@mail.yahoo.com>

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

As for qutebrowser, this can be considered a duplicate of:
https://issues.guix.gnu.org/52672 ("qutebrowser 2.4.0 text rendering
broken").

The Anki bug could indeed be the same. If I remember correctly, Anki
does use QtWebEngine.

-- 
            me@the-compiler.org | https://www.qutebrowser.org 
       https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
       GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
             I love long mails! | https://email.is-not-s.ms/

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

  parent reply	other threads:[~2022-01-04 20:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28974452.1530175.1641317754644.ref@mail.yahoo.com>
2022-01-04 17:35 ` bug#53011: Possible to Update qtbase-5 to v5.15.8? Jaft via Bug reports for GNU Guix
2022-01-04 18:03   ` Leo Famulari
2022-01-04 18:04   ` Leo Famulari
2022-01-04 18:04   ` Florian Bruhin
2022-01-05  7:07     ` Philip McGrath
2022-01-05 19:08     ` Leo Famulari
2022-01-05 19:09       ` Leo Famulari
2022-02-02 19:15         ` Jaft via Bug reports for GNU Guix
2022-01-04 20:32   ` Florian Bruhin [this message]
2022-01-05 19:10   ` bug#53011: [PATCH] gnu: Fix text rendering in QtWebEngine Leo Famulari
2022-07-01 22:08   ` bug#53011: Qt patches for 5.15.5 phodina via Bug reports for GNU Guix
2023-03-29  0:38   ` bug#53011: Possible to Update qtbase-5 to v5.15.8? Maxim Cournoyer

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=20220104203210.s4b52rccx2xrzexm@aragog \
    --to=me@the-compiler.org \
    --cc=53011@debbugs.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.
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).