From ac51f7e6c40f385186ea90a64ef854d713863b43 Mon Sep 17 00:00:00 2001 From: Daniel Kraus Date: Tue, 17 Sep 2024 07:42:00 +0200 Subject: [PATCH] Fix console input and output. --- content/posts/2024/kmail-crash/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/posts/2024/kmail-crash/index.md b/content/posts/2024/kmail-crash/index.md index 471d2af..4bfeb57 100644 --- a/content/posts/2024/kmail-crash/index.md +++ b/content/posts/2024/kmail-crash/index.md @@ -15,7 +15,7 @@ Last night, I suddenly could not start KMail anymore. Konsole revealed this: ```fish -daniel@seppel9 ~ (main) [1]> kmail +$ kmail org.kde.pim.kmail: setFcc: collection invalid "" We have an error during reading password "Entry not found" *** KMail got signal 11 (Exiting) @@ -27,7 +27,7 @@ fish: Job 1, 'kmail' terminated by signal SIGSEGV (Address boundary error) Luckily, I quickly [found a fix][1]: ```fish -rm .local/share/kmail2/autosave/* +rm ~/.local/share/kmail2/autosave/* ``` Don't know what caused this problem and why KMail chokes on