[Akonadi] [Bug 410935] akonadi _ews_ressource crashes when setting office365 account

Krzysztof Nowicki bugzilla_noreply at kde.org
Fri Aug 6 14:28:31 BST 2021


--- Comment #7 from Krzysztof Nowicki <krissn at op.pl> ---
The EWS resource keeps a copy of e-mail tags along with their metadata on the
Exchange server. This is done to enable synchronization of multiple Akonadi
instances connected to one Exchange mailbox.

This crash looks like for some reason the EWS resource is upset about this tag
metadata, that it reads from the server. The crash is actually inside Akonadi
itself, which is unable to read the tag metadata from the data stream.

This will be tricky to work around. The best option would be to erase the
server-side copy, but this would require some manual EWS request to be issued.

I would really like to understand why is Akonadi crashing here, whether it's
due to malformed tag metadata or due to some other problem.

To debug this, it is necessary to enable EWS request dumps. This can be done by
editing ~/.config/QtProject/qtlogging.ini and setting the
org.kde.pim.ews.client.proto.debug option to true:


With that enabled the problem can be reproduced by an attempt to set-up the
account again.

Once the crash happens, you should be able to fetch logs from the systemd
journal (I assume you're using systemd):

  journalctl --user -b0 /usr/bin/akonadi_ews_resource

In the log output please search for the "9bf757ae-69b5-4d8a-bf1d-2dd0c0871a28"
- the UUID used as the property set for Akonadi EWS. Around this UUID the log
should contain a bunch of XML text. Please attach it to the bug report. Please
note that it will expose all the tags you have in your KMail, so make sure
there is no company confidential stuff in there.

The content of the tag metadata should shed some light on why is Akonadi being
so upset trying to read it.

You are receiving this mail because:
You are the assignee for the bug.

More information about the Kdepim-bugs mailing list