Bug 514550 - Kontact sometimes crashes on first start, seemingly waiting on akonadi
Summary: Kontact sometimes crashes on first start, seemingly waiting on akonadi
Status: RESOLVED FIXED
Alias: None
Product: kontact
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2026-01-13 19:21 UTC by Christian (Fuchs)
Modified: 2026-01-13 23:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/334686/events/5a34b177943f4be18140872620e4da6e/


Attachments
New crash information added by DrKonqi (115.45 KB, text/plain)
2026-01-13 19:22 UTC, Christian (Fuchs)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian (Fuchs) 2026-01-13 19:21:59 UTC
Application: kontact (6.6.0 (25.12.0))

ApplicationNotResponding [ANR]: false
Qt Version: 6.10.1
Frameworks Version: 6.21.0
Operating System: Linux 6.18.3-200.fc43.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 43 (KDE Plasma Desktop Edition)"
DrKonqi: 6.5.4 [CoredumpBackend]

-- Information about the crash:
Unfortunately not 100% reproducible, but quite often: Sometimes on first start, kontact shows an empty window (no mails / other entries from akonadi), freeses a bit and then crashes.

This always happens on first start only, restarting afterwards always works.
I hope that the backtrace can lead to finding and fixing the root cause.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#4  QtWebEngineCore::ContentClientQt::SetGpuInfo () at /usr/src/debug/qt6-qtwebengine-6.10.1-2.fc43.x86_64/src/core/content_client_qt.cpp:528
#5  0x00007ff3b498a869 in content::GpuDataManagerImplPrivate::UpdateGpuInfo () at ../../../../../src/3rdparty/chromium/content/browser/gpu/gpu_data_manager_impl_private.cc:1051
#6  0x00007ff3b4982dbb in content::GpuDataManagerImpl::UpdateGpuInfo () at ../../../../../src/3rdparty/chromium/content/browser/gpu/gpu_data_manager_impl.cc:168
#7  0x00007ff3b499ae04 in content::GpuProcessHost::DidInitialize () at ../../../../../src/3rdparty/chromium/content/browser/gpu/gpu_process_host.cc:988
#8  0x00007ff3b7df9358 in viz::GpuHostImpl::DidInitialize () at ./../../../../../src/3rdparty/chromium/components/viz/host/gpu_host_impl.cc:498
#9  0x00007ff3b2c2fb54 in viz::mojom::GpuHostStubDispatch::Accept () at ./gen/services/viz/privileged/mojom/gl/gpu_host.mojom.cc:1297
#10 0x00007ff3b6cbce32 in mojo::InterfaceEndpointClient::HandleValidatedMessage () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:1052
#11 0x00007ff3b6cbe7be in mojo::MessageDispatcher::Accept () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/message_dispatcher.cc:43
#12 0x00007ff3b6cbcadc in mojo::InterfaceEndpointClient::HandleIncomingMessage () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:724
#13 0x00007ff3b6cc20e2 in mojo::internal::MultiplexRouter::ProcessIncomingMessage () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/multiplex_router.cc:1121
#14 0x00007ff3b6cc5952 in mojo::internal::MultiplexRouter::Accept () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/multiplex_router.cc:734
#15 0x00007ff3b6cbe7be in mojo::MessageDispatcher::Accept () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/message_dispatcher.cc:43
#16 0x00007ff3b6cb6311 in mojo::Connector::DispatchMessage () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:562
#17 0x00007ff3b6cb700c in mojo::Connector::ReadAllAvailableMessages () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:620
#18 0x00007ff3b6cb715e in mojo::Connector::OnHandleReadyInternal () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:452
#19 mojo::Connector::OnWatcherHandleReady () at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:418


Reported using DrKonqi
Comment 1 Christian (Fuchs) 2026-01-13 19:22:00 UTC
Created attachment 188485 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Albert Astals Cid 2026-01-13 21:40:20 UTC
Nothing to do with akonadi. This is a Qt bug, will be fixed in Qt 6.10.1 

You should ask your distribution to backport the patch

https://mail.kde.org/pipermail/distributions/2026-January/001666.html
Comment 3 Christian (Fuchs) 2026-01-13 21:50:45 UTC
(In reply to Albert Astals Cid from comment #2)
> Nothing to do with akonadi. This is a Qt bug, will be fixed in Qt 6.10.1 
> 
> You should ask your distribution to backport the patch
> 
> https://mail.kde.org/pipermail/distributions/2026-January/001666.html

Oh, fancy, thanks for the quick reply, I assume they will offer a version with the fix soon enough, else I shall go pester their bugzilla. 
Have a good one :)
Comment 4 Albert Astals Cid 2026-01-13 23:57:56 UTC
I actually meant it will be fixed in Qt 6.10.2 sorry about the mistake.