Fresh Install of Ubuntu mate 24.04 LTS. After starting the Onboard keyboard, the "Onboard Keyboard icon indicator" will appear in the panel indicating that the program has started and currently running. Virtual Keyboard will appear but when I move the mouse cursor over to the Virtual Keyboard or the "Onboard Keyboard icon indicator", the whole program will disappear. No error message.
I tried to boot into USB "ISO Live Session", the same crash happens.
In the previous Ubuntu Mate 22.04 LTS, this was working fine.
I believe you're right! In an Ubuntu MATE 24.04 LTS ("Noble Numbat") VirtualBox VM, I activated the "On-Screen Keyboard" (available either in the "Ubuntu MATE Menu" -> "Universal Access" -> "Onboard" or by clicking om the accessibility icon in the task bar and by then sliding, to the right, the "slider" for the "On-Screen Keyboard" option). The on-screen keyboard then appeared on the screen but, when I mouse clicked on any key in that virtual keyboard, it disappeared. In my case, it did generate a ".crash" file named _usr_bin_onboard.1000.crash located in the /var/crash directory.
You may want to click on the "This bug affects 2 people. Does this bug affect you?" link in that Launchpad bug web page (to add yourself to the list of affected users by that bug) and you may also want to add a comment in that page to report your experience about this bug.
On a related note: a few minutes ago, in that same bug web page in Launchpad, I've clicked on the link to add myself as one of the affected people and that had the result of changing the bug status: "Status changed to 'Confirmed' because the bug affects multiple users."
How do we remove the OSKBD while we wait? It is making my screen blink when the mouse goes down the screen from time to time.
I use it very often on my TV from a distance.
I think that disabling the onscreen keyboard ("onboard") - instead of removing it - will be enough. To disable the on-screen keyboard, in Ubuntu MATE 24.04 LTS ("Noble Numbat"), please do the following:
1 - Using your mouse, (left) click on the accessibility icon (the icon of a white figure of a man in blue background) that is located on the taskbar, near the upper right corner of the screen, to bring up the accessibility context menu, as I show in the following screenshot:
2 - In that accessibility context menu, click on the left part of the"On-Screen Keyboard" slider to disable it, so it then looks like this:
3 - Click on an "empty" part of the desktop to hide the accessibility context menu.
Guys! I think I solved it! I was struggling with it a lot and suddenly it is fixed for me now.
just go to menu>preferences>onboard settings
and from there (keyboard must be selected from left pane) go to advanced and change "input event source" from Xinput to GTK.
I've had trouble using Onboard with my Lenovo Ideapad Flex 3 2-in-1 laptop with UM 22.04. Onboard would pop up if the focus was on a text entry widget, but I couldn't use it to type anything. Danial_Sooozani's suggestion about changing "Input event source" from Xinput to GTK fixed that. Thank you, Danial.
However, Onboard didn't stay fixed very long. I could type a few letters with it and then Onboard would lock up. Sometimes it would freeze with a key
depressed, causing an endless repeating stream of that key. And this happened whether I clicked on Onboard's keys with either a bluetooth mouse or the touchscreen.
Since then I've been fiddling with the Onboard settings and this morning I found that the freezing up problem appears to be solved by changing the Keyboard / Advanced / Input Options / Touch input setting from "single touch" to "none". I know it seems as if that would prevent using the touchscreen or touchpad to operate the on-screen keyboard, but it doesn't. I can use a bluetooth mouse, the touchpad, or the touchscreen, and Onboard is now working without freezing up. (And I have no clue why that setting would prevent Onboard from freezing up when using a mouse to press the keys.)
Perhaps one of you with UM 24.04 installed can try changing this setting to see if that fixes your freezing problem. It's worth a try.
FWIW - when I went to use this applet, ayatana-indicator-a11y also crashed (SIGTRAP - which is quite interesting as that suggests some kind of deadlock).
