Reverting GTK commit 5debed5ae247c1dd440cb71d0a6d328df74b0844 makes the problem go away, but I can't say whether this is a GTK bug until I know what ubiquity is doing between steps/pages. That commit adds
functionality to GTK to properly shut down accessibility when a window is closed, but ubiquity's window doesn't close, which makes me wonder why reverting that commit makes the problem go away...
Reverting GTK commit 5debed5ae247c1d d440cb71d0a6d32 8df74b0844 makes the problem go away, but I can't say whether this is a GTK bug until I know what ubiquity is doing between steps/pages. That commit adds
functionality to GTK to properly shut down accessibility when a window is closed, but ubiquity's window doesn't close, which makes me wonder why reverting that commit makes the problem go away...