When I open Evolution a core dump starts and Evolution finally quits. Consequently, i am lost to know how what measures to take to open Evolution successfully. Any suggestions? I have tried reboot without success.
Version: Evolution 3.58.1-1.1 under Gnome
Release OpenSUSE Tumbleweed 20251112-3803.1
Has it ever worked?
If yes, what “changed” since the last time it worked?
… A ‘zypper dup’ update?
… Some other activitiy?
What if you log in using a new user account … does it work?
(if it works, that possibly suggests corruption in your regular user account, related to Evolution configuration).
The OpenSUSE release (installed with zypper dup) quoted above is the latest from today. The behaviour began thereafter.
Evolution opened as usual by highlighting the top new email in the Inbox. But it did not display the email contents before the core dump and crash. I was able to delete that mail quickly before the core dump was initiated and after that all appeared to work normally again. So the deleted mail may have been the culprit, I suppose.
The deleted mail originated from a trusted source and I am now unable to download it again from my mail service provider.
But today the core dump and crash happened again with a different mail on top of the inbox from a different trusted source. So it seems that the mails are not the culprit. I am beginning to suspect some Evolution or Gnome issue.
Looking good AFAICS. There is a slight chance that the “home_ecsos” repo contains some library that is out of date for TW and that you got installed, but I doubt it.
But to make sure you could disable it and then look in Myrlyn or “YaST sw_single” if that makes any packages that you have install show up in red; that would be packages that are newer than the available version in any active repository.
Other than that, you could check if you are missing any shared lib that evolution needs with
ldd `which evolution`
Check the output of that command for any error messages like complaints about missing shared libs.
If that also doesn’t help, please file a bug report.
BTW having both “PackMan” and “PackMan Essentials” at the same time is redundant; “PackMan Essentials” is a subset of the whole “PackMan”. If you have “PackMan” anyway, you can remove “Packman Essentials”.
(the exact wording or format might have changed over time)
This tells you that the executable is linked against a shared lib that you don’t have on your system; either not at all or not in that version. This is one of those things that theoretically shouldn’t happen, yet they do. In that case, something went horribly wrong.
In other words, it seems that the core dump and crash is started repeatably by the Evolution function Ctrl+I
i.e. “Force images in HTML mail to be loaded”
evolution is still on GTK3 and I’m not sure it even uses Vulkan? Apparently there is no way to force the renderer, is it still using the cairo renderer?
I saw something similar with the “Gnome Camera” web cam app (AKA “snapshot”) with the update of gstreamer-plugins-rs to 1.26.8, but that is a GTK4 app so:
GSK_RENDERER=opengl snapshot
works, but
GSK_RENDERER=opengl evolution
has no effect here (it doesn’t even read the GSK_RENDERER variable apparently).
But maybe image loaders (for some specific formats?) have issues with older AMD silicon?