Bug 419556 – crash in Evolution: Deleting an imap folder ...

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 419556 - crash in Evolution: Deleting an imap folder ...


Summary:	crash in Evolution: Deleting an imap folder ...


Status:	RESOLVED DUPLICATE of bug 324168

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

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

URL:
Whiteboard:

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

Reported:	2007-03-17 23:40 UTC by Karl Mikaelsson
Modified:	2008-04-10 08:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Karl Mikaelsson 2007-03-17 23:40:05 UTC

What were you doing when the application crashed?
Deleting an imap folder (1) with two subfolders (1, 1.2, 1.2.3). 1.2.3 had two mails which I moved out or deleted before trying to delete the tree.


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.0 2007-03-16 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-gentoo-r3 #2 Sat Mar 17 23:19:34 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaCandy
Icon Theme: gnome

Memory status: size: 140115968 vsize: 140115968 resident: 30908416 share: 18018304 rss: 30908416 rss_rlim: 4294967295
CPU usage: start_time: 1174174160 rtime: 665 utime: 630 stime: 35 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1231808320 (LWP 10886)]
[New Thread -1272800368 (LWP 10923)]
[New Thread -1353655408 (LWP 10919)]
[New Thread -1311425648 (LWP 10910)]
[New Thread -1302623344 (LWP 10904)]
[New Thread -1281193072 (LWP 10901)]
[New Thread -1264407664 (LWP 10897)]
[New Thread -1247183984 (LWP 10895)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 119574

Thread 1 (Thread -1231808320 (LWP 10886))

#0 __kernel_vsyscall
#1 ??
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 pthread_mutex_lock
from /lib/libpthread.so.0
#5 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#6 vee_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#7 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#8 vtrash_uid_removed
from /usr/lib/libcamel-provider-1.2.so.10
#9 vtrash_folder_changed
from /usr/lib/libcamel-provider-1.2.so.10
#10 folder_changed
from /usr/lib/libcamel-provider-1.2.so.10
#11 camel_object_trigger_event
from /usr/lib/libcamel-1.2.so.10
#12 thaw
from /usr/lib/libcamel-provider-1.2.so.10
#13 imap_thaw
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimap.so
#14 camel_folder_thaw
from /usr/lib/libcamel-provider-1.2.so.10
#15 emfu_delete_rec
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 emfu_delete_rec
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#17 emfu_delete_rec
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#18 emfu_delete_response
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#19 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#25 action_widget_activated
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_real_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#34 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#35 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#36 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#39 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_button_button_release
from /usr/lib/libgtk-x11-2.0.so.0
#41 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#42 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#43 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#44 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#45 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#46 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#47 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#48 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#49 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#50 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#51 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#52 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#53 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#54 bonobo_main
from /usr/lib/libbonobo-2.so.0
#55 main
#0 __kernel_vsyscall



----------- .xsession-errors (4203980 sec old) ---------------------
--------------------------------------------------

Comment 1 Karl Mikaelsson 2007-03-17 23:46:33 UTC

Slight correction - there was no subfolders in between. The maildir folder looked something like .foo.bar.baz, but there was no .foo.bar folder "in between" (caused by a procmail rule not acting like I intended it to).
I'm not sure if that helps find the error in question though.

Comment 2 palfrey 2007-04-26 13:52:24 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 3 Diego Escalante Urrelo (not reading bugmail) 2007-06-17 08:12:14 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 4 palfrey 2007-08-17 12:57:58 UTC

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

Comment 5 André Klapper 2008-04-10 08:18:19 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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