2 instances of onboard onscreen keyboard running and settings only applying to one
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| onboard (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I installed Ubuntu 18.04 Bionic Beaver development branch
Onboard 1.4.1-2ubuntu1
An onscreen keyboard comes installed by default, but it's not very usable
* Lack of buttons https:/
* Pipe doesn't work https:/
* Uppercase is broken https:/
I tried changing the settings for the onscreen keyboard, selecting the "Full" layout (instead of "Compact"), but found the settings did not take effect even after a reboot.
https:/
Then I ran onboard from the launcher, and the full keyboard appeared at the bottom of the screen *constantly* and resized the rest of my screen smaller.
With the full layout, uppercase works, and so far it seems fine.
However now whenever I click on any window that has a text input, the buggy compact onscreen keyboard appears over the working full layout onscreen keyboard.
I actually like the behavior of the buggy compact onscreen keyboard's ability to show/hide as needed vs the full "onboard" keyboard displaying constantly.
So right now it's a bit of a mess, sorry if I should have reported each issue as part of a single bug report.
Desired outcome:
1. The automatically displayed keyboard should respect the settings (eg: the layout) set by onboard-settings.
2. If I run onboard manually, meaning it stays at the bottom of the screen constantly, another instance should not automatically pop up over it.
| Francesco Fumanti (frafu) wrote | #1 |
The main problem is that Onboard was not designed to work with GNOME3, that has restrictions, that Onboard can hardly bypass. (Onboard is also incompatible to Wayland, which is an additional issue.) There is a gnome extension for Onboard that slightly improves the situation, but a proper compatibility with GNOME 3 requires Onboard to be rewritten, having the restrictions of GNOME 3 in mind. A rewrite of Onboard started some time ago under the name of OnboardOSK; but I don't know what state OnboardOSK is in.