Bug 449898 - "setFcc: collection invalid" after answering an e-mail
Summary: "setFcc: collection invalid" after answering an e-mail
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.19.2
Platform: Arch Linux Linux
: NOR critical
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-09 23:26 UTC by sedrubal
Modified: 2022-02-13 13:18 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sedrubal 2022-02-09 23:26:31 UTC
SUMMARY

kmail crashes when I click on a mail address in the body of an email. Unfortunately it seems, that some data gets corrupt during the crash and I am not able to start kmail again. I manually deleted some kmail / akonadi related files without success. But I could create a backup using PIM Data Exporter. After deleting everything I found in ~/.local/share and ~/.config/ and restored the backup, it worked again.

STEPS TO REPRODUCE
1. Open a mail with an email address in the message body
2. click on the email address

OBSERVED RESULT
kmail freezes / crashes. When I close it, it does not start again. Instead it is crashing with the message

EXPECTED RESULT
I want to write a new email to the address, I clicked on.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.24
KDE Frameworks Version: 5.90.0 
Qt Version: 5.15.2

ADDITIONAL INFORMATION

This is the log when I try to start kmail:
$ kmail
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
org.kde.pim.kmail: setFcc: collection invalid  ""
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
19 -- exe=/usr/bin/kmail
13 -- platform=xcb
11 -- display=:1
14 -- appname=kmail
17 -- apppath=/usr/bin
10 -- signal=11
11 -- pid=183353
28 -- appversion=5.19.2 (21.12.2)
18 -- programname=KMail
31 -- bugaddress=submit@bugs.kde.org
12 -- startupid=0
Comment 1 sedrubal 2022-02-09 23:32:03 UTC
The original crash is described in Bug 449891. This bug is about the corrupt data.
Comment 2 Hauke 2022-02-11 10:13:46 UTC
Can confirm this bug (also using Arch with KMail 5.19.2). But for me answering any mails (not only mail with an mail-adress in the message body) causes this crash.

Removing all files in ~./local/share/kmail2/autosave/ solved the startup issue and KMail starts normally. Answering a mail results in a crash again.

After the crash this autosave folder contains one file with the following (anonymized) content:

To: ??? ??? <???@???.de>
Date: ???
Message-ID: <1962715.oMNUckLgyt@???>
X-KMail-Identity: 1229347080
X-KMail-Transport: 435071032
X-KMail-Fcc: -7
X-KMail-Link-Message: 120072
X-KMail-Link-Type: reply
X-KMail-Identity-Name: ???@???
X-KMail-Transport-Name: ???
In-Reply-To: <a42558f3-b4f7-0b3a-e0db-e???@???.de>
References: <973d58b5-9acb-5694-14de-2???@???.de> <edf1af6b-c3ff-ae21-3395-5???@???.de> <a42558f3-b4f7-0b3a-e0db-e???@???.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"


The log output in the moment of the crash is the following:

*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
/tmp/messageviewer_oqpWBI.index.2 was not removed .
/tmp/messageviewer_oqpWBI.index.2 was removed .
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmail path = /usr/bin pid = 7740
KCrash: Arguments: /usr/bin/kmail 
[warn] epoll_wait: Ungültiger Dateideskriptor
[warn] epoll_wait: Ungültiger Dateideskriptor
[warn] epoll_wait: Ungültiger Dateideskriptor
[warn] epoll_wait: Ungültiger Dateideskriptor
..........


This epoll_wait warning is printed a thousand times. The string "Ungültiger Dateideskriptor" is German for "Bad file descriptor".
Comment 3 sedrubal 2022-02-11 11:10:45 UTC
(In reply to Hauke from comment #2)
> But for me answering any mails (not only mail with an mail-adress in the message body) causes this crash.

Can confirm, that this bug is caused by answering any mail.

> Removing all files in ~./local/share/kmail2/autosave/ solved the startup
> issue and KMail starts normally. Answering a mail results in a crash again.

Can confirm that, too. Thanks for the "fix".
Comment 4 demm 2022-02-12 16:28:04 UTC
Seems a duplicate of https://bugs.kde.org/show_bug.cgi?id=449826
Issue is with gpgme 1.17.0.
Comment 5 Hauke 2022-02-13 10:42:52 UTC
Fixed for me with KMail 21.12.2-2 (more details here: https://bugs.kde.org/show_bug.cgi?id=449872#c11).
Comment 6 sedrubal 2022-02-13 13:18:30 UTC
Yes, the update also fixes it for me. Thanks.