evolution-exchange-storage crashed with SIGSEGV in soup_message_queue_next()

[William Grant]

Binary package hint: evolution-exchange

I wasn't doing anything at all with that account.

ProblemType: Crash
Architecture: i386
Date: Tue Mar 18 15:56:06 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/evolution/2.22/evolution-exchange-storage
NonfreeKernelModules: nvidia
Package: evolution-exchange 2.22.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/evolution/2.22/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Connector_CalFactory:1.2 --oaf-ior-fd=21
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
Signal: 11
SourcePackage: evolution-exchange
StacktraceTop:
 soup_message_queue_next () from /usr/lib/libsoup-2.4.so.1
 soup_message_queue_first () from /usr/lib/libsoup-2.4.so.1
 soup_message_queue_remove_message ()
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? ()
Title: evolution-exchange-storage crashed with SIGSEGV in soup_message_queue_next()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner vboxusers video
SegvAnalysis:
 Segfault happened at: 0xb6fee222 <soup_message_queue_next+130>: mov (%eax),%eax
 PC (0xb6fee222) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:soup_message_queue_next (queue=0x811b700, iter=0xbfeb2d64) at soup-message-queue.c:164
soup_message_queue_first (queue=0x811b700, iter=0xbfeb2d64) at soup-message-queue.c:104
soup_message_queue_remove_message (queue=0x811b700, msg=0x80bce50)
message_finished (msg=0x80bce50, user_data=0x80e4cb8) at soup-session.c:983
g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0

[Sebastien Bacher (seb128)]

Thank you for your bug report, the crash is similar to http://bugzilla.gnome.org/show_bug.cgi?id=510365

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!