From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: Josselin Poiret <dev@jpoiret.xyz>, 64200@debbugs.gnu.org
Subject: bug#64200: Netsurf very frequently freezes when editing text (Harfbuzz issue?)
Date: Thu, 22 Jun 2023 01:08:21 +0000 [thread overview]
Message-ID: <87jzvwfgn3.fsf@protonmail.com> (raw)
In-Reply-To: <87mt0smpz4.fsf@riseup.net>
Dear Csepp,
On Thu, Jun 22, 2023 at 12:00 AM, Csepp wrote:
>
> So, I built Netsurf with --with-latest=harfbuzz, which also affected
> GTK+ and a bunch of other packages along the way, and it worked on my
> first attempt, just needed a stronger machine.
> I copied over the resulting Netsurf to my laptop and have been using it
> all day today, it seems to have shooed that bug away.
> (Don't squash bugs, bugs are good for the ecosystem. They are only a
> problem when they get inside your mainframe and cause a short. UwU)
> BTW there was no log when it caused my system to hang. I had to reboot
> it with sysrq. Probably a kernel bug?
>
> So it looks like Harfbuzz can be updated without any problem.
Great, that's good to hear and a nontrivial test too! I'll await
comments on this mesa+friends update branch and plan on including the
harfbuzz update there. Stay tuned...
John
next prev parent reply other threads:[~2023-06-22 1:09 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
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 [this message]
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=87jzvwfgn3.fsf@protonmail.com \
--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.