From: Leo Famulari <leo@famulari.name>
To: 53011@debbugs.gnu.org
Subject: bug#53011: Possible to Update qtbase-5 to v5.15.8?
Date: Tue, 4 Jan 2022 13:04:41 -0500 [thread overview]
Message-ID: <YdSMOd9lJ5p3C0b+@jasmine.lan> (raw)
In-Reply-To: <28974452.1530175.1641317754644@mail.yahoo.com>
On Tue, Jan 04, 2022 at 05:35:54PM +0000, Jaft via Bug reports for GNU Guix wrote:
> Partially because it's the latest version but primarily because there's a bug in the current version for QTwebengine.
> As detailed at r/qutebrowser - Comment by u/The-Compiler on ”WebGL blacklisted on Guix”, most text gets broken (https://bugs.chromium.org/p/chromium/issues/detail?id=1164975); I haven't tried other browsers but I've experienced this with Qutebrowser, currently.
> It seems the issue was addressed in QT v5.15.7 so an update to, at least, that would, theoretically, solve the problem.
I wonder if this is related to <https://issues.guix.gnu.org/52993>
("There is a problem with text rendering in the anki").
next prev parent reply other threads:[~2022-01-04 18:07 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 [this message]
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
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=YdSMOd9lJ5p3C0b+@jasmine.lan \
--to=leo@famulari.name \
--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).