GNU bug report logs - #53011
Possible to Update qtbase-5 to v5.15.8?

Previous Next

Package: guix;

Reported by: Jaft <wamm_kd_schmelingski <at> yahoo.com>

Date: Tue, 4 Jan 2022 17:37:01 UTC

Severity: normal

Merged with 52672, 52993

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: "bdju" <bdju <at> tilde.team>
Subject: bug#52672: closed (Re: bug#53011: Possible to Update qtbase-5 to
 v5.15.8?)
Date: Wed, 29 Mar 2023 00:39:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#53011: qutebrowser 2.4.0 text rendering broken

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 52672 <at> debbugs.gnu.org.

-- 
53011: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53011
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Jaft <wamm_kd_schmelingski <at> yahoo.com>
Cc: Florian Bruhin <me <at> the-compiler.org>,
 Philip McGrath <philip <at> philipmcgrath.com>, 53011-done <at> debbugs.gnu.org,
 Leo Famulari <leo <at> famulari.name>, phodina <phodina <at> protonmail.com>,
 bdju <bdju <at> tilde.team>
Subject: Re: bug#53011: Possible to Update qtbase-5 to v5.15.8?
Date: Tue, 28 Mar 2023 20:38:26 -0400
Hi,

Jaft <wamm_kd_schmelingski <at> yahoo.com> writes:

> 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've updated the Qt 5 packages to 5.15.8 on staging; feel free to give
it a shot in the next week or so, after which I'll consider merging the
staging branch to master if there are no blockers.

-- 
Thanks,
Maxim

[Message part 3 (message/rfc822, inline)]
From: "bdju" <bdju <at> tilde.team>
To: <bug-guix <at> gnu.org>
Subject: qutebrowser 2.4.0 text rendering broken
Date: Sun, 19 Dec 2021 16:39:20 -0600
[Message part 4 (text/plain, inline)]
I'm told it's this bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=1164975

and it's related to haveing an old QtWebEngine + new glibc

Fix here:
https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/374232

I think the QtWebEngine package just needs to be updated, but I'll leave
it up to the experts.

I attached a screenshot showing the issue on a github page.
You can temporarily get around the issue with special launch options
(including not using your usual settings)

qutebrowser --temp-basedir --qt-flag disable-seccomp-filter-sandbox
[2021-12-19-163833_grim.png (image/png, attachment)]

This bug report was last modified 2 years and 54 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.