| Summary: | Kontact fails to start properly on wayland | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Geert Janssens <info> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 6.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Geert Janssens
2025-11-17 18:22:03 UTC
Further investigation shows the issue happens in kmail2, not kontact. I have also found the issue is not wayland specific. kmail2 also crashes under X11 After a recent update of my system I'm now running kmail2 6.5.3 (25.08.3). I have searched a bit further on the web and I can use kmail2 if I start it as follows: $ QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" kmail If started like that, kmail works fine (at least under X11). I'll note this line missing from the console output now: "GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium." Clearly something is wrong when falling back to Vulkan rendering. I just tried again under Plasma Wayland. The workaround for kmail also works there, but kontact is still not running. With the workaround the console output is shorter, but kontact continues to not work as described in the original message: it appears in the task bar, but its window never materializes. When run as: $ QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" kontact The output on console becomes org.kde.pim.pimcommonactivities: Plasma activities is not running: 1 qt.svg.draw: The requested buffer size is too big, ignoring qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x557a24573760 qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x557a24573760 org.kde.pim.mailtransport: We have an error during reading password for 1396373894 "Entry not found" So the eglSwapBuffers error remains when starting kontact. I'm changing this bug back to contact and report my kmail specific findings (with workaround) in a separate bug. |