Evolution crashed with SIGSEGV

[Dirk Schmidtke]

Evolution crashed after doing the following steps:

1. clicked new email
2. New email window opened, but could not enter email text body (no form field displayed)
3. Closed new email window, which made Evolution crash

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: evolution 3.43.3-1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 17 15:55:24 2022
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2022-02-22 (22 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcCmdline: evolution
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fcd557ccdb6: mov (%rdi),%rax
 PC (0x7fcd557ccdb6) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
Title: evolution crashed with SIGSEGV
UpgradeStatus: Upgraded to jammy on 2022-02-22 (22 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1964922, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.