evolution crashed with SIGSEGV

Bug #1968163 reported by Byron
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
New
Undecided
Unassigned

Bug Description

Evolution crashes on startup in Ubuntu 22.04. It looks like it is a internationalization issue.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: evolution 3.44.0-1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 7 07:14:14 2022
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2022-04-07 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
 Segfault happened at: 0x7fd8faace2eb: mov 0x8,%rax
 PC (0x7fd8faace2eb) ok
 source "0x8" (0x00000008) 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/libffi.so.8
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
Title: evolution crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Byron (byron-goodman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1965798, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.