From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "N. Jackson" 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 00:58:21 +0000 Message-ID: <871pxgbvwy.fsf@Phoenix> References: <878qrxgg74.fsf@Phoenix> <87v7uxibl9.fsf@Phoenix> <878qrpbazd.fsf@Phoenix> <86pll16ut7.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6252"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, 75209@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 06 01:59:25 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 1tUbSn-0001V9-A4 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Jan 2025 01:59:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tUbST-0005OK-UV; Sun, 05 Jan 2025 19:59:06 -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 1tUbSQ-0005OA-L6 for bug-gnu-emacs@gnu.org; Sun, 05 Jan 2025 19:59:04 -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 1tUbSQ-0003Xv-23 for bug-gnu-emacs@gnu.org; Sun, 05 Jan 2025 19:59:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-Version:Date:References:In-Reply-To:From:To:Subject; bh=keuivuz0aMvtz8ha7u7Y/wU8WrYjgS+RLO+s28xgls0=; b=dD1WX6oP3jcojEte0AIB7oAPfotu5mn26u9nEFU318J/9geapRFHg/2iWl5F7/pqbD7PY4QWPy4kbNnTT3/7bvRauB0nYsM5h9qz9z93geq7tRtgvUImWd6lD+R7YewtQ0maHE2N6GrLUD3dozQh7UMW7bI858JeKbWuFasYecF266fm0L/37v4M8tk7dnqo7bstCFnF5EwbRPSEjffc/dUyZBJQPzNWpnqwZcoWp8zCAkz4c1jwSzHEC6tFXkrHeG5DDMAvyoP96LG4iW45712wmvtZFA6EeDqVJXvCbDoYPjFvTn5+hU+pc/DEldSOCFjJQAhEj1svtXVbOExR5g==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tUbSP-0007wR-Ow for bug-gnu-emacs@gnu.org; Sun, 05 Jan 2025 19:59:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: "N. Jackson" Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Jan 2025 00:59:01 +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.173612511530485 (code B ref 75209); Mon, 06 Jan 2025 00:59:01 +0000 Original-Received: (at 75209) by debbugs.gnu.org; 6 Jan 2025 00:58:35 +0000 Original-Received: from localhost ([127.0.0.1]:36002 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tUbRy-0007vd-QO for submit@debbugs.gnu.org; Sun, 05 Jan 2025 19:58:35 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]:48961) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tUbRu-0007vK-I6 for 75209@debbugs.gnu.org; Sun, 05 Jan 2025 19:58:32 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id E5837240101 for <75209@debbugs.gnu.org>; Mon, 6 Jan 2025 01:58:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1736125103; bh=pLJa6+4O8pvChBralfIxLvQ/7CXtLQZa6imnFBrf15k=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=Qhb9CQDhxNxHA++8ygDDXngs3brL2J5ReQ87qMA/9ZOGMJ+6NM34fUWcFS595ps64 c4lIEy37v+aM5sCs1YJ03mAfq6VGVOqgK+f4pSH6S7R6EqPR0CKXGQRjD+sNKb2y9R ybVXqxtfz0DN7tLdJ3ZpzRnAFM3bHjWK4tUqAA7bOJ0zqzVhbl6V+mwBHHi9A38MQP GjSFmH2Rla6m4BKuyh8stwxrz0kFOXNIDM39AgTx7wz7HsmkQj9mJk4KYBzm+J7AkW W8wOQ/6tgdT3tY1PBiR4EzLpqYqUWOIxm5Rp5brZ2c9eSB2mVVu1CBYwofQD7VLYd8 +c+lw49RGz5Iw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YRG5B3JKDz6tvc; Mon, 6 Jan 2025 01:58:22 +0100 (CET) In-Reply-To: <86pll16ut7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 05 Jan 2025 19:21:08 +0200") 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:298623 Archived-At: At 19:21 +0200 on Sunday 2025-01-05, Eli Zaretskii wrote: >> From: "N. Jackson" >> >> Running list-timers shows: >> >> Idle Next Repeat Function >> -1d 15h 43m 30.2s 1h org-persist--refresh-gc-lock > > This timer is disabled. See bug#39824 for some related discussions, > in particular > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39824#53 I have now read that bug report and I admit I don't fully understand it[1]. IIUC, the user's timer had encountered an error, a backtrace had been produced, and the user had said `q' to the debugger, leaving the timer in a broken state. Here, like in that bug report, the broken timer has `t' in the first element: [t 26490 7240 117604 3600 org-persist--refresh-gc-lock nil nil 17000 nil] However, I have seen no error. (If I were presented with a backtrace, I would almost certainly make a copy of the buffer and then hit `c' rather than `q', but in fact I haven't seen a backtrace in a long time. Indeed, debug-on-error is nil. I have seen no error messages in this run of Emacs and there are no errors (or anything else unexpected in Messages).) 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. (One other observation: IIUC, it says in bug#39824 that the broken timer moves farther into the past, but here my broken timer is counting forward (it is now due in negative 1 day and 5 hours) so presumably in a day or so it will no longer be negative. Will it then start running again I wonder? If this behaviour is expected, perhaps it should be mentioned in the documentation. It seems a bit peculiar to me.) [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. (But maybe it was well understood and the mechanism was too trivial to record.) [And I don't think, just because a timer fails once, that one necessarily wants that timer disabled (because the problem might be transient). Also it seems to me that if a timer is going to be disabled then that should be done explicitly rather than as a side-effect of an abort.] But that is all irrelevant here.