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

Bug #1245087 reported by Fabio Duran Verdugo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

Reconnect to my wireless connection

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.10.0-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Sat Oct 26 20:20:08 2013
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2013-07-07 (111 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130704)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
SegvAnalysis:
 Segfault happened at: 0x7f353f750263: mov 0x90(%rax),%rdi
 PC (0x7f353f750263) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Fabio Duran Verdugo (fabioduran) wrote :
information type: Private → Public
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.