KMail Crashes when started

Help
1

Hey there,

since a few weeks KMail crashes when started with the following:

org.kde.pim.pimcommonactivities: Plasma activities is not running:  1
GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
kf.windowsystem: KWindowInfo is only functional when running on X11
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
KCrash: Application 'kmail' crashing... crashRecursionCounter = 2
zsh: segmentation fault (core dumped)  kmail

I am on Manjaro Linux with Kmail 6.4.3. The Window comes up and then directly crashes. KOrganizer and KAdressbook work so far without any issues and I do get notifications for new incoming mails, but I cannot open KMail to work with them. Any ideas what I can do to sort this issue out?

Any help appreciated.

Regards

Max

1 Like
2

Have you solved this problem?

3

I would say I found a workaround:

Setting MESA_LOADER_DRIVER_OVERRIDE=“llvmpipe” in the Desktop file avoids the issue, but not directly solves it. I found it by experimenting with different options I found online via searching for the second line of the error.

4

Please report crashes to https://bugs.kde.org, so the developers can see if there are similar reports and diagnose why it crashed. There is a great guide at Guidelines and HOWTOs/Debugging/How to create useful crash reports - KDE Community Wiki on how to include as much information as possible. Thank you for reporting!

5

I’m having the same issue, but don’t know how to apply the workaround… could you describe the process with more detail? thanks!

6

Search for the Desktop file of kmail (for me it is at /usr/share/applications/org.kde.kmail2.desktop) and change the Exec line:
Before: kmail -qwindowtitle %c %u
After: Exec=env MESA_LOADER_DRIVER_OVERRIDE=“llvmpipe” kmail -qwindowtitle %c %u

This made it work for me :slight_smile:

Will create a detailed Bug Report as soon as I find some time for it

1 Like
7

This workaround fixed Akregator for me in Fedora 43. Thanks!

1 Like
8

As I now migrated to a new PC and therefore switched again to the NVIDIA proprietary drivers, the issue is gone and I cannot create a detailed Bug report anymore. Sorry!

Therefore, I also see this for me as resolved.