Linking Google calendar to Evolution caused crash

Bug #762993 reported by bclintbe
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server
Expired
Critical
evolution-data-server (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

I was just finishing the process of linking my Google calendar with Evolution. I had already retrieved my list of calendars, selected the one I wanted, and put in my password for the second time. Evolution simply closed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution 2.32.2-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sat Apr 16 12:31:14 2011
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcCmdline: evolution
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x40c9d4: mov (%edx),%eax
 PC (0x0040c9d4) ok
 source "(%edx)" (0x00000011) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libedataserverui-1.2.so.11
 ?? () from /usr/lib/libedataserverui-1.2.so.11
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: evolution crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
bclintbe (bclintbe) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 rebuild_model (selector=0xa1140b8) at e-source-selector.c:365
 on_idle_rebuild_model_callback (selector=0xa1140b8) at e-source-selector.c:479
 g_idle_dispatch (source=0xa7edd50, callback=0x40ce60 <on_idle_rebuild_model_callback>, user_data=0xa1140b8) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:4545
 g_main_dispatch (context=0x979bca0) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:2440
 g_main_context_dispatch (context=0x979bca0) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:3013

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=648369

affects: evolution (Ubuntu) → evolution-data-server (Ubuntu)
Changed in evolution-data-server (Ubuntu):
status: New → Triaged
Changed in evolution-data-server:
importance: Unknown → Critical
status: Unknown → New
Changed in evolution-data-server:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Upstream said the commit at http://git.gnome.org/browse/evolution-data-server/commit/?id=a92e3633bece22801adb1bcf0bfd84c79de42f1f should fix this bug as well, could somebody try it and comment back? Otherwise please try the same on Oneiric. Thanks.

Changed in evolution-data-server (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Fabio Duran Verdugo (fabioduran) wrote :

still is valid this bug?, could somebody try it?

Changed in evolution-data-server:
status: Incomplete → Expired
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in evolution-data-server (Ubuntu):
status: Incomplete → Invalid
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.