this post was submitted on 30 Mar 2024
36 points (97.4% liked)

Linux

48323 readers
722 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Any virtual keyboard / on-screen keyboard recommendations for Gnome (Wayland) users? The default one doesn't support X11/XWayland apps, which unfortunately is most of them...

you are viewing a single comment's thread
view the rest of the comments
[–] astro_ray@lemdro.id 1 points 7 months ago (1 children)

Not just X11 apps, it doesn't work properly even in webapps.

Well, there's not really many good alternative, but used to use Onboard which has some good features. You can give that a try.

[–] gwendolencopper@kbin.social 2 points 7 months ago* (last edited 7 months ago)

@astro_ray

If you're talking about running web-apps in the browser, I found that using environment variable MOZ_USE_XINPUT2=1 solves some of my virtual keyboard issues in Firefox (update I just tried disabling the variable and it works the same...maybe it was just placebo...). For example, if you wanted to run the Librewolf flatpak you can do flatpak run --env=MOZ_USE_XINPUT2=1 io.gitlab.librewolf-community or to set the variable permanently you can do flatpak override --user --env=MOZ_USE_XINPUT2=1 io.gitlab.librewolf-community and then Librewolf will always launch with that option.

As for Chromium forks, they don't use Wayland yet so that just goes back to the X11 / XWayland issues. Same goes for Electron apps. At least from what I understand from https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6238. Maybe there's a way to force Chromium/Electron to use Wayland, I haven't tried it yet

And I'll try Onboard, thanks for the tip

Update: I tried onboard, and it also didn't work for X11 apps :(