From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75209@debbugs.gnu.org, "N. Jackson" <njackson@posteo.net>
Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Tue, 31 Dec 2024 17:42:07 +0000 [thread overview]
Message-ID: <87ldvvhhqo.fsf@localhost> (raw)
In-Reply-To: <864j2lnf1j.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> I don't know how to reproduce this. The warning pops up seemingly
>> at random, often when the only visible window [before the *Warnings*
>> window appears] is NOT in Org mode.
>
> Ihor, any ideas or suggestions? Should this be reported to the Org
> list first?
Sounds like Emacs being killed by force in the middle of writing to that
file. Or, alternatively, C-g in the middle of writing.
If that's kill -9 or similar, I would not call this unexpected.
gc-lock.eld is a file used to flag that cache dir is being worked on by
multiple emacs instances. GC here refers to garbage-collecting cache data.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-12-31 17:42 UTC|newest]
Thread overview: 21+ 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 [this message]
[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-01 15:54 ` N. Jackson
2025-01-02 13:34 ` N. Jackson
2025-01-05 14:18 ` N. Jackson
2025-01-05 17:21 ` Eli Zaretskii
2025-01-06 0:58 ` N. Jackson
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=87ldvvhhqo.fsf@localhost \
--to=yantar92@posteo.net \
--cc=75209@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=njackson@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).