Ok, I don't see a way around this either now. I'll try something like: if is-auto-starting and is-gnome-shell then fail, basically a working replacement for "NotShowIn=GNOME;". Manually starting Onboard will then stay possible, no matter the system state.
What about X-GNOME-AutoRestart=true, is there a clean way to opt out of restarting at termination? I can see rate limiting in the gnome-session source, but must have missed a clear way to end restarts. > Maybe the GNOME developers would consider allowing alternate > screen keyboards since their built-in keyboard is very lacking. Getting GMOME to support alternative osks may not be easy. As I understand it, the Activities view is inaccessible to portable keyboards, so only shell extensions can fully replace the built-in keyboard. It's either GNOME Shell only or the rest of the world. That's a sad state of affairs IMO, and it isn't only an obstacle for Onboard, but hurts a whole eco-system of brilliant input devices like Dasher and Cellwriter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879942 Title: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/879942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
