I've found the problem. If I'm reading Ubiquity's GTK frontend code
correctly, the main loop is shut down when the installer switches pages.
Commit 5debed5ae247c1dd440cb71d0a6d328df74b0844 introduces some extra
code to make sure accessibility is properly shut down when the mainloop
quits. The problem here is that accessibility is initialized when
gtk_init is called, so in ubiquity's case, switching installer pages
causes the main loop to quit, which shuts down accessibility, but when
the main loop is started again, there is no accessibility enabled for
ubiquity any more.
** Package changed: ubiquity (Ubuntu Quantal) => gtk+3.0 (Ubuntu
Quantal)
** Changed in: gtk+3.0 (Ubuntu Quantal)
Status: Confirmed => Triaged
** Summary changed:
- orca quits after closing the greeter with "install now" option
+ If a GTK application quits the main loop and restarts it again, accessibility
is lost.
--
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/ubuntu/+source/gtk+3.0/+bug/1056300/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
