[apport] evolution-2.10 crashed with SIGSEGV in ORBit_object_get_connection()

[Martin Schaaf]

Binary package hint: evolution

Added a caldav calendar and during connection it crashed.

ProblemType: Crash
Architecture: powerpc
Date: Wed Jun 20 12:07:32 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/evolution-2.10
Package: evolution 2.10.1-0ubuntu2 [modified: usr/lib/evolution/2.10/libemiscwidgets.so.0.0.0 usr/lib/evolution/2.10/libeshell.so.0.0.0 usr/lib/evolution/2.10/libetable.so.0.0.0 usr/lib/evolution/2.10/libetext.so.0.0.0 usr/lib/evolution/2.10/libetimezonedialog.so.0.0.0 usr/lib/evolution/2.10/libeutil.so.0.0.0 usr/lib/evolution/2.10/libevolution-a11y.so.0.0.0 usr/lib/evolution/2.10/libevolution-widgets-a11y.so.0.0.0 usr/lib/evolution/2.10/killev usr/lib/evolution/2.10/evolution-addressbook-export usr/lib/evolution/2.10/evolution-alarm-notify usr/lib/evolution/2.10/backup usr/bin/evolution-2.10]
PackageArchitecture: powerpc
ProcCmdline: evolution calendar:///?startdate=20070620T120000
ProcCwd: /home/ms
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libORBit-2.so.0
 ORBit_object_get_connection () from /usr/lib/libORBit-2.so.0
 ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0
 ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0
Uname: Linux inderecke 2.6.20-16-powerpc64-smp #3 SMP Thu Jun 7 19:39:25 UTC 2007 ppc64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.