On a fully up-to-date Ubuntu Gnome 16.04 with the latest Gnome 3.20 from the gnome3-staging PPA. The crash occured when I repeatedly tried to click on the + sign next to To: in a mail, in order to see all recipients.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: evolution 3.20.2-0ubuntu1~xenial1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon May 23 16:23:04 2016
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2015-04-17 (401 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150416)
ProcCmdline: evolution
SegvAnalysis:
Segfault happened at: 0x7f3c74fba259: mov 0x10(%rax),%rdi
PC (0x7f3c74fba259) ok
source "0x10(%rax)" (0x656c69662d6f7675) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
webkit_dom_html_image_element_set_src () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
Title: evolution crashed with SIGSEGV in webkit_dom_html_image_element_set_src()
UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
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 #1571623, 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.