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

Bug #1166804 reported by wicasa71
498
This bug affects 58 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Confirmed
Undecided
Unassigned

Bug Description

crash

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: evolution-data-server 3.8.0-0ubuntu1~raring1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 9 08:59:47 2013
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2013-04-07 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fbeca913b2e: mov 0x90(%rax),%rdi
 PC (0x7fbeca913b2e) 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 lpadmin plugdev sambashare sudo

Revision history for this message
wicasa71 (wicasa71) wrote :
Tim Lunn (darkxst)
information type: Private → Public
Revision history for this message
Michael Gratton (mjog) wrote :

This happened for me on a lossy internet connection.

Changed in ubuntu-gnome:
status: New → Confirmed
Revision history for this message
Jeffrey Flaker (jflaker) wrote :

Happens on boot before my wireless is connected....Probably need to catch the error then retry in 30 seconds

Revision history for this message
Fabio Duran Verdugo (fabioduran) wrote :

I can always reproduce when I reconnect to my wan and wireless connection

Andrey (am6puk)
information type: Public → Public Security
Ubuntu GNOME (ug-bot)
tags: removed: need-amd64-retrace
Tim Lunn (darkxst)
Changed in ubuntu-gnome:
milestone: none → trusty
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

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