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 417890 - crash in Evolution: checking exchange e-mail
crash in Evolution: checking exchange e-mail
Status: RESOLVED DUPLICATE of bug 330157
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-13 15:17 UTC by mnishiza
Modified: 2007-03-17 19:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mnishiza 2007-03-13 15:17:15 UTC 
What were you doing when the application crashed?
checking exchange e-mail


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

Memory status: size: 120291328 vsize: 0 resident: 120291328 share: 0 rss: 29114368 rss_rlim: 0
CPU usage: start_time: 1173798956 rtime: 0 utime: 280 stime: 0 cutime:271 cstime: 0 timeout: 9 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 -1233348944 (LWP 10797)]
[New Thread -1309021280 (LWP 10839)]
[New Thread -1300628576 (LWP 10838)]
[New Thread -1292235872 (LWP 10837)]
[New Thread -1283843168 (LWP 10811)]
[New Thread -1275450464 (LWP 10810)]
[New Thread -1257321568 (LWP 10809)]
[New Thread -1247462496 (LWP 10808)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 118304

Thread 1 (Thread -1233348944 (LWP 10797))

  • #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 folder_changed
    at camel-vee-folder.c line 1457
  • #7 camel_object_trigger_event
    at camel-object.c line 1504
  • #8 vee_remove_folder
    at camel-vee-folder.c line 831
  • #9 camel_vee_folder_remove_folder
    at camel-vee-folder.c line 296
  • #10 camel_vee_folder_finalise
    at camel-vee-folder.c line 1723
  • #11 camel_object_unref
    at camel-object.c line 928
  • #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 command_quit
    at e-shell-window-commands.c line 111
  • #22 bonobo_ui_component_add_verb_list
    from /usr/lib/libbonoboui-2.so.0
  • #23 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #24 bonobo_closure_invoke_va_list
    from /usr/lib/libbonobo-2.so.0
  • #25 bonobo_closure_invoke
    from /usr/lib/libbonobo-2.so.0
  • #26 bonobo_ui_component_add_verb_list
    from /usr/lib/libbonoboui-2.so.0
  • #27 _ORBIT_skel_small_Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobo-2.so.0
  • #28 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #29 Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobo-2.so.0
  • #30 bonobo_ui_engine_add_sync
    from /usr/lib/libbonoboui-2.so.0
  • #31 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #37 bonobo_ui_engine_emit_verb_on_w
    from /usr/lib/libbonoboui-2.so.0
  • #38 bonobo_ui_sync_menu_new
    from /usr/lib/libbonoboui-2.so.0
  • #39 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #42 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #43 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #44 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 gtk_menu_shell_append
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #50 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #51 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #52 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #53 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #54 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #56 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #58 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #59 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #60 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #61 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #62 main
    at main.c line 615
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-03-17 19:56:13 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 330157 ***