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 410952 - crash in Evolution: Just deleting some messa...
crash in Evolution: Just deleting some messa...
Status: RESOLVED DUPLICATE of bug 330728
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-02-22 20:21 UTC by Duncan Lithgow
Modified: 2007-02-23 05:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Duncan Lithgow 2007-02-22 20:21:50 UTC
What were you doing when the application crashed?
Just deleting some messages from my inbox - maybe I deleted something before the message list was regenerated?


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

Memory status: size: 131379200 vsize: 0 resident: 131379200 share: 0 rss: 38211584 rss_rlim: 0
CPU usage: start_time: 1172175113 rtime: 0 utime: 3450 stime: 0 cutime:3223 cstime: 0 timeout: 227 it_real_value: 0 frequency: 459

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 -1232447824 (LWP 6110)]
[New Thread -1315607648 (LWP 6401)]
[New Thread -1303229536 (LWP 6130)]
[New Thread -1293800544 (LWP 6125)]
[New Thread -1285407840 (LWP 6124)]
[New Thread -1256539232 (LWP 6123)]
[New Thread -1266680928 (LWP 6120)]
[New Thread -1248146528 (LWP 6118)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232447824 (LWP 6110))

  • #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 ect_check
    at gal-a11y-e-cell-text.c line 69
  • #6 ect_get_name
    at gal-a11y-e-cell-text.c line 81
  • #7 atk_object_get_name
    from /usr/lib/libatk-1.0.so.0
  • #8 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #9 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2406
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #12 IA__g_signal_emit
    at gsignal.c line 2243
  • #13 atk_object_notify_state_change
    from /usr/lib/libatk-1.0.so.0
  • #14 gal_a11y_e_cell_remove_state
    at gal-a11y-e-cell.c line 525
  • #15 ectr_model_row_changed_cb
    at gal-a11y-e-cell-tree.c line 48
  • #16 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #17 IA__g_closure_invoke
    at gclosure.c line 490
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #20 IA__g_signal_emit
    at gsignal.c line 2243
  • #21 e_table_model_row_changed
    at e-table-model.c line 487
  • #22 e_tree_table_adapter_node_set_expanded
    at e-tree-table-adapter.c line 1117
  • #23 e_tree_table_adapter_load_expanded_state
    at e-tree-table-adapter.c line 1053
  • #24 e_tree_load_expanded_state
    at e-tree.c line 2010
  • #25 regen_list_regened
    at message-list.c line 1691
  • #26 mail_msgport_replied
    at mail-mt.c line 461
  • #27 g_io_unix_dispatch
    at giounix.c line 162
  • #28 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #29 g_main_context_iterate
    at gmain.c line 2677
  • #30 IA__g_main_loop_run
    at gmain.c line 2881
  • #31 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #32 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 James Olds 2007-02-23 05:28:43 UTC
Thanks for the bug report. It looks like 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 330728 ***