evolution crashed with SIGSEGV in dbus_timeout_handle()

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

Bug Description

Binary package hint: evolution

escription: Ubuntu lucid (development branch)
Release: 10.04
evolution:
  Installed: 2.28.3-0ubuntu9
  Candidate: 2.28.3-0ubuntu9
  Version table:
 *** 2.28.3-0ubuntu9 0
        500 http://ubuntu.mirror.garr.it/mirrors/ubuntu-archive/ lucid/main Packages
        100 /var/lib/dpkg/status
the application was on and suddenly is turned off

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
Date: Mon Apr 19 07:10:12 2010
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/bin/evolution
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x11a39a: mov 0x4(%esi),%eax
 PC (0x0011a39a) ok
 source "0x4(%esi)" (0x1766795b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown 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 cdrom dialout dip lpadmin netdev plugdev sambashare

Revision history for this message
lucius (sallucius) 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.