From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Csepp <raingloom@riseup.net>, 64200@debbugs.gnu.org
Subject: bug#64200: Netsurf very frequently freezes when editing text (Harfbuzz issue?)
Date: Wed, 21 Jun 2023 14:46:32 +0000 [thread overview]
Message-ID: <87o7l8g9fg.fsf@protonmail.com> (raw)
In-Reply-To: <87ilbh41xx.fsf@jpoiret.xyz>
Hi Josselin and Csepp,
On Wed, Jun 21, 2023 at 11:08 AM, Josselin Poiret wrote:
> 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.
>
Likely that it was just overlooked, these things happen. Despite being
two major releases behind, our version is less than a year old at
least, so it wasn't completely forgotten :)
I just tried a guix build harfbuzz --with-latest=harfbuzz and it
worked, but I only built once and didn't try dependents. A quick look
at the changelog shows mostly fixes and new API, doesn't look like
anything immediately obvious as breaking, but this will affect ~9000
packages.
I do think this could be a more impactful change than the Mesa update
but I say we put them all on a feature branch and see how the builds
work out. If harfbuzz needs more work than it seems, we can just hold
off on it and group it with the inevitable next Mesa update or some
other related packages.
How does that sound? I'll give it some days for comments on my
previous message about a Mesa branch but the patches here are all
trivial (so far...) so it would be nice to get builds started soon. My
thoughts for Mesa were hopefully just a few days of checking builds
and then merging, to keep it simple and straightforward. But we should
group builds together rather than wasting resources.
John
PS: Csepp if you can reproduce the build failure and attach a log
somewhere, that would be helpful. If newer harfbuzz is helpful but too
drastic of a change everywhere, we could have a 'harfbuzz-next' to
ease the transition.
PPS: I'll bring this up elsewhere, but on a similar vein I noticed our
freetype package is built without brotli support (anyone know why?).
It is needed for the update to Godot 4. I'll raise the details on a
forthcoming Godot patch.
next prev parent reply other threads:[~2023-06-21 14:47 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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7l8g9fg.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).