Bug 492817 - Akonadi EWS resource nonreliability and crash after authentication issues
Summary: Akonadi EWS resource nonreliability and crash after authentication issues
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: EWS Resource (show other bugs)
Version: 6.1.2
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-08 14:03 UTC by Erik Quaeghebeur
Modified: 2024-09-11 07:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Excerpt from system log including backtrace for crash (67.83 KB, text/plain)
2024-09-08 14:03 UTC, Erik Quaeghebeur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Quaeghebeur 2024-09-08 14:03:32 UTC
Created attachment 173444 [details]
Excerpt from system log including backtrace for crash

SUMMARY
I recently updated from KDE5 to KDE6. The EWS resource for 5 wasn't all too stable, but for 6 it has become dramatically bad. Effectively, the resource becomes disabled very soon after restarting and I need to manually restart it in akonadiconsole to fetch my mail (and then later I find it deactivated again).

I do not know whether there is a crash associated to this deactivation or not, also because DrKonqi seems to not work any more for me on KDE6. In any case, in my logs I found a backtrace for the EWS resource, which I'm attaching here, with some context.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.6.47-gentoo-a (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 49.7 GB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION
I can install more debug symbol packages, if needed. Tell me which, as I don't have DrKonqi's input about this.
Comment 1 Erik Quaeghebeur 2024-09-11 07:49:31 UTC
By looking at my logs right after restarting the agent, I now am quite confident that the crash happens when restarting the agent and is reproducible. (I typically have to restart the agent twice, as the first time is not successful.)