On Screen Keyboard Zorin Os

0 views
Skip to first unread message

Paciente Flynn

unread,
Aug 5, 2024, 10:53:17 AM8/5/24
to butmoderti
Ibelieve in Gnome it is called onboard and can be launched from the Settings > accessibility screen. Of from alt+F2 keyboard shortcut and typing in onboard and hitting enter.

If this does not work, you may need to install it:


From your screenshot, it looks like your Local Region and Language is set to English (US).

I believe that this is why it is defaulting to English.

I agree, though... If your local language was set to Urdu, would the keyboard not switch to English when you need it?


I have installed Zorin 16.3 Pro. Unfortunately, the on-screen keyboard does not work. When I click in a text field, the keyboard appears, but unfortunately it does not respond to any input. I have also installed Onboard but when I click into a text field, the Gnome on-screen keyboard opens. I disabled the onscreen keyboard in the accessibility settings after I installed Onboard.

What unfortunately also does not work via touch is launching applications from the bar.

The computer is a HP Pavilion x360 Convertible 14.

What other information is needed to help me?

Peter


From your post, it sounds as though the built in on-screen keyboard is launching. However, it is not responding to Touch Screen input. Have you tested it with Mouse Input?

The issue may be a touch issue, not an on-screen keyboard issue.


from what u have said, it sounds like u are having an issue with ur touch-pad. try clicking the on-screen keyboard keys using left key or right key of ur touch-pad or if u have an external mouse u can use that.


Thank you very much for the answer. I think it is a combination of a touch problem and an on-screen keyboard problem. With the mouse the input works. That points to a touch problem. On the other hand, yes the onboard keyboard works with touch. This then points to a problem with the Gnome on-screen keyboard. I would use Onboard. But the Gnome keyboard is always displayed although it is switched off in the settings.


You would think that you could just uninstall Caribou to solve the issue. But... Gnome doesn't like that. It likes to break the Gnome shell if you remove it.

And if you do manage to remove it - it is likely to re-appear with a system update.


Is there ANY WAY to get rid of this?

image1319267 39 KB

Please help me, I am very panicked. I may lose my files again if I have to reinstall Zorin and I can do nothing else if this shows up in text windows when i am not using touchscreen. What did I break and how do I kill the OSK? (On screen keyboard)


Some apps, like Firefox (as covered in this question) don't trigger the on-screen keyboard. I have had other situations, e.g. when switching between apps and in LibreOffice (which is an X app, but like Firefox ships with Ubuntu Touch).


I just installed a fresh copy of the (currently) newest Ubuntu LTS. Because I did this on an Acer with Touchscreen capability, it decided I want an on-screen keyboard which I very much do NOT. It's constantly in the way and completely unnecessary.


I've been searching for days for a solution, but it's already off in the settings, I can't find any way to force remove it from the filesystem or otherwise make it behave. How do I deal with this nuisance? As is, there's no way the computer will work for what I need.


QUESTION: I sometimes use the existing onscreen keyboard, and it works well in landscape mode. However, when in portrait mode, there are two different versions of the screen keyboard that may appear. One is clearly more usable than the other (see pics). Is there some way to control which version appears?


After further experimentation, it appears that the preferred keyboard version can indeed be reliably summoned in portrait view by first rotating the screen to landscape view, bringing up the screen keyboard, and then going back to portrait view. After this, the preferred keyboard version reliably appears every time the keyboard is summoned. This is persistent even after the automatic screen idle timeout and password lock engages, or even if user locks the screen via the user menu on the bottom-right corner. However, it is NOT persistent after user log-out, or after poweroff/reboot.


Especially because you reproduced this on Ubuntu, it sounds like a general issue in GNOME. Maybe you can find an appropriate place to report the bug to the GNOME community in order for this to be improved in future.


All the following are likely to be common GNOME-desktop-related issues. Basically, I think 2 GB of RAM may be too little for GNOME+running apps, and this bay-trail processor too weak. Occasionally, during normal use (e.g. web browsing with Chromium or reading docs with Evince) the system can become unresponsive, freezing and then resuming after several seconds. Referring to the system-monitor after these events shows that at least one of the CPU cores had hit 100% before recovering and continuing. I doubt this is a problem with any particular application(s) but rather due to hardware limitation of this device.


