[Akonadi] [Bug 500047] New: Crash occured after trying to clear the synchronisation state of Microsoft 365 account in KOrganizer

[Torsten Maehne]

https://bugs.kde.org/show_bug.cgi?id=500047

            Bug ID: 500047
           Summary: Crash occured after trying to clear the
                    synchronisation state of Microsoft 365 account in
                    KOrganizer
    Classification: Frameworks and Libraries
           Product: Akonadi
           Version: unspecified
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: EWS Resource
          Assignee: kdepim-bugs at kde.org
          Reporter: Torsten.Maehne at gmx.de
                CC: carl at carlschwan.eu, krissn at op.pl
  Target Milestone: ---

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

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