Bug 502578 - Kontact crash on startup
Summary: Kontact crash on startup
Status: REPORTED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
: 502684 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-04-08 19:48 UTC by Jan Kohnert
Modified: 2025-04-15 11:03 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/160186/events/3b7f437d0a09477bb204dca1a631df25/


Attachments
New crash information added by DrKonqi (189.55 KB, text/plain)
2025-04-08 19:48 UTC, Jan Kohnert
Details
KMail crash report (141.90 KB, text/vnd.kde.kcrash-report)
2025-04-12 07:05 UTC, Felix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kohnert 2025-04-08 19:48:51 UTC
Application: kontact (6.3.3 (24.12.3))

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.12.0
Operating System: Linux 6.13.8-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.3.4 [CoredumpBackend]

-- Information about the crash:
Kontact crashes immediately after start-up with message:
jankoh@kohni-mobil ~ $ kontact 
kf.windowsystem: KWindowInfo is only functional when running on X11
qt.svg.draw: The requested buffer size is too big, ignoring
[5530:5572:0408/213023.980307:ERROR:angle_platform_impl.cc(44)] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
[5530:5572:0408/213023.980320:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_SUCCESS
[5530:5572:0408/213023.980325:ERROR:native_pixmap_egl_binding.cc(118)] Unable to initialize binding from pixmap
[5530:5572:0408/213023.980337:ERROR:ozone_image_backing.cc(309)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[5530:5572:0408/213023.980340:ERROR:shared_image_manager.cc(255)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[5530:5572:0408/213023.980342:ERROR:native_skia_output_device.cpp(261)] ProduceSkia() failed.
[5530:5572:0408/213023.980414:ERROR:raster_decoder.cc(1146)]   RasterDecoderImpl: Context lost during MakeCurrent.
[5530:5572:0408/213023.980456:ERROR:raster_decoder.cc(1146)]   RasterDecoderImpl: Context lost during MakeCurrent.
[5530:5572:0408/213023.980528:ERROR:raster_decoder.cc(1146)]   RasterDecoderImpl: Context lost during MakeCurrent.
[5530:5572:0408/213023.980551:ERROR:raster_decoder.cc(1146)]   RasterDecoderImpl: Context lost during MakeCurrent.
[5530:5572:0408/213023.994913:ERROR:shared_context_state.cc(885)] Failed to make current since context is marked as lost
[5530:5572:0408/213023.994926:ERROR:skia_output_surface_impl_on_gpu.cc(2264)] Failed to make current.
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
KCrash: Application 'kontact' crashing... crashRecursionCounter = 2
Speicherzugriffsfehler (Speicherabzug geschrieben)
jankoh@kohni-mobil ~ $

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x000076d82b49162e in viz::CompositorFrameSinkSupport::~CompositorFrameSinkSupport () at ./../../../../../qtwebengine/src/3rdparty/chromium/components/viz/service/frame_sinks/compositor_frame_sink_support.cc:181
#6  0x000076d82b4919fc in viz::CompositorFrameSinkSupport::~CompositorFrameSinkSupport () at ./../../../../../qtwebengine/src/3rdparty/chromium/components/viz/service/frame_sinks/compositor_frame_sink_support.cc:188
#7  std::default_delete<viz::CompositorFrameSinkSupport>::operator() () at /usr/include/c++/14.2.1/bits/unique_ptr.h:93
#8  std::unique_ptr<viz::CompositorFrameSinkSupport, std::default_delete<viz::CompositorFrameSinkSupport> >::~unique_ptr () at /usr/include/c++/14.2.1/bits/unique_ptr.h:399
#9  viz::RootCompositorFrameSinkImpl::~RootCompositorFrameSinkImpl () at ./../../../../../qtwebengine/src/3rdparty/chromium/components/viz/service/frame_sinks/root_compositor_frame_sink_impl.cc:292


Reported using DrKonqi
Comment 1 Jan Kohnert 2025-04-08 19:48:52 UTC
Created attachment 180096 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Felix 2025-04-09 06:03:38 UTC
This happens when starting KMail, too.
Comment 3 Tobias Leupold 2025-04-09 17:00:15 UTC
I see a similar problem when starting KMail, using Artix Linux. Interestingly, KMail crashes with an X11 session, but not using a Wayland session. I suppose this is some QtWebEngine 6.9.0 issue, as KMail does start for a split second and then crashes. I posted the problem on the Artix forums at https://forum.artixlinux.org/index.php/topic,8014.msg47937.html

Starting KMail from a console, I get this (only on X11):

$ LC_ALL=C.UTF-8 kmail
org.kde.pim.messagelist: Saved theme loading failed
org.kde.pim.messagelist: Saved theme loading failed
org.kde.pim.messagelist: Saved theme loading failed
[5921:5921:0409/180927.657594:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[5921:5921:0409/180927.657610:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: No such file or directory (2)
[...]
[5921:5962:0409/180927.961877:ERROR:gpu_memory_buffer_support_x11.cc(134)] Can't create buffer -- unsupported config: usage=SCANOUT, format=BGRA_8888
Failed to create GBM buffer for GLX.
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
KCrash: Application 'kmail' crashing... crashRecursionCounter = 2
Abgebrochen

Maybe this helps?
Comment 4 Antonio Rojas 2025-04-11 16:16:13 UTC
*** Bug 502684 has been marked as a duplicate of this bug. ***
Comment 5 Felix 2025-04-12 07:05:33 UTC
Created attachment 180189 [details]
KMail crash report
Comment 6 auxsvr 2025-04-14 20:24:38 UTC
On latest opensuse tumbleweed, Kontact crashes on Wayland with the stacktrace above. If I use QT_QPA_PLATFORM=xcb, it starts, but the message viewer in kmail and akregator (everything using qtwebengine) is corrupted.
Comment 7 Jan Kohnert 2025-04-14 21:02:22 UTC
(In reply to auxsvr from comment #6)
> On latest opensuse tumbleweed, Kontact crashes on Wayland with the
> stacktrace above. If I use QT_QPA_PLATFORM=xcb, it starts, but the message
> viewer in kmail and akregator (everything using qtwebengine) is corrupted.

I can confirm setting mentioned env variable fixes the crash. At first glance, it seems Kontact is working fine on Arch when started with it, I don't see a corrupted message or akregator viewer.

 Best, Jan
Comment 8 Jan Kohnert 2025-04-14 21:12:29 UTC
(In reply to Jan Kohnert from comment #7)
> (In reply to auxsvr from comment #6)
> > On latest opensuse tumbleweed, Kontact crashes on Wayland with the
> > stacktrace above. If I use QT_QPA_PLATFORM=xcb, it starts, but the message
> > viewer in kmail and akregator (everything using qtwebengine) is corrupted.
> 
> I can confirm setting mentioned env variable fixes the crash. At first
> glance, it seems Kontact is working fine on Arch when started with it, I
> don't see a corrupted message or akregator viewer.
> 
>  Best, Jan

But, quitting leads to
kf.xmlgui: 0x78e9e0013630 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x78e9e0017858 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x6231c00c7e40 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x6231c0131b08 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x6231c042c918 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x6231c043cb08 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x6231c036e818 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x78e9e0010b58 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
kf.xmlgui: 0x6231c04cef38 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
corrupted size vs. prev_size while consolidating
*** KMail got signal 6 (Exiting)
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
Speicherzugriffsfehler (Speicherabzug geschrieben)
jankoh@kohni-mobil ~ $ 
which is probably unrelated, though...
Comment 9 the 2025-04-15 10:17:06 UTC
(In reply to Jan Kohnert from comment #7)
> (In reply to auxsvr from comment #6)
I tried the above mentioned environment variable and still have graphical artifacts in the message preview window.

To be specific, I only experienced the crash at start up with a fresh install of cachy os / arch, on my existing installation of cachy os / arch I only have the artifacts.

> > On latest opensuse tumbleweed, Kontact crashes on Wayland with the
> > stacktrace above. If I use QT_QPA_PLATFORM=xcb, it starts, but the message
> > viewer in kmail and akregator (everything using qtwebengine) is corrupted.
> 
> I can confirm setting mentioned env variable fixes the crash. At first
> glance, it seems Kontact is working fine on Arch when started with it, I
> don't see a corrupted message or akregator viewer.
> 
>  Best, Jan
Comment 10 the 2025-04-15 11:03:19 UTC
Just tried the environment variable QT_QPA_PLATFORM=xcb on my fresh installed cachy os system and Kmail still crashes on start up. May we have two different errors?