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 436203 - Crash when trying to disable an account
Crash when trying to disable an account
Status: RESOLVED DUPLICATE of bug 324168
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-05-05 21:02 UTC by Milan Bouchet-Valat
Modified: 2007-06-21 16:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Milan Bouchet-Valat 2007-05-05 21:02:28 UTC 
Steps to reproduce:
In Edit -> Preferences, I try to disable one of my 2 mail accounts (IMAP): one is working flawlessly, but the other makes Evo crash, and I can't disable it.
I'm still able to modify this account or to make/unmake it default.

Stack trace:
[... stuff without link with the crash]
< b0987b90 >

(evolution-2.10:18673): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject'

(evolution-2.10:18673): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233365312 (LWP 18673)]
0xb738ca24 in camel_folder_summary_content_info_free ()
   from /usr/lib/libcamel-provider-1.2.so.10
(gdb) thread apply all bt

+ Trace 132618

Thread 1 (Thread -1233365312 (LWP 18673))

  • #0 camel_folder_summary_content_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #1 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #2 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #3 ??
  • #4 pthread_mutex_unlock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #6 camel_folder_summary_clear
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 ??
  • #9 pthread_mutex_unlock
  • #10 camel_object_unref
    from /usr/lib/libcamel-1.2.so.10
  • #11 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
    from /usr/lib/libcamel-1.2.so.10
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 camel_object_unref
    from /usr/lib/libcamel-1.2.so.10 


Other information:
Comment 1 Pedro Villavicencio 2007-05-05 22:56:54 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 2 Milan Bouchet-Valat 2007-05-06 09:11:28 UTC 
I hope this is better:

(gdb) thread apply all bt

+ Trace 132671

Thread 1 (Thread -1233205568 (LWP 28580))

  • #0 pthread_mutex_lock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #1 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #2 camel_message_info_free
  • #3 vee_message_info_free
    at camel-vee-summary.c line 45
  • #4 camel_message_info_free
    at camel-folder-summary.c line 2803
  • #5 camel_folder_summary_clear
    at camel-folder-summary.c line 1158
  • #6 camel_folder_summary_finalize
    at camel-folder-summary.c line 177
  • #7 camel_object_unref
    at camel-object.c line 928
  • #8 camel_folder_finalize
    at camel-folder.c line 192
  • #9 camel_object_unref
    at camel-object.c line 928
  • #10 store_info_unref
    at mail-component.c line 198
  • #11 mail_component_remove_store
    at mail-component.c line 1300
  • #12 mail_component_remove_store_by_uri
    at mail-component.c line 1327
  • #13 account_able_changed
    at em-account-prefs.c line 310
  • #14 account_able_clicked
  • #15 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 IA__g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #18 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #19 IA__g_signal_emit
    at gsignal.c line 2243
  • #20 IA__gtk_button_clicked
    at gtkbutton.c line 889
  • #21 gtk_real_button_released
    at gtkbutton.c line 1484
  • #22 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #23 g_type_class_meta_marshal
    at gclosure.c line 567
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #27 IA__g_signal_emit
    at gsignal.c line 2243
  • #28 IA__gtk_button_released
    at gtkbutton.c line 881
  • #29 gtk_button_button_release
    at gtkbutton.c line 1377
  • #30 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #31 g_type_class_meta_marshal
    at gclosure.c line 567
  • #32 IA__g_closure_invoke
    at gclosure.c line 490
  • #33 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #34 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #35 IA__g_signal_emit
    at gsignal.c line 2243
  • #36 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #37 IA__gtk_propagate_event
    at gtkmain.c line 2364
  • #38 IA__gtk_main_do_event
    at gtkmain.c line 1598
  • #39 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #40 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #41 g_main_context_iterate
    at gmain.c line 2677
  • #42 IA__g_main_loop_run
    at gmain.c line 2881
  • #43 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #44 main
    at main.c line 611 






Comment 3


André Klapper





          2007-06-21 16:44:36 UTC
        



same issue as bug 324168

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