evolution crashed with SIGSEGV in dbus_timeout_handle()

Bug #571453 reported by Nicolas DERIVE
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: evolution

it may be the same as https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/530760. I got a crash few minutes after evolution start.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
CrashCounter: 1
Date: Wed Apr 28 23:21:32 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
ProcCmdline: evolution --component=mail
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
 LANGUAGE=fr_FR:fr:en_GB:en
SegvAnalysis:
 Segfault happened at: 0x9f139a: mov 0x4(%esi),%eax
 PC (0x009f139a) ok
 source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
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/libgnome-keyring.so.0
Title: evolution crashed with SIGSEGV in dbus_timeout_handle()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video

Revision history for this message
Nicolas DERIVE (kalon33) wrote :
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 #530760, 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.

Other bug subscribers

Remote bug watches

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