subscribe seb128 We need to get this working for final release, so I think the best way forward is as follows:
1. Revert 5debed5ae247c1dd440cb71d0a6d328df74b0844 in the gtk+3.0 package. This will work around the problem by not shutting down accessibility at all for GTK, which was how things were for most of this cycle prior to this commit being made upstream. Shutting down accessibility is the right thing to do long term, as it cleans up unused sockets and connections, but reverting this commit won't break anything either. 2. Once upstream has worked out a proper solution to this problem, we can drop the revert, and pull the upstream fix and SRU it. I have subscribed Sebastien to get his thoughts on whether this is reasonable. If he gives the go ahead, I'll take care of the first step of the above prior to final freeze. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056300 Title: If a GTK application quits the main loop and restarts it again, accessibility is lost. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1056300/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
