GNOME Bugzilla – Bug 643526
[regression] Crash in et_get_n_children
Last modified: 2013-09-13 01:10:40 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.
+ Trace 226140
Thread 1 (Thread 22682)
I just tried evolution -c calendar. I get the same crash. With -c mail it starts.
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).
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.
OK, but there doesnt seem to be a configure flag for that.
very strange. I restarted gnome and now the problem seems to have gone away.
(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.
given the state of gnome-3, I couldn't find the setting, besides I'm pretty sure that I never had accessibility running.
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.
Created commit 8f01d97 in evo master (3.1.2+) Created commit 8b7bfa4 in evo gnome-3-0 (3.0.3+)
*** Bug 648492 has been marked as a duplicate of this bug. ***
*** Bug 653059 has been marked as a duplicate of this bug. ***
*** Bug 657110 has been marked as a duplicate of this bug. ***