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 356156 - crash in Evolution: closing the main window ...
crash in Evolution: closing the main window ...
Status: RESOLVED DUPLICATE of bug 330157
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-15 18:13 UTC by f_red_bergen
Modified: 2006-09-17 16:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description f_red_bergen 2006-09-15 18:13:30 UTC
What were you doing when the application crashed?
closing the main window in email mode


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 163479552 vsize: 0 resident: 163479552 share: 0 rss: 41566208 rss_rlim: 0
CPU usage: start_time: 1158343870 rtime: 0 utime: 1058 stime: 0 cutime:1018 cstime: 0 timeout: 40 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232832848 (LWP 5766)]
[New Thread -1296610400 (LWP 5785)]
[New Thread -1287824480 (LWP 5782)]
[New Thread -1266582624 (LWP 5775)]
[New Thread -1258153056 (LWP 5769)]
[New Thread -1249760352 (LWP 5768)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 André Klapper 2006-09-15 18:59:27 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 f_red_bergen 2006-09-16 22:26:06 UTC
Okay, I think this might be better -- I am using the "unstable" version because it seems better at handling large maildir-style mailboxes, with less crashing. But it still does this, and doesn't remember which messages had been marked "read" before it crashed. Thanks, Fred

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 137043968 vsize: 0 resident: 137043968 share: 0 rss: 34521088 rss_rlim: 0
CPU usage: start_time: 1158443658 rtime: 0 utime: 7576 stime: 0 cutime:5152 cstime: 0 timeout: 2424 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 -1232058704 (LWP 5665)]
[New Thread -1322263648 (LWP 5824)]
[New Thread -1313870944 (LWP 5822)]
[New Thread -1305478240 (LWP 5675)]
[New Thread -1292031072 (LWP 5671)]
[New Thread -1268663392 (LWP 5670)]
[New Thread -1260233824 (LWP 5668)]
[New Thread -1251841120 (LWP 5667)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232058704 (LWP 5665))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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 3 André Klapper 2006-09-17 16:04:39 UTC
Perfect stacktrace, thanks a lot!
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 ***