Thanks! From a quick glance, Orca isn't frozen. Orca is still getting and processing accessibility events even after that error. But it's getting those events from defunct accessible objects, objects with ROLE_INVALID, etc.
I'll take a longer look next week and handle the currently-unhandled error. But the problem may persist. Orca cannot bring defunct/invalid objects back from the dead; it can only try to gracefully step around their bodies. Thus getting to the bottom of the Synaptic and/or AT-SPI2 issues needs to occur. I'd be curious to know what happens if, when the Synaptic issue occurs, you Alt+Tab into another accessible application. Does Orca present your interactions with that app? Thanks again! --joanie On 04/22/2017 03:25 PM, Paul Gevers wrote: > Resending with Thunderbird mail.strictly_mime set to true, because your > host refused my message. I hope this one reaches you. Reply-To set to > the bug. > > Paul > > > -------- Forwarded Message -------- > Subject: Re: Bug#859262: Re: freezes Orca screen reader > Date: Sat, 22 Apr 2017 21:07:08 +0200 > From: Paul Gevers <elb...@debian.org> > To: Joanmarie Diggs <jdi...@igalia.com>, 859...@bugs.debian.org > > Hi Joanmarie, > > On 19-04-17 22:35, Joanmarie Diggs wrote: >> Please send me a full debug.out, captured from Orca master or Orca >> 3.24.x (i.e. current stable). Instructions here: >> https://wiki.gnome.org/Projects/Orca/Debugging > > I hope the attached log contains enough information for you to work it out. > > Mind you, my Orca setup isn't speaking (as can be seen from the top of > the log), but I think it captures the same error as reported in this bug > already. > > I created a Debian package for the 3.24 version which I build on > debomatic¹ for this purpose. > > Paul > > ¹ > http://debomatic-amd64.debian.net/distribution#unstable/gnome-orca/3.24.0-1 >
