e-addressbook-factory crashed with SIGSEGV in g_main_context_dispatch()

Bug #602225 reported by gurpreet
112
This bug affects 22 people
Affects Status Importance Assigned to Milestone
evolution-data-server
Fix Released
Critical
evolution-data-server (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: evolution-data-server

I was composing an email and when I tried to search for the contact by typing first letter of name the address book crashed .

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution-data-server 2.30.2-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Tue Jul 6 16:22:33 2010
ExecutablePath: /usr/lib/evolution/e-addressbook-factory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/evolution/e-addressbook-factory
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_IN
SegvAnalysis:
 Segfault happened at: 0x3e2f5f: movl $0x0,0x14(%eax)
 PC (0x003e2f5f) ok
 source "$0x0" ok
 destination "0x14(%eax)" (0xaaaaaabe) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /usr/lib/libedata-book-1.2.so.2
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
Title: e-addressbook-factory crashed with SIGSEGV in g_main_context_dispatch()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
gurpreet (gurpreet-amrok) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 bookview_idle_stop (data=0x8606050)
 g_idle_dispatch (source=0x870ccc8, callback=0xaaaaaaaa,
 g_main_context_dispatch (context=0x85fb1c0)
 g_main_context_iterate (context=0x85fb1c0,
 g_main_loop_run (loop=0x85f8930)

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-data-server (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=623703

Changed in evolution-data-server (Ubuntu):
status: New → Triaged
Changed in evolution-data-server:
status: Unknown → New
Revision history for this message
jdstrydom (jdstrydom) wrote :

affects am64 as well

  Installed: 2.30.2-0ubuntu3
  Candidate: 2.30.2-0ubuntu3
  Version table:
 *** 2.30.2-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Pedro Villavicencio (pedro) wrote :
Changed in evolution-data-server (Ubuntu):
status: Triaged → Fix Committed
Changed in evolution-data-server:
status: New → Fix Released
Revision history for this message
Oded Arbel (oded-geek) wrote :

I'm seeing this problem on Maverick with Evolution 2.30.2-1ubuntu3 .

Will this be fixed for 10.10 - as I'm under the impression that 2.32 (where the fix was committed) will not be available in 10.10?

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Obed,

if the bug was set as fixed this is because it will be fixed, by backporting the fix in the version supported by 10.10.

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

I ported the bugfix to version 2.30, my fix is in the branch lp:~bmillemathias/ubuntu/maverick/evolution-data-server/main

Revision history for this message
Natim (site-remy) wrote :

Is it possible to have a updated package for this bug ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package evolution-data-server - 2.30.3-1ubuntu2

---------------
evolution-data-server (2.30.3-1ubuntu2) maverick; urgency=low

  * debian/patches/60_google_backend_lookup.patch:
    - Fix crash when lookup address in google backend (LP: #602225)
 -- Baptiste Mille-Mathias <email address hidden> Sat, 04 Sep 2010 11:26:17 +0200

Changed in evolution-data-server (Ubuntu):
status: Fix Committed → Fix Released
Changed in evolution-data-server:
importance: Unknown → Critical
Revision history for this message
Natim (site-remy) wrote :

I have evolution-data-server but still get this bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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