[apport] evolution-jescs crashed with SIGSEGV

[Khorne]

Binary package hint: evolution-jescs

Evolution-jescs suddenly crashed when exiting evolution

ProblemType: Crash
Architecture: i386
Date: Sat Mar 31 18:07:13 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/evolution/2.10/evolution-jescs
Package: evolution-jescs 2.9.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/evolution/2.10/evolution-jescs --oaf-activate-iid=OAFIID:GNOME_Evolution_SunOneStorage_CalendarFactory --oaf-ior-fd=28
ProcCwd: /
ProcEnviron:
 LANG=pl_PL.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution-jescs
Stacktrace:
 #0 0xb71cd113 in ?? () from /usr/lib/libORBit-2.so.0
 #1 0x080b3e90 in ?? ()
 #2 0x00000011 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/libORBit-2.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux blacktosh 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

[Daniel Holbach (dholbach)]

Thanks for your bug report.

[Apport retracing service (apport)]

StacktraceTop:link_connection_state_changed (cnx=0x80b3e90, status=LINK_DISCONNECTED) at linc-connection.c:774
giop_connection_handle_input (lcnx=0x80b3e90) at giop-recv-buffer.c:1326
link_connection_io_handler (gioc=0x0, condition=<value optimized out>, data=0x80b3e90) at linc-connection.c:1387
link_source_dispatch (source=0x8103200, callback=0xb71cd610 <link_connection_io_handler>, user_data=0x80b3e90) at linc-source.c:159

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release?

If you are able to reproduce the crash, can you please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Thanks in advance.

[Khorne (szczygiel-piotr)]

I mark it invalid as it doesn't happen for a long time since reported.