From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43943@debbugs.gnu.org
Subject: bug#43943: >=27.1; segfault with package-list-packages and others
Date: Mon, 12 Oct 2020 18:32:11 +0200 [thread overview]
Message-ID: <87imbf1k38.fsf@web.de> (raw)
In-Reply-To: <83v9ff32x1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
> tags 43943 unreproducible
> thanks
>> From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
>> Date: Mon, 12 Oct 2020 10:39:18 +0200
>>
>> Update: Deleting ~/path/to/workspace/.cache fixed the crash. Sadly I did
>> not keep a backup :-(
>>
>> Folders in my .cache (from bash history) were:
>> chromium/ dconf/ fontconfig/ guile/ mozilla/ mu/ node-gyp/ pip/
>
> My guess is that it was the fontconfig cache.
Can something be done to prevent a segfault in this case? I had no clue
how to fix this and stumbled around which could have cost quite a lot of
time, because org-agenda is crucial to my daily work.
… upon realizing this I just decided to join the donors for org mode. I
really do need it to be able to work, and I earn more money when using
it than I would without it (I know how it ends when I don’t track my
work in org mode) so I should pay for it.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2020-10-12 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 6:04 bug#43943: 27.1; segfault with package-list-packages and others Dr. Arne Babenhauserheide
2020-10-12 8:39 ` bug#43943: >=27.1; " Dr. Arne Babenhauserheide
2020-10-12 15:00 ` Eli Zaretskii
2020-10-12 16:32 ` Dr. Arne Babenhauserheide [this message]
2020-10-12 17:24 ` Eli Zaretskii
2020-10-12 17:33 ` Robert Pluim
2020-10-12 18:43 ` Dr. Arne Babenhauserheide
2020-10-12 18:46 ` Dr. Arne Babenhauserheide
2020-10-12 18:48 ` Dr. Arne Babenhauserheide
2020-10-12 19:10 ` Eli Zaretskii
2020-10-12 19:28 ` Dr. Arne Babenhauserheide
2020-11-16 3:19 ` Stefan Kangas
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=87imbf1k38.fsf@web.de \
--to=arne_bab@web.de \
--cc=43943@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).