From: "N. Jackson" <njackson@posteo.net>
To: 75209@debbugs.gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, Ihor Radchenko <yantar92@posteo.net>
Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Sun, 05 Jan 2025 14:18:14 +0000 [thread overview]
Message-ID: <878qrpbazd.fsf@Phoenix> (raw)
In-Reply-To: <87v7uxibl9.fsf@Phoenix> (N. Jackson's message of "Thu, 02 Jan 2025 13:34:10 +0000")
The following might be "normal", in which case I apologise for the
noise, but it seems odd to me and it might have some bearing on the
bug.
Running list-timers shows:
Idle Next Repeat Function
-1d 15h 43m 30.2s 1h org-persist--refresh-gc-lock
2.4s 1m battery-update-handler
2.4s 5m savehist-autosave
4.2s - undo-auto--boundary-timer
50.1s 1m display-time-event-handler
* 0.1s t show-paren-function
* 0.5s t #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_9>
* 0.5s :repeat blink-cursor-start
* 30.0s - desktop-auto-save
I see nothing in the manuals about what it means for a
relative timer to be negative. (Or is org-persist--refresh-gc-lock
running on a timer set with an absolute time that list-timers is
merely displaying as a relative time?) And it seems odd that this
time is before this Emacs session started (emacs-uptime shows 1 day,
1 hour, 16 minutes, 40 seconds).
next prev parent reply other threads:[~2025-01-05 14:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 18:48 bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" N. Jackson
2024-12-30 19:31 ` Eli Zaretskii
[not found] ` <87zfkddk1l.fsf@Phoenix>
2024-12-30 20:01 ` Eli Zaretskii
2025-01-01 17:41 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-01 18:52 ` Eli Zaretskii
2025-01-01 21:09 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-31 17:42 ` Ihor Radchenko
[not found] ` <87frm3elkr.fsf@Phoenix>
2024-12-31 19:02 ` Ihor Radchenko
2024-12-31 19:54 ` Eli Zaretskii
2025-01-01 9:42 ` Ihor Radchenko
2025-01-01 12:14 ` Eli Zaretskii
2025-01-02 17:28 ` Ihor Radchenko
2025-01-02 18:48 ` Eli Zaretskii
2025-01-05 10:03 ` Ihor Radchenko
2025-01-05 11:15 ` Eli Zaretskii
2025-01-05 13:18 ` Ihor Radchenko
2025-01-11 14:05 ` Ihor Radchenko
2025-01-11 14:34 ` Eli Zaretskii
2025-01-13 15:36 ` N. Jackson
2025-01-13 17:27 ` Ihor Radchenko
2025-01-01 15:54 ` N. Jackson
2025-01-11 15:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 13:34 ` N. Jackson
2025-01-05 14:18 ` N. Jackson [this message]
2025-01-05 17:21 ` Eli Zaretskii
2025-01-06 0:58 ` N. Jackson
2025-01-06 13:49 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878qrpbazd.fsf@Phoenix \
--to=njackson@posteo.net \
--cc=75209@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yantar92@posteo.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/emacs.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).