evolution-data-server-2.28 crashed with SIGSEGV in dbus_timeout_handle()

Bug #527023 reported by Maciej Bęcławski
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: evolution-data-server

Lucid. Evolution crashed when starting.

ProblemType: Crash
Architecture: i386
Date: Wed Feb 24 07:18:38 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/evolution/evolution-data-server-2.28
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
NonfreeKernelModules: wl
Package: evolution-data-server 2.28.2-1ubuntu3
ProcCmdline: /usr/lib/evolution/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2 --oaf-ior-fd=35
ProcEnviron:
 LC_TIME=en_DK.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0xb8339a: mov 0x4(%esi),%eax
 PC (0x00b8339a) ok
 source "0x4(%esi)" (0x7ffffffb) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_timeout_handle () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: evolution-data-server-2.28 crashed with SIGSEGV in dbus_timeout_handle()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #438457, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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