From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Csepp <raingloom@riseup.net>, 64200@debbugs.gnu.org
Cc: John Kehayias <john.kehayias@protonmail.com>
Subject: bug#64200: Netsurf very frequently freezes when editing text (Harfbuzz issue?)
Date: Wed, 21 Jun 2023 11:08:58 +0200 [thread overview]
Message-ID: <87ilbh41xx.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87a5wto7da.fsf@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hi Csepp,
Csepp <raingloom@riseup.net> writes:
> Like the title says. It never happens when just browsing, but happens
> very frequently (like a minute after starting to type) when editing
> text, at least on Brutaldon, but maybe on other sites too.
>
> I noticed that our Harfbuzz package is two entire major releases behind.
> Maybe there are bugfixes in the latest one that we could use?
>
> I tried building it but it froze up my laptop for some reason (rather
> strange, even if it runs out of memory it should just be killed by
> earlyoom) so I haven't attempted to test this theory yet.
>
> Is there any particular reason Harfbuzz wasn't covered by the last
> core-updates? If it turns out to be a bug in it, what would be the best
> way to proceed?
core-updates was lagging behind, and while merging you don't want to
introduce potential sources of issues. This could maybe go into the
graphics updates along with mesa, if John thinks it's appropriate.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-06-21 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 2:47 bug#64200: Netsurf very frequently freezes when editing text (Harfbuzz issue?) Csepp
2023-06-21 9:08 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-06-21 14:46 ` John Kehayias via Bug reports for GNU Guix
2023-06-21 22:00 ` Csepp
2023-06-22 1:08 ` John Kehayias via Bug reports for GNU Guix
2023-06-26 2:16 ` Csepp
2023-06-29 15:06 ` John Kehayias via Bug reports for GNU Guix
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilbh41xx.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=64200@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=john.kehayias@protonmail.com \
--cc=raingloom@riseup.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.