Application: kmail (6.4.0 (25.04.0)) ApplicationNotResponding [ANR]: false Qt Version: 6.9.0 Frameworks Version: 6.13.0 Operating System: Linux 6.11.0-25-generic x86_64 Windowing System: Wayland Distribution: KDE neon 6.3 DrKonqi: 6.3.4 [CoredumpBackend] -- Information about the crash: What happened the last time before KMail started crashing on startup: - When I wanted to send a Mail, KMail warned me that the sent-mail folder was invalid, so I opened the configuration dialog - every sent-mail / drafts / templates folder was shown red in the configuration dialog (despite the text within the textboxes looking right). * -> more below - I changed the sent-mail folder for that account to use the non-local IMAP folder, then sent the mail - closed the window, KMail seemed to continue normally in the background - the next time (and every time since that) I tried to start KMail it crashed * I've seen this behaviour before in bug #502121. Differences to that bug: - In #502121 I got a message - then KMail quit. This time it just crashes. - there is only the akonadi_maildir_resource_0/ in ~/.local/share. - I did not notice Mails missing from sent-mail folders - but I had not looked that day, so that might still have been the case. - The workaround I used there does not work this time. Additional Info: I still get new mail notifications. The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x000079c8c95133dd in viz::CompositorFrameSinkSupport::StopObservingBeginFrameSource () at ./../../../../../src/3rdparty/chromium/components/viz/service/frame_sinks/compositor_frame_sink_support.cc:1324 #7 viz::CompositorFrameSinkSupport::UpdateNeedsBeginFramesInternal () at ./../../../../../src/3rdparty/chromium/components/viz/service/frame_sinks/compositor_frame_sink_support.cc:1313 #8 0x000079c8c951da9d in viz::CompositorFrameSinkSupport::SetNeedsBeginFrame () at ./../../../../../src/3rdparty/chromium/components/viz/service/frame_sinks/compositor_frame_sink_support.cc:583 #9 viz::CompositorFrameSinkSupport::~CompositorFrameSinkSupport () at ./../../../../../src/3rdparty/chromium/components/viz/service/frame_sinks/compositor_frame_sink_support.cc:145 #10 0x000079c8c951e0b5 in viz::CompositorFrameSinkSupport::~CompositorFrameSinkSupport () at ./../../../../../src/3rdparty/chromium/components/viz/service/frame_sinks/compositor_frame_sink_support.cc:188 Reported using DrKonqi
Created attachment 181103 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Now this is interresting.... After reporting this, I started akonadiconsole to check my mails there... And it crashed! The end of the backtrace looks exactly like the one from this crash - I'll attach it here.
Created attachment 181104 [details] Crash of akonadiconsole
small update: now that kwalletd broke and syncing mails is no longer possible, kmail and akonadiconsole start again. I wonder what will happen when that is fixed...
another small update: kf6-kwallet update to 6.14.0-0zneon+24.04+noble+release+build32 didn't fix kwallet, but makes kmail crash again.
Another update... meanwhile kmail had worked for a few days - then started crashing again. After some research today, I found this bug report for qtwebengine: https://bugreports.qt.io/browse/QTBUG-136122 Based on that report, I looked into how to disable my iGPU (normally I do this immediately, but my new mainboard has something like > 200 options, so I was not able to find it on the first setup). This finally fixed the issue for me. The Qt-bugreport indicates that the issue has been fixed in 6.9.1 - I'll close this after neon upgrades to Qt 6.9.1.
As far as I understand now this was a bug in QtWebengine, which is marked as fixed in 6.9.1. If someone needs a workaround for an older version: disable the iGPU in BIOS. (cause: QtWebengine might try to render on wrong GPU).