We could set 'toolkit-accessibility' silently in Onboard's startup, but that should be the last option. I'd prefer not to fight with gnome- settings-daemon over that key. It would still be an incomplete solution, since 'screen-keyboard-enabled' can be reset any time afterwards, taking down a11y for new processes with it.
Setting 'screen-keyboard-enabled'=true in your script when entering tablet mode would get rid of the dialog, but some processes started before tablet mode might still be invisible to Onboard, firefox in particular. You'd have to restart them after switching to get auto-show and word suggestions working. The only real solution I see is keeping 'toolkit-accessibility' enabled at all times, i.e. not letting g-s-d turn it off. Either by patching gsd-a11y-settings-manager.c, or by deactivating the a11y-settings plugin. Try this: gsettings set org.gnome.settings-daemon.plugins.a11y-settings active false You have to do this only once, and looking through the source, there seems little harm for your custom setup in disabling the plugin. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1227173 Title: On every startup Onboard asks for enabling accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