Across a number of applications, the top title bar behaves inconsistently, typically with touch-unresponsive maximise button at top-right (perhaps related to point 4 above), and sometimes with unresponsive back-arrow at top-left (usually if the application window is already maximised). Unresponsive back arrow is never a problem when using a connected mouse.


Feature requests for future EndlessOS releases: In addition to addressing the major UI issues, it would be good to have more user-level customisation. Options to turn off animations or other unrequired features, etc., which could improve usability/performance on older/underpowered devices. Theming options especially for app windows: Currently, grey-and-grey is tiring on the eyes. More visual contrast would be very useful, especially for the title bar and its icons/buttons.


From a tablet user perspective, I would welcome any UI tweaks that improve touch-responsiveness and usability, and help balance the lack of a fine-pointing device with the need to preserve screen real-estate for actual content.


Is it approved for both Vision and Perspective also? Running a gateway is one thing, but the on-screen keyboard usually causes issues, or in 22.04 at one time had issues with kiosk/full-screen mode with clients not actually going full screen.


If there is an approved OS and workarounds are required for things to work properly beyond a default install, it would be nice if documentation was provided to install something or tweak a setting to get it to work.


It has been tested and approved for both Vision and Perspective to work as well as it did with 20 to an extent. Due to changes in Ubuntu that we cannot currently code around, the Desktop launcher does not work unless the entire application is installed on the Desktop of the client.


As for the touchscreen stuff, the issues surrounding that typically dealt with jxBrowser working with Perpective Workstation. We don't have the latest version of jxBrowser included because of problems getting the touchscreen keyboard to work properly with the regressions introduced in the upgraded library. With Vision, I am being told that the touchscreen keyboard is working as intended.


Hi, I am a pretty new Linux user. I am running Ubuntu Mate 18.04, on a Lenovo ThinkPad x250 laptop. Getting it up and running has generally been very smooth, but I have run into a problem with the screen going black after keyboard/mouse inactivity for about 10-15 mins (including watching video).


When the screen goes black, the computer seems to still be working (audio from video continues, and can be started/stopped pressing the space bar, and audio can be turned up and down with the relevant buttons) but I can't wake the screen by pressing the keyboard keys or moving/clicking the mouse, or by hitting the power button.


After digging in forums, I had a go at pressing the Ctrl + Alt + F1 key when the problem occurs, and this does take me into a terminal screen ok, and then I can get back safely to the GUI by pressing Ctrl + Alt + F7, so overall I won't be losing unsaved work with the problem. However, I would like to be able to control power management (and I'd really like a nice screensaver!)...


I've tried changing settings in the Screensaver and Power Management preferences in the Control Centre, but these don't seem to have any effect. I've tried lengthening the "Regard the computer as idle after" time in the screensaver panel, but this doesn't seem to make any difference, and in fact the screensaver doesn't kick in even if I set it shorter than the time that it takes for the screen to go to black... I've tried unchecking the "activate screensaver when computer is idle" and "Lock screen when screensaver is active" checkboxes. I've also made sure that the "Put display to sleep" time in Power Management is 1 hour.


Hello,

Sometimes screen saving options are turned on in BIOS/UEFI. That may unpredictably mess OS screen saving options. As the first option I would like propose to verify BIOS settings and turn off its screen/power saving options, if any.


Thanks very much for your help Gene. Strangely, after having this problem consistently for a couple of days, I don't seem to be able to replicate the symptoms, today... I'm not sure what fixed it -- just about the only thing that I did except for continued fiddling with the time periods in Screensaver and Power Management was set the screen brightness in Power Management to 100% (it was 80%), but putting it back to 80% doesn't seem to cause any problems, so it doesn't seem to be an inherent problem of the system dealing with a partially bright screen. I can only imagine that a configuration file or process had become corrupt, and that either fiddling with settings more, a couple of normal reboots, or switching between ctrl+alt+F1/F7 when the problem occurred instead of a hard shut-down cleared out the problem... I can now watch videos without the screen going blank, and if I leave the computer unattended for the period of time specified in the Screensaver settings, xscreensaver starts up fine...

3a8082e126
Reply all
Reply to author
Forward
0 new messages