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 643526 - [regression] Crash in et_get_n_children
[regression] Crash in et_get_n_children
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Contacts
3.0.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Milan Crha
Evolution QA team
: 648492 653059 657110 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-02-28 21:10 UTC by David Ronis
Modified: 2013-09-13 01:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
evo patch (2.42 KB, patch)
2011-06-06 13:51 UTC, Milan Crha
committed Details | Review

Description David Ronis 2011-02-28 21:10:53 UTC
I'm trying out gnome-2.91.90 with evolution and friends' git-master.   I've been using the mailer for most of the day, but just switched to my contacts.   Evo crashes, without bugbuddy poping up.

There is a core file and here's the backtrace:


Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

Thread 1 (Thread 22682)

  • #0 et_get_n_children
    at gal-a11y-e-table.c line 132
  • #1 atk_object_get_n_accessible_children
    at atkobject.c line 774
  • #2 append_children
    at ../../atk-adaptor/accessible-cache.c line 225
  • #3 add_pending_items
    at ../../atk-adaptor/accessible-cache.c line 280
  • #4 g_idle_dispatch
    at gmain.c line 4537
  • #5 g_main_dispatch
    at gmain.c line 2440
  • #6 g_main_context_dispatch
    at gmain.c line 3013
  • #7 g_main_context_iterate
    at gmain.c line 3091
  • #8 g_main_loop_run
    at gmain.c line 3299
  • #9 gtk_main
    at gtkmain.c line 1349
  • #10 main
    at main.c line 734

Comment 1 David Ronis 2011-02-28 21:13:15 UTC
I just tried evolution -c calendar.  I get the same crash.   With -c mail it starts.
Comment 2 David Ronis 2011-02-28 21:16:29 UTC
One more thing.  I'm running today's git master here.  At home, I was running yestereday's git master and I'm pretty sure that this didn't happen (at least for the calendar).
Comment 3 Matthew Barnes 2011-02-28 21:36:41 UTC
Accessibility is known to be horribly broken under GNOME 3.  I don't know the details, that's just from what I've overheard on #fedora-desktop and gtk-devel-list.  Best disable it.
Comment 4 David Ronis 2011-02-28 22:02:22 UTC
OK, but there doesnt seem to be a configure flag for that.
Comment 5 David Ronis 2011-02-28 22:06:49 UTC
very strange.  I restarted gnome and now the problem seems to have gone away.
Comment 6 Milan Crha 2011-03-01 08:17:19 UTC
(In reply to comment #5)
> very strange.  I restarted gnome and now the problem seems to have gone away.

Might be just a coincidence, or you successfully disabled the accessibility in your system settings.
Comment 7 David Ronis 2011-03-01 15:55:33 UTC
given the state of gnome-3, I couldn't find the setting, besides I'm pretty sure that I never had accessibility running.
Comment 8 Milan Crha 2011-06-06 13:51:54 UTC
Created attachment 189324 [details] [review]
evo patch

for evolution;

I managed to reproduce this crash in calendar finally, under Gnome 3. This patch fixes the issue, by two steps:
a) set the widget to gtk accessibility object, as there was set none
b) do not crash even when there is no widget set

The patch also fixes couple more runtime warnings, those many from eti_get_accessible still left - I do not know how to fix them.

Anyway, the thing is that evolution doesn't crash like this anymore.
Comment 9 Milan Crha 2011-06-06 13:55:49 UTC
Created commit 8f01d97 in evo master (3.1.2+)
Created commit 8b7bfa4 in evo gnome-3-0 (3.0.3+)
Comment 10 Milan Crha 2011-06-29 12:14:48 UTC
*** Bug 648492 has been marked as a duplicate of this bug. ***
Comment 11 Milan Crha 2011-08-24 11:50:52 UTC
*** Bug 653059 has been marked as a duplicate of this bug. ***
Comment 12 Milan Crha 2011-09-06 17:16:19 UTC
*** Bug 657110 has been marked as a duplicate of this bug. ***