Created attachment 152924 [details] DrKonqi wouldn't allow me to automatically upload the bug so instead I downloaded the kcrash file and I have no idea how to upload it manually to bugs.kde.org so I'm adding it here. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open korganizer 2. I was adding a google calendar account to Korganizer and about a minute later my whole screen went to the tty screen I think (plasmashell crashed) and then it came back and the akondi crash reporter came up. I suspect it's because of the amount of events it was trying to load. OBSERVED RESULT crash EXPECTED RESULT not crash SOFTWARE/OS VERSIONS Application: akonadiserver (5.21.2 (22.08.2)) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.2-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 5.26.0 [KCrashBackend] ADDITIONAL INFORMATION
This is caused by kwin_wayland crashing. Please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to get a backtrace for kwin_wayland and post that here
(In reply to Nicolas Fella from comment #1) > This is caused by kwin_wayland crashing. > > Please follow > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > to get a backtrace for kwin_wayland and post that here #0 0x00007f2597faa464 in ?? () #1 0x00007f259815cd75 in ?? () #2 0x0000000017ea91c0 in ?? () #3 0x0000557a16b3c070 in ?? () #4 0x000000000000000b in ?? () #5 0x00007f2595d7d01c in ?? () #6 0x0000557a16a596c0 in ?? () #7 0x0000557a16b3c088 in ?? () #8 0x0000557a16ae1f50 in ?? () #9 0x000000017d4ef48b in ?? () #10 0x00619d6d177fcd60 in ?? () #11 0x00007f256001f670 in ?? () #12 0x0000557a1694cc00 in ?? () #13 0x0000000000000032 in ?? () #14 0x0000557a17d44330 in ?? () #15 0x00007f25983cacb0 in ?? () #16 0xbff0000000000000 in ?? () #17 0xcff2d23cd5edc700 in ?? () #18 0xbfdb477bfd84a2fb in ?? () #19 0x0000000000000008 in ?? () #20 0xffffffffffffffff in ?? () #21 0x00000001c8afb940 in ?? () #22 0x0000557a17d443a4 in ?? () #23 0x0000000000001000 in ?? () #24 0x0000000000000000 in ?? () Is this what you are looking for? I can replicate the crash again if you would like.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This is likely fixed with https://invent.kde.org/pim/akonadi/-/commit/1d9d64ec3cf78dfdddc2239df0d33b08dc442104