On 04/29/2017 10:55 AM, Paul Gevers wrote:
> And to prepare for fixes of the package in Debian (which is 3.22.2 and
> will be extremely hard convince the release managers to update in this
> stage due to the freeze), which fixes would we need to backport to fix
> the issues identified so far?
---------
commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7
Author: Joanmarie Diggs <jdi...@igalia.com>
Date: Sat Apr 29 11:38:17 2017 -0400
Handle yet another Atspi "The process appears to be hung" exception
commit 382c5408afc7dd25f9b477a5e30c50ba917155c0
Author: Joanmarie Diggs <jdi...@igalia.com>
Date: Sat Apr 29 11:28:17 2017 -0400
Add check for dead accessibles before attempting to generate
presentation
commit d51f87a7f000d099da98247dc7ca337b2b5483be
Author: Joanmarie Diggs <jdi...@igalia.com>
Date: Fri Apr 28 15:35:39 2017 -0400
Handle another Atspi "The process appears to be hung" exception
commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6
Author: Joanmarie Diggs <jdi...@igalia.com>
Date: Thu Apr 27 06:35:11 2017 -0400
Return immediately in isLayoutOnly() if obj is dead
---------
Note that 382c540 may need to be reverted. Hopefully not. But rather
than playing endless whac-a-mole with Atspi errors resulting from
whatever it is Synaptic is doing, I am sanity checking much earlier on
in the process. There is the possibility that doing so will cause other
badly-behaved apps to not be presented. :-/
I've asked on the Orca list for testing, and we have enough users that
use master and respond quite quickly to calls for testing, that we
should know soon enough.
I believe I've already said this, but I'll say it again: Getting to the
bottom of the Synaptic and/or AT-SPI problem(s) should be done.
(Something I'm afraid I don't have time for. Sorry!)
--joanie
