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 374568 - crash in Evolution: clicked X to close evo
crash in Evolution: clicked X to close evo
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: 2006-11-13 06:04 UTC by Keith Hopkins
Modified: 2006-11-13 11:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Keith Hopkins 2006-11-13 06:04:56 UTC 
What were you doing when the application crashed?
clicked X to close evo


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

Memory status: size: 247107584 vsize: 0 resident: 247107584 share: 0 rss: 43577344 rss_rlim: 0
CPU usage: start_time: 1163394157 rtime: 0 utime: 1943 stime: 0 cutime:1727 cstime: 0 timeout: 216 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 -1232423248 (LWP 14351)]
[New Thread -1390412896 (LWP 14510)]
[New Thread -1386239072 (LWP 14368)]
[New Thread -1345328224 (LWP 14366)]
[New Thread -1336935520 (LWP 14363)]
[New Thread -1326675040 (LWP 14362)]
[New Thread -1277404256 (LWP 14358)]
[New Thread -1285833824 (LWP 14357)]
[New Thread -1269011552 (LWP 14354)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 85983

Thread 1 (Thread -1232423248 (LWP 14351))

  • #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 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


André Klapper





          2006-11-13 11:30:18 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 330157 ***