Bug 306001 – evolution crashed while trying to delete an IMAP account

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 306001 - evolution crashed while trying to delete an IMAP account


Summary:	evolution crashed while trying to delete an IMAP account


Status:	RESOLVED DUPLICATE of bug 324168

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.2.x (obsolete)
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-05-31 06:40 UTC by C Shilpa
Modified:	2006-06-17 15:52 UTC

See Also:
GNOME target:	---
GNOME version:	2.5/2.6

Description C Shilpa 2005-05-31 06:40:19 UTC

Distribution/Version: NLD

Here is the stack trace:

+ Trace 60372

#0 ??
#1 ??
#2 ??
#3 ??
#4 msgrcv
from /lib/tls/libpthread.so.0
#5 <signal handler called>
#6 camel_message_info_free
at camel-folder-summary.c line 2567
#7 vee_message_info_free
at camel-vee-summary.c line 46
#8 camel_message_info_free
at camel-folder-summary.c line 2584
#9 camel_folder_summary_clear
at camel-folder-summary.c line 1034
#10 camel_folder_summary_finalize
at camel-folder-summary.c line 169
#11 camel_object_unref
at camel-object.c line 920
#12 camel_folder_finalize
at camel-folder.c line 193
#13 camel_object_unref
at camel-object.c line 920
#14 store_info_unref
at mail-component.c line 188
#15 mail_component_remove_store
at mail-component.c line 1064
#16 mail_component_remove_store_by_uri
at mail-component.c line 1092
#17 account_delete_clicked
at em-account-prefs.c line 245
#18 g_cclosure_marshal_VOID__VOID
from /opt/gnome/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#20 signal_emit_unlocked_R
from /opt/gnome/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#23 gtk_button_clicked
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#24 ??
#25 ??
#26 ??
#27 __JCR_LIST__
from /opt/gnome/lib/libgobject-2.0.so.0
#28 ??
#29 ??
#30 ??
#31 g_value_peek_pointer
from /opt/gnome/lib/libgobject-2.0.so.0
#32 gtk_button_grab_notify
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#33 ??
#34 ??
#35 ??
#36 __JCR_LIST__
from /opt/gnome/lib/libgobject-2.0.so.0
#37 __JCR_LIST__
from /opt/gnome/lib/libgobject-2.0.so.0
#38 ??
#39 ??
#40 g_cclosure_marshal_VOID__VOID
from /opt/gnome/lib/libgobject-2.0.so.0
#41 g_cclosure_marshal_VOID__VOID
from /opt/gnome/lib/libgobject-2.0.so.0
#42 g_type_class_meta_marshal
from /opt/gnome/lib/libgobject-2.0.so.0
#43 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#44 signal_emit_unlocked_R
from /opt/gnome/lib/libgobject-2.0.so.0
#45 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#46 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#47 gtk_button_released
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#48 ??
#49 ??
#50 ??
#51 g_value_peek_pointer
from /opt/gnome/lib/libgobject-2.0.so.0
#52 gtk_button_released
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#53 ??
#54 sortable_info.5
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#55 ??
#56 _gtk_marshal_VOID__ENUM_FLOAT
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#57 ??
#58 ??
#59 ??
#60 g_value_peek_pointer
from /opt/gnome/lib/libgobject-2.0.so.0

Comment 1 Khasim Shaheed 2005-06-10 11:57:32 UTC

Not able to reproduce. Hence closing the bug.

Feel free to reopen the bug if you face the same issue again.

Comment 2 André Klapper 2006-06-17 15:51:08 UTC

khasim: just because you're unable to reproduce does not mean that you are allowed to close this. plain wrong.

Comment 3 André Klapper 2006-06-17 15:52:20 UTC

marking correctly as a duplicate of bug 324168 - this bug exists and is valid.

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