bug#52672: closed (qutebrowser 2.4.0 text rendering broken)

[GNU bug Tracking System]

Your message dated Tue, 28 Mar 2023 20:38:26 -0400
with message-id <878rfg75od.fsf@gmail.com>
and subject line Re: bug#53011: Possible to Update qtbase-5 to v5.15.8?
has caused the debbugs.gnu.org bug report #53011,
regarding qutebrowser 2.4.0 text rendering broken
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53011: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53011
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: qutebrowser 2.4.0 text rendering broken Date: Sun, 19 Dec 2021 16:39:20 -0600

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
Description: PNG image

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#53011: Possible to Update qtbase-5 to v5.15.8?
>
>
>
>
> Date: 
>
> Tue, 28 Mar 2023 20:38:26 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
>
>
>
>
> Hi,
>
> Jaft <wamm_kd_schmelingski@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
>
>
> --- End Message ---