GNU bug report logs -
#75209
30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"
Previous Next
Full log
Message #62 received at 75209 <at> debbugs.gnu.org (full text, mbox):
> From: "N. Jackson" <njackson <at> posteo.net>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, Ihor Radchenko <yantar92 <at> posteo.net>
> Date: Sun, 05 Jan 2025 14:18:14 +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).
This timer is disabled. See bug#39824 for some related discussions,
in particular
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39824#53
This bug report was last modified 1 day ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.