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 631928 - Evolution SEGV in ect_check()
Evolution SEGV in ect_check()
Status: RESOLVED DUPLICATE of bug 330728
Product: evolution
Classification: Applications
Component: general
3.0.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-10-11 22:35 UTC by David Woodhouse
Modified: 2013-09-13 01:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Woodhouse 2010-10-11 22:35:33 UTC 
==12158== Process terminating with default action of signal 11 (SIGSEGV)
==12158==  Access not within mapped region at address 0x6E69616C70
==12158==    at 0x5730E95: ect_check (gal-a11y-e-cell-text.c:83)
==12158==    by 0x573197D: ect_get_name (gal-a11y-e-cell-text.c:95)
==12158==    by 0xE51BDBD: ??? (in /usr/lib64/gtk-2.0/modules/at-spi-corba/modules/libatk-bridge.so)
==12158==    by 0xE51BEBF: ??? (in /usr/lib64/gtk-2.0/modules/at-spi-corba/modules/libatk-bridge.so)
==12158==    by 0xE51C7E3: ??? (in /usr/lib64/gtk-2.0/modules/at-spi-corba/modules/libatk-bridge.so)
==12158==    by 0x319FC14748: atk_focus_tracker_notify (atkutil.c:200)
==12158==    by 0xE2D01BB: gail_focus_idle_handler (gail.c:589)
==12158==    by 0x3F6D81E1A5: gdk_threads_dispatch (gdk.c:512)
==12158==    by 0x3197841E32: g_main_context_dispatch (gmain.c:2149)
==12158==    by 0x319784260F: g_main_context_iterate.clone.5 (gmain.c:2780)
==12158==    by 0x3197842C81: g_main_loop_run (gmain.c:2988)
==12158==    by 0x3F6D14B0B6: gtk_main (gtkmain.c:1237)
==12158==    by 0x4032A4: main (main.c:677)
Comment 1 Matthew Barnes 2010-10-12 00:11:35 UTC 
I am very close to just ripping out our broken and unmaintained ETable accessibility support.

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