Bug 500047 - Crash occured after trying to clear the synchronisation state of Microsoft 365 account in KOrganizer
Summary: Crash occured after trying to clear the synchronisation state of Microsoft 36...
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: EWS Resource (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-02-14 08:51 UTC by Torsten Maehne
Modified: 2025-02-14 08:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/132928/events/00b9f06e48fa4db8b0e47551c5071924/


Attachments
New crash information added by DrKonqi (150.19 KB, text/plain)
2025-02-14 08:51 UTC, Torsten Maehne
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Torsten Maehne 2025-02-14 08:51:17 UTC
Application: akonadi_ews_resource (6.3.2 (24.12.2))

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.10.0
Operating System: Linux 6.13.2-arch1-1 x86_64
Windowing System: Wayland
Distribution: EndeavourOS
DrKonqi: 6.3.0 [CoredumpBackend]

-- Information about the crash:
After upgrading KDE Plasma to 6.3.0 from the Arch Linux repositories, I faced a very long black screen after login to my account via SDDM. Just a blinking console cursor was shown - no graphical elements. The system didn't react to any keyboard/mouse input. After several minutes, the desktop slowly appeared with a spinning notification of the akonadi_migration_agent. It does not seem to progress/finish even now after almost 20 min running. When I opened KOrganizer, I noticed that the calendar of my university's Microsoft 365 account was not fully synchronized. To resolve the issue, I tried clearing the synchronisation state (folder tree state and folder item state) via the advanced tab in the Microsoft Exchange Configuration dialog. After hitting OK, the crash was reported.

I have faced the black screen behavior after SDDM login now several times when KDE Plasma were updated with pacman to a new release. The unresponsiveness and lack of any status message for more than a minute is irritating and triggers people to force a reboot. The ACPI signals generated by the power button seem to at least trigger a clean shutdown. However, I observed at several occasions, that even the shutdown got stuck.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  std::__atomic_base<int>::fetch_add (this=0x0, __i=1, __m=std::memory_order::acq_rel) at /usr/include/qt6/QtCore/qbasicatomic.h:47
#6  QAtomicOps<int>::ref<int> (_q_value=<error reading variable: Cannot access memory at address 0x0>) at /usr/include/qt6/QtCore/qatomic_cxx11.h:259
[...]
#10 QArrayDataPointer<char16_t>::QArrayDataPointer (this=0x7fff6a15c390, other=..., this=<optimized out>, other=<optimized out>) at /usr/include/qt6/QtCore/qarraydatapointer.h:40
#11 0x0000629132f19b33 in QString::QString (this=0x7fff6a15c390, other=..., this=<optimized out>, other=<optimized out>) at /usr/include/qt6/QtCore/qstring.h:1261
#13 operator<< (debug=..., version=...) at /usr/src/debug/kdepim-runtime/kdepim-runtime-24.12.2/resources/ews/ewsclient/ewsserverversion.cpp:130


Reported using DrKonqi
Comment 1 Torsten Maehne 2025-02-14 08:51:18 UTC
Created attachment 178347 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.