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 354500 - crash in Evolution: click on a message in me...
crash in Evolution: click on a message in me...
Status: RESOLVED DUPLICATE of bug 333934
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-05 19:14 UTC by Baptiste Mille-Mathias
Modified: 2006-09-05 19:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Baptiste Mille-Mathias 2006-09-05 19:14:57 UTC 
What were you doing when the application crashed?
click on a message in messages list


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

Memory status: size: 163790848 vsize: 0 resident: 163790848 share: 0 rss: 41312256 rss_rlim: 0
CPU usage: start_time: 1157478209 rtime: 0 utime: 3937 stime: 0 cutime:3619 cstime: 0 timeout: 318 it_real_value: 0 frequency: 60

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 -1210480976 (LWP 5622)]
[New Thread -1318884448 (LWP 5678)]
[New Thread -1300268128 (LWP 5669)]
[New Thread -1291875424 (LWP 5668)]
[New Thread -1283482720 (LWP 5639)]
[New Thread -1263105120 (LWP 5634)]
[New Thread -1245828192 (LWP 5632)]
[New Thread -1237394528 (LWP 5630)]
[New Thread -1228948576 (LWP 5629)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71661

Thread 1 (Thread -1210480976 (LWP 5622))

  • #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 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 2404
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #12 IA__g_signal_emit
    at gsignal.c line 2241
  • #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 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 2438
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #20 IA__g_signal_emit
    at gsignal.c line 2241
  • #21 e_table_model_row_changed
    at e-table-model.c line 487
  • #22 etta_proxy_node_data_changed
    at e-tree-table-adapter.c line 777
  • #23 IA__g_cclosure_marshal_VOID__POINTER
    at gmarshal.c line 601
  • #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 2197
  • #27 IA__g_signal_emit
    at gsignal.c line 2241
  • #28 e_tree_model_node_data_changed
    at e-tree-model.c line 279
  • #29 main_folder_changed
    at message-list.c line 2962
  • #30 do_async_event
    at mail-mt.c line 676
  • #31 idle_async_event
    at mail-mt.c line 687
  • #32 g_idle_dispatch
    at gmain.c line 3926
  • #33 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #34 g_main_context_iterate
    at gmain.c line 2677
  • #35 IA__g_main_loop_run
    at gmain.c line 2881
  • #36 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #37 main
    at main.c line 615
  • #0 __kernel_vsyscall 






Comment 1


Baptiste Mille-Mathias





          2006-09-05 19:21:22 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 333934 ***