That segfault is an AT-SPI2 bug. And apparently an elusive one. https://bugzilla.gnome.org/show_bug.cgi?id=767074
On 04/23/2017 04:46 AM, Paul Gevers wrote: > Hi Joanmarie, > > Yesterday, I send you a log while Synaptic had not much to do, because I > ran it earlier the same day (so maybe the original issue wasn't there). > Today I tried again, hoping that there were updates to apply, which > there were. orca segfaulted on me. Please see the attached stack trace. > Maybe it tells more than the one of yesterday. > > paul@testavoira ~/tmp $ orca > /usr/lib/python3/dist-packages/pyatspi/Accessibility.py:184: Warning: > g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Atspi.Event.host_application = property(fget=lambda x: > x.source.get_application()) > Segmentation fault > paul@testavoira ~/tmp $ > > For people normally running orca, would it get automatically restarted, > such that it would appear to hang, will in reality it was restarting? Or > is it more likely I experienced another bug, maybe related to debugging? > Or maybe the behavior is slightly different between the Debian version > and my (newer) version of orca. > > Paul >
