| Summary: | Kontact crash on startup | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Jan Kohnert <bughunter> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | auxsvr, felix, metzpinguin, the, tl |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| 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
KMail crash report |
||
|
Description
Jan Kohnert
2025-04-08 19:48:51 UTC
Created attachment 180096 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
This happens when starting KMail, too. 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? *** Bug 502684 has been marked as a duplicate of this bug. *** Created attachment 180189 [details]
KMail crash report
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. (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 (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... (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 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? QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" is a workaround for me. (In reply to auxsvr from comment #11) > QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" is a workaround for me. Confirmed. That works for me even without the Sig6 I get when using `QT_QPA_PLATFORM=xcb`. Best, Jan Just for the record: Starting KMail with QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" set also makes the crash disappear I experience on Artix and X11. Looks like some Qt upstream problem with Qt 6.9.0, no?! I just created a Qt bug report referencing this bug here: https://bugreports.qt.io/browse/QTBUG-136088 There is already https://bugreports.qt.io/browse/QTBUG-135935 Maik Oh – I didn't find that. Thanks for the info, I'll close my one as a duplicate I am afraid of writing something irrelevant in the QT bug tracker, but I am using Wayland and more modern hardware. lsgpu gives card0 Intel Dg2 (Gen12) drm:/dev/dri/card0 └─renderD129 drm:/dev/dri/renderD129 card1 Intel Alderlake_p (Gen12) drm:/dev/dri/card1 └─renderD128 drm:/dev/dri/renderD128 and lspci -k | grep -EA3 'VGA|DISPLAY' shows this: 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) Subsystem: Dell Device 0beb Kernel driver in use: i915 Kernel modules: i915, xe I am running KDE under Wayland, at least according to $XDG_SESSION_TYPE Don't be afraid ;-) This is definitely an upstream bug. And they already closed it as "wontfix". Maybe, some more information and/or complaints will be an argument to investigate this further?! If the information is really irrelevant, they will say so … |