bug#52993: closed (There is a problem with text rendering in the anki)

[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 There is a problem with text rendering in the anki
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: 
>
> There is a problem with text rendering in the anki
>
>
>
>
> Date: 
>
> Tue, 04 Jan 2022 00:30:28 +0100
>
>
>
>
> User-agent: 
>
> mu4e 1.6.10; emacs 28.0.50
>
>
>
>
> Hi,
>
> I use a flashcard program anki (version: 2.1.16). And today (after the
> `guix pull; guix package -u` commands) it's stop working
> properly. Please see a pic: https://i.imgur.com/EqWtnrb.png usually it
> looks something like https://josh.works/images/17-05-16-anki.jpg
>
>
> here is my current and previous generations:
> https://pastebin.com/qaMKSmaX
>
> After I switched back to the generation 133, anki started to work again.
> Please feel free to ask if I can provide more data.
> -- 
> With best regards,
> Igor Gajsin
>
>
>
> --- 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 ---