evolution crashed with SIGSEGV in webkit_dom_html_image_element_set_src()

Bug #1589467 reported by Jorge Morais
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

The error occurred when I clicked on the ".." following a list of on recipients of an e-mail I had sent.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: evolution 3.18.2-0ubuntu1~wily1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
Uname: Linux 4.2.0-36-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Jun 6 08:35:13 2016
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2015-06-11 (360 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: evolution
SegvAnalysis:
 Segfault happened at: 0x7ff9c5bd244c: mov 0x10(%rax),%rdi
 PC (0x7ff9c5bd244c) 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 wily on 2015-10-22 (227 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jorge Morais (jorgemorais) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) 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 #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.

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.