evolution-calendar-factory crashed with SIGSEGV in soup_socket_connect_sync()

Bug #1342044 reported by Muelli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

I guess I was resuming

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution-data-server 3.10.4-0ubuntu1.1
Uname: Linux 3.14.0-031400rc4-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Jul 15 00:08:35 2014
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2014-01-22 (173 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017)
ProcCmdline: //usr/lib/evolution/evolution-calendar-factory -w
SegvAnalysis:
 Segfault happened at: 0x7f6bc1d57263: mov 0x90(%rax),%rdi
 PC (0x7f6bc1d57263) ok
 source "0x90(%rax)" (0x00000090) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 soup_socket_connect_sync () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
Title: evolution-calendar-factory crashed with SIGSEGV in soup_socket_connect_sync()
UpgradeStatus: Upgraded to trusty on 2014-07-01 (13 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) 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 #1235446, 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.