From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id iErmKCd0k2QNXQEASxT56A (envelope-from ) for ; Thu, 22 Jun 2023 00:05:27 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id uIEgKCd0k2T/aQAAG6o9tA (envelope-from ) for ; Thu, 22 Jun 2023 00:05:27 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 4C98F3BF4F for ; Thu, 22 Jun 2023 00:05:27 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=riseup.net header.s=squak header.b=bkclkQHq; dmarc=fail reason="SPF not aligned (relaxed)" header.from=riseup.net (policy=none); spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1687385127; a=rsa-sha256; cv=none; b=DMBCUSN536EsI52cpTiPKCJ3OXOG94QrxDmVxx3rh//et7Eho0MJJx9n4Z5eznO6ezayVI 2KTN0KUpQr9lPUoyyrtMbAx/XW9PN7+fO5ahSnG6Sk7rsS3KsHC9WBi6DPVDrtxHCh2zUY ZpBX7uh0RR/tUYIyBLPuBk+fv2b0gX1W+UnevIvEAD9RUGdU9mQpO//WGwktP5G5p5VHDY GTg7/JN8mlI1heCL53peFQ4Hp1CAtJ85HhO/okM8It3srt5ZEQuIQd4ux97e3aUI73D93C oS73Kj8g3e3f1dNJVefkPT3kO+BqQk7rf9+6Zxqa/1b+QizO//WKulf97+ZSwQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=riseup.net header.s=squak header.b=bkclkQHq; dmarc=fail reason="SPF not aligned (relaxed)" header.from=riseup.net (policy=none); spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1687385127; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:resent-cc:resent-from:resent-sender: resent-message-id:in-reply-to:in-reply-to:references:references: list-id:list-help:list-unsubscribe:list-subscribe:list-post: dkim-signature; bh=/ADdIiAs0S5hHqbT5502fzrWuBG6l3+vL+ac5YDvlDM=; b=bUjBSDcA0DWz3H5UJtJZdEz/Pekqd5C8YrMQ42ehAKIpXFOZR7zzpK8ngc4e6GSZISCrb4 5aEc+zuU5qtFGdSMWn7jzoKeyKVK0lEweBljYd8zprCGX5istqEaWrYfl6ZVDSNavOgheY XDKdk6IWR3ImJMDhFi1SoaiI3XzS1VlKVU3RV0gmucm1t9TyBJzdzPdydF65DRY6kmd+4O ijZn1RiN7pyveBuyUN893orFQbnguqh/8j2mXPoIsiipCEUZPQta6o27GBPMyR8XNhtAWX sh9jUhEmYXAkG4lE35m3TgD1QHfNaq+39mNLbqugeO/1MKUjxs8HuRy2kLv1eQ== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qC5wn-0006Yt-Jk; Wed, 21 Jun 2023 18:05:05 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qC5wk-0006Yk-Sn for bug-guix@gnu.org; Wed, 21 Jun 2023 18:05:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qC5wk-000276-Ih for bug-guix@gnu.org; Wed, 21 Jun 2023 18:05:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qC5wj-000525-VI for bug-guix@gnu.org; Wed, 21 Jun 2023 18:05:01 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#64200: Netsurf very frequently freezes when editing text (Harfbuzz issue?) Resent-From: Csepp Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Wed, 21 Jun 2023 22:05:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64200 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: John Kehayias Cc: Josselin Poiret , Csepp , 64200@debbugs.gnu.org Received: via spool by 64200-submit@debbugs.gnu.org id=B64200.168738510119340 (code B ref 64200); Wed, 21 Jun 2023 22:05:01 +0000 Received: (at 64200) by debbugs.gnu.org; 21 Jun 2023 22:05:01 +0000 Received: from localhost ([127.0.0.1]:34331 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qC5wi-00051n-T6 for submit@debbugs.gnu.org; Wed, 21 Jun 2023 18:05:01 -0400 Received: from mx0.riseup.net ([198.252.153.6]:46978) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qC5wh-00051Y-1t for 64200@debbugs.gnu.org; Wed, 21 Jun 2023 18:04:59 -0400 Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4QmcxJ3Klzz9tMN; Wed, 21 Jun 2023 22:04:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1687385092; bh=Vp2aA0SA8n9r6NfgFsDNXx282Wrt6Y3rO3nZhmTyxn8=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=bkclkQHqpOuDJASc3LEVtnCft6VO7NjCn0CXpRcgQPApuVtfX/Libw167Mi1lnrjt Zlo2bC5mEoU0KsBEtrCVmxiuOmqJBaHq3Cr/XOk5fHpLrW6HC6x2As81l0Eszk8x7r yybIvkc2PGZr/cXJ/SDjPQ5tGJ8oIzusGGXP2S7s= X-Riseup-User-ID: F569B38D538B0D35369AA6452B1C8B18D13D62E4E7FED0FD542777C28531D54D Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4QmcxH3Zl1zFqgS; Wed, 21 Jun 2023 22:04:51 +0000 (UTC) References: <87a5wto7da.fsf@riseup.net> <87ilbh41xx.fsf@jpoiret.xyz> <87o7l8g9fg.fsf@protonmail.com> From: Csepp Date: Thu, 22 Jun 2023 00:00:32 +0200 In-reply-to: <87o7l8g9fg.fsf@protonmail.com> Message-ID: <87mt0smpz4.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: bug-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -0.75 X-Migadu-Queue-Id: 4C98F3BF4F X-Spam-Score: -0.75 X-TUID: Ltok/doITVMb John Kehayias writes: > Hi Josselin and Csepp, > > On Wed, Jun 21, 2023 at 11:08 AM, Josselin Poiret wrote: > >> Hi Csepp, >> >> Csepp 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. 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.