From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" Date: Mon, 06 Jan 2025 15:49:37 +0200 Message-ID: <86r05g59xq.fsf@gnu.org> References: <878qrxgg74.fsf@Phoenix> <87v7uxibl9.fsf@Phoenix> <878qrpbazd.fsf@Phoenix> <86pll16ut7.fsf@gnu.org> <871pxgbvwy.fsf@Phoenix> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12267"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, 75209@debbugs.gnu.org To: "N. Jackson" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 06 14:50:29 2025 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tUnUy-00030T-VG for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Jan 2025 14:50:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tUnUh-0007n2-SY; Mon, 06 Jan 2025 08:50:12 -0500 Original-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 1tUnUa-0007iL-Dw for bug-gnu-emacs@gnu.org; Mon, 06 Jan 2025 08:50:05 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tUnUZ-00032z-Q3 for bug-gnu-emacs@gnu.org; Mon, 06 Jan 2025 08:50:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=A2yPEpUl54a4ZisB/ZE2f3ikkBwWZ+umnZUVrnnRUkc=; b=NKLDcpPKkVFo32as6LV8/YFZzqvRYf/pUYRn7Wnp0Il6jKRgfv6InTqIkGZgWOuGHaQBCKrQ6ItwDuPZZSa/gGZr+fxoBdwOM438B6xiq6MAOy+aTNtqEswzECGWucpd6q6D+0kX9Itvn8RVE7IELzYCK1kORJG/SCHlrcZPgr0eCGXLMTl/agYvNCh214cIiaZj5ZCHM8AflNe/XD2GUA4Tw3JpNC+xJ1ucU1AtEoZvSTvHICxXFFnvEHa+RHyjUfykXMSFc27v88Zg3j46YPOrOlTbT4SHC17RqFjIbTIlVnMIamsIkhj/ICZ8kzk9wr9lh+BVgFIdr5d8eLl2Vw==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tUnUY-0005BT-Jx for bug-gnu-emacs@gnu.org; Mon, 06 Jan 2025 08:50:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Jan 2025 13:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 75209 X-GNU-PR-Package: emacs Original-Received: via spool by 75209-submit@debbugs.gnu.org id=B75209.173617139219900 (code B ref 75209); Mon, 06 Jan 2025 13:50:02 +0000 Original-Received: (at 75209) by debbugs.gnu.org; 6 Jan 2025 13:49:52 +0000 Original-Received: from localhost ([127.0.0.1]:37339 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tUnUN-0005Au-Hx for submit@debbugs.gnu.org; Mon, 06 Jan 2025 08:49:51 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35330) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tUnUJ-0005Ac-OO for 75209@debbugs.gnu.org; Mon, 06 Jan 2025 08:49:49 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tUnUE-0002zq-Bu; Mon, 06 Jan 2025 08:49:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=A2yPEpUl54a4ZisB/ZE2f3ikkBwWZ+umnZUVrnnRUkc=; b=DZl+zwwg5X9w +EfapyvDruVuuh0tUnYcX0G/PDuAnezuULLr4IscPviK5tnqCWa0FxW713/oXAx78CWPm42ry1uZn CtCsm/b/UKzGqYT1vStYrXFL4qv14JC1bTBtmpuWiB6/cuE9r5GnQruHGro0fnSWXG+qqUnKLlZR0 o6IwOoRTuabTn7VDlNL4wV1xKiOwFQ1YembT0cd4Adx+II0PiHFIEgcXPbqXemiRDygGuRUTBF37A cZzm8oTnYZzcJP5q213hZEVS5uvMFNHRmqGkssP3CWDxW2FmGGU5XIUTm02slGOupdxPiz+TdUpRy SUW83NY2cMQ2fXyOkpg6gA==; In-Reply-To: <871pxgbvwy.fsf@Phoenix> (njackson@posteo.net) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298655 Archived-At: > From: "N. Jackson" > Cc: 75209@debbugs.gnu.org, yantar92@posteo.net > Date: Mon, 06 Jan 2025 00:58:21 +0000 > > I'm guessing (wildly) that what happened is this: > > 1. I woke my system from suspend. > > 2. All timers in both my instances of Emacs ran roughly > simultaneously. > > 3. Org Mode's locking mechanisms are not working properly when two > copies of org-persist--refresh-gc-lock run at essentially the > same time, and it failed in one instance of Emacs. > > 4. Org Mode (or something else) caught the failure and reported > > Warning (emacs): Emacs reader failed to read data in > "/home/nlj/.cache/org-persist/gc-lock.eld". The error was: > "End of file during parsing" > > and the running of the timer was aborted, leaving it in a broken > state. > > I think this wild conjecture would explain why sometimes (but by no > means always) I see this warning when I resume from suspend; why I > rarely see the warning at other times; and why sometimes I see the > warning in my regular Emacs session and sometimes in the instance in > which I'm running Gnus. I think you are right. I think the mechanisms involved in this scenario should be audited to find possible problems and solutions. For example, if the timer function could signal an error, it should catch the error and handle it instead of leading to the timer being disabled. > [1] I don't understand why bug#39824 was closed as Not A Bug when > the mystery of how the timers got in an incoherent state wasn't > fully clarified. Because the data for investigating it was not available.