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
Hi Cobra,
On 22-04-17 21:26, Cobra wrote:
> On 2017-04-22 19:51, Paul Gevers wrote:
>> On 22-04-17 00:26, Cobra wrote:
>>> The directories are different when starting at boot:
>> This doesn't sound good. I think it shouldn't matter how you call an
>> init-script, it should behave the same. I guess
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 o
[CC-ing tts-project@l.a.d.o as they are the maintainer of
speech-dispatcher; although I believe most contributers there also read
d-a11n.]
On 22-04-17 00:26, Cobra wrote:
> Looks like we're chasing a pulseaudio<->speech-dispatcher bug now. Fun.
I concluded the same based on my logs. Although ther
4 matches
Mail list logo
