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 356484 - crash in Evolution: The application was aski...
crash in Evolution: The application was aski...
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-18 05:32 UTC by maillist
Modified: 2006-09-18 19:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description maillist 2006-09-18 05:32:35 UTC
What were you doing when the application crashed?
The application was asking for account passwords every 10 minutes checking for mail. Remember password was already checked. I allowed it to repeat several times. I finally canceled both then went to close evolution as it crashed.


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

Memory status: size: 156323840 vsize: 0 resident: 156323840 share: 0 rss: 36184064 rss_rlim: 0
CPU usage: start_time: 1158556189 rtime: 0 utime: 743 stime: 0 cutime:689 cstime: 0 timeout: 54 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 -1231989072 (LWP 17216)]
[New Thread -1266476128 (LWP 17249)]
[New Thread -1274868832 (LWP 17234)]
[New Thread -1313043552 (LWP 17233)]
[New Thread -1292158048 (LWP 17229)]
[New Thread -1283298400 (LWP 17228)]
[New Thread -1258083424 (LWP 17224)]
[New Thread -1249690720 (LWP 17223)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 Karsten Bräckelmann 2006-09-18 11:24:02 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.

Also, are you able to reproduce this?
Comment 2 maillist 2006-09-18 18:05:36 UTC
Yes the bug is reproducible, by 
1. opening evolution
2. closing evolution


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1232505168 (LWP 8019)]
0x00000000 in ?? ()
(gdb) thread apply all bt

Thread 1 (Thread -1232505168 (LWP 8019))

  • #0 ??
  • #1 camel_vee_folder_rebuild_folder
    from /usr/lib/libcamel-provider-1.2.so.8
  • #2 camel_object_trigger_event
    from /usr/lib/libcamel-1.2.so.8
  • #3 camel_vee_folder_new
    from /usr/lib/libcamel-provider-1.2.so.8
  • #4 camel_vee_folder_remove_folder
    from /usr/lib/libcamel-provider-1.2.so.8
  • #5 camel_vee_folder_new
    from /usr/lib/libcamel-provider-1.2.so.8
  • #6 camel_object_unref
    from /usr/lib/libcamel-1.2.so.8
  • #7 vfolder_foreach_cb
    at mail-vfolder.c line 1155
  • #8 IA__g_hash_table_foreach
    at ghash.c line 662
  • #9 mail_vfolder_shutdown
    at mail-vfolder.c line 1166
  • #10 impl_quit
    at mail-component.c line 799
  • #11 _ORBIT_skel_small_GNOME_Evolution_Component_quit
    at Evolution-common.c line 64
  • #12 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #13 GNOME_Evolution_Component_quit
    at Evolution-stubs.c line 102
  • #14 es_run_quit
    at e-shell.c line 1298
  • #15 e_shell_quit
    at e-shell.c line 1366
  • #16 e_shell_request_close_window
    at e-shell.c line 964
  • #17 window_delete_event_cb
    at e-shell.c line 356
  • #18 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #19 IA__g_closure_invoke
    at gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #22 IA__g_signal_emit
    at gsignal.c line 2241
  • #23 gtk_widget_event_internal
    at gtkwidget.c line 3901
  • #24 IA__gtk_main_do_event
    at gtkmain.c line 1379
  • #25 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #26 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #27 g_main_context_iterate
    at gmain.c line 2677
  • #28 IA__g_main_loop_run
    at gmain.c line 2881
  • #29 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #30 main
    at main.c line 615

Comment 3 maillist 2006-09-18 18:19:16 UTC
This stack trace seems to be more verbose. I'm not sure if that is good or not but here you go.

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

Memory status: size: 123166720 vsize: 0 resident: 123166720 share: 0 rss: 26284032 rss_rlim: 0
CPU usage: start_time: 1158603238 rtime: 0 utime: 217 stime: 0 cutime:202 cstime: 0 timeout: 15 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 -1232324944 (LWP 8592)]
[New Thread -1314722912 (LWP 8608)]
[New Thread -1314456672 (LWP 8607)]
[New Thread -1293952096 (LWP 8604)]
[New Thread -1258419296 (LWP 8603)]
[New Thread -1277166688 (LWP 8602)]
[New Thread -1285559392 (LWP 8599)]
[New Thread -1266812000 (LWP 8597)]
[New Thread -1250026592 (LWP 8595)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232324944 (LWP 8592))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #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 IA__g_hash_table_foreach
    at ghash.c line 662
  • #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
    at gtkmarshalers.c line 83
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #27 IA__g_signal_emit
    at gsignal.c line 2241
  • #28 gtk_widget_event_internal
    at gtkwidget.c line 3901
  • #29 IA__gtk_main_do_event
    at gtkmain.c line 1379
  • #30 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #31 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #32 g_main_context_iterate
    at gmain.c line 2677
  • #33 IA__g_main_loop_run
    at gmain.c line 2881
  • #34 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #35 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 4 Karsten Bräckelmann 2006-09-18 19:50:17 UTC
Thanks for the fast response and the debugging symbols. :)

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 ***
Comment 5 Karsten Bräckelmann 2006-09-18 19:57:13 UTC
Also...

(In reply to comment #3)
> This stack trace seems to be more verbose. I'm not sure if that is good or not
> but here you go.

Yes, that stacktrace was perfect. :)  Thanks again.


Just a note, since I am suffering from that crash myself for quite a while already:  This crash is pretty harmless. The only data that may get lost is meta data in the IMAP case -- like read/unread status and such. However, there is an easy workaround for this. Since this data is synced to the server on leaving the folder, one can easily and effectively prevent any (meta) data loss at all by simply "switching forth and back". Actally, just switching the mail folder once before closing Evo will do. HTH