Bug 390279 – crash in Evolution: I closed the application...

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 390279 - crash in Evolution: I closed the application...


Summary:	crash in Evolution: I closed the application...


Status:	RESOLVED DUPLICATE of bug 349521

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	392118 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-28 08:58 UTC by benoit.roussel
Modified:	2007-01-05 15:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description benoit.roussel 2006-12-28 08:58:20 UTC

What were you doing when the application crashed?
I closed the application.
Is this fixed in this version :2.8 or in a higher one?


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 133767168 vsize: 0 resident: 133767168 share: 0 rss: 38428672 rss_rlim: 0
CPU usage: start_time: 1167295985 rtime: 0 utime: 6661 stime: 0 cutime:5533 cstime: 0 timeout: 1128 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232820560 (LWP 5928)]
[New Thread -1306526816 (LWP 5991)]
[New Thread -1293943904 (LWP 5962)]
[New Thread -1283925088 (LWP 5961)]
[New Thread -1261290592 (LWP 5955)]
[New Thread -1252250720 (LWP 5954)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 97483

Thread 1 (Thread -1232820560 (LWP 5928))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 segv_redirect
at main.c line 426
#4 <signal handler called>
#5 ??
#6 camel_vee_folder_rebuild_folder
from /usr/lib/libcamel-provider-1.2.so.8
#7 camel_object_trigger_event
from /usr/lib/libcamel-1.2.so.8
#8 camel_vee_folder_new
from /usr/lib/libcamel-provider-1.2.so.8
#9 camel_vee_folder_remove_folder
from /usr/lib/libcamel-provider-1.2.so.8
#10 camel_vee_folder_new
from /usr/lib/libcamel-provider-1.2.so.8
#11 camel_object_unref
from /usr/lib/libcamel-1.2.so.8
#12 vfolder_foreach_cb
at mail-vfolder.c line 1155
#13 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#14 mail_vfolder_shutdown
at mail-vfolder.c line 1166
#15 impl_quit
at mail-component.c line 799
#16 _ORBIT_skel_small_GNOME_Evolution_Component_quit
at Evolution-common.c line 64
#17 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#18 GNOME_Evolution_Component_quit
at Evolution-stubs.c line 102
#19 es_run_quit
at e-shell.c line 1298
#20 e_shell_quit
at e-shell.c line 1366
#21 e_shell_request_close_window
at e-shell.c line 964
#22 window_delete_event_cb
at e-shell.c line 356
#23 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 bonobo_main
from /usr/lib/libbonobo-2.so.0
#35 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 Pascal Terjan 2007-01-03 00:51:23 UTC

*** Bug 392118 has been marked as a duplicate of this bug. ***

Comment 2 palfrey 2007-01-05 15:22:48 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 349521 ***