Bug 338218 – it just quit

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 338218 - it just quit


Summary:	it just quit


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-04-12 13:47 UTC by user
Modified:	2006-06-19 05:49 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description user 2006-04-12 13:47:19 UTC

Distribution: SuSE Linux 9.3 (i586)
Package: Evolution
Priority: Normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: SUSE
Synopsis: it just quit
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution-2.6'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232456000 (LWP 7835)]
[New Thread -1300464720 (LWP 7925)]
[Thread debugging using libthread_db enabled]
[New Thread -1232456000 (LWP 7835)]
[New Thread -1300464720 (LWP 7925)]
[Thread debugging using libthread_db enabled]
[New Thread -1232456000 (LWP 7835)]
[New Thread -1300464720 (LWP 7925)]
[New Thread -1292072016 (LWP 7889)]
[New Thread -1283679312 (LWP 7879)]
[New Thread -1255298128 (LWP 7853)]
[New Thread -1274180688 (LWP 7850)]
[New Thread -1265632336 (LWP 7848)]
[New Thread -1246868560 (LWP 7843)]
[New Thread -1242145872 (LWP 7838)]
[New Thread -1242063952 (LWP 7837)]
0xffffe410 in ?? ()

+ Trace 67587

Thread 1 (Thread -1232456000 (LWP 7835))

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 gnome_init_with_popt_table
from /opt/gnome/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 ??
#8 ??
#9 ??
#10 ??
#11 raise
from /lib/tls/libc.so.6
#12 abort
from /lib/tls/libc.so.6
#13 mono_handle_native_sigsegv
from /usr/lib/libmono.so.0
#14 mini_method_compile
from /usr/lib/libmono.so.0
#15 <signal handler called>
#16 camel_message_info_uint32
at camel-folder-summary.c line 2862
#17 vee_info_uint32
at camel-vee-summary.c line 71
#18 camel_message_info_uint32
at camel-folder-summary.c line 2862
#19 folder_getv
at camel-folder.c line 352
#20 camel_object_get
at camel-object.c line 1599
#21 view_changed
at mail-component.c line 512
#22 view_changed_timeout
at mail-component.c line 590
#23 g_source_get_current_time
from /opt/gnome/lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#25 g_main_context_acquire
from /opt/gnome/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /opt/gnome/lib/libglib-2.0.so.0
#27 bonobo_main
from /opt/gnome/lib/libbonobo-2.so.0
#28 main
at main.c line 611
#0 ??





------- Bug created by bug-buddy at 2006-04-12 13:47 -------

Comment 1 Guillaume Desmottes 2006-04-12 16:18:48 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Sankar P 2006-06-19 05:49:47 UTC

What type of account where you using? Exchange? A fix has been made recently to fix a few issues in camel-stub-marshall code by Fejj. It fixes a few crashes. The stack traces matches some stub-marshal code. Grab the latest build and reopen with traces if you get this again.