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 426902 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 349493
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-04-06 12:36 UTC by gutocarvalho
Modified: 2007-04-07 10:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description gutocarvalho 2007-04-06 12:36:04 UTC
What were you doing when the application crashed?



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

Memory status: size: 208326656 vsize: 0 resident: 208326656 share: 0 rss: 47095808 rss_rlim: 0
CPU usage: start_time: 1175812691 rtime: 0 utime: 8867 stime: 0 cutime:8426 cstime: 0 timeout: 441 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 -1233353040 (LWP 5649)]
[New Thread -1284437088 (LWP 6398)]
[New Thread -1301623904 (LWP 5668)]
[New Thread -1344107616 (LWP 5667)]
[New Thread -1268016224 (LWP 5666)]
[New Thread -1335714912 (LWP 5663)]
[New Thread -1327322208 (LWP 5662)]
[New Thread -1318929504 (LWP 5661)]
[New Thread -1293194336 (LWP 5657)]
[New Thread -1284801632 (LWP 5656)]
[New Thread -1259623520 (LWP 5653)]
[New Thread -1251230816 (LWP 5652)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233353040 (LWP 5649))

  • #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 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 atk_object_notify_state_change
    from /usr/lib/libatk-1.0.so.0
  • #14 gal_a11y_e_cell_add_state
    at gal-a11y-e-cell.c line 496
  • #15 ectr_model_row_changed_cb
    at gal-a11y-e-cell-tree.c line 46
  • #16 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #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 animate_expander
    at e-cell-tree.c line 447
  • #24 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #29 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-04-07 10:44:39 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 349493 ***