From 4ff291d3aaf687464b59938daa39cd08f7a5e0d3 Mon Sep 17 00:00:00 2001 From: Daniel Kraus Date: Tue, 17 Sep 2024 07:09:17 +0200 Subject: [PATCH] Add blog post about Kmail crash. --- content/posts/2024/kmail-crash/index.md | 36 +++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 content/posts/2024/kmail-crash/index.md diff --git a/content/posts/2024/kmail-crash/index.md b/content/posts/2024/kmail-crash/index.md new file mode 100644 index 0000000..471d2af --- /dev/null +++ b/content/posts/2024/kmail-crash/index.md @@ -0,0 +1,36 @@ +--- +title: How to fix KMail not starting +description: How I got my KMail working again when it crashed during the startup process +date: 2024-09-17T06:00:00+0200 +draft: false +ShowLastmod: false +tags: + - Plasma + - Fix + - KMail +--- + +Last night, I suddenly could not start KMail anymore. + +Konsole revealed this: + +```fish +daniel@seppel9 ~ (main) [1]> kmail +org.kde.pim.kmail: setFcc: collection invalid "" +We have an error during reading password "Entry not found" +*** KMail got signal 11 (Exiting) +*** Dead letters dumped. +KCrash: Application 'kmail' crashing... crashRecursionCounter = 2 +fish: Job 1, 'kmail' terminated by signal SIGSEGV (Address boundary error) +```` + +Luckily, I quickly [found a fix][1]: + +```fish +rm .local/share/kmail2/autosave/* +``` + +Don't know what caused this problem and why KMail chokes on +autosave files, but at least I can now start it again. + +[1]: