PineTab2 virtual keyboard: symbols instead of numbers

[clemfandango]

Hello! I'm having a bug with the PineTab2 virtual keyboard (Maliit) with two different Flathub packages (ungoogled-chromium and Xlog).

When I press a number with the virtual keyboard, the "shift" version of that number is actually entered into the UI. For example, when pressing 3, # is entered, or 4, $ is entered, etc.

I've left the state of the PineTab2 largely unchanged since receiving it — no major OS changes, etc.

Is anyone else able to reproduce this? If yes, where's the correct place to report this bug? Thanks!

[docfufu]

I have the same problem with the vitual keyboard

[Surehand53]

Hello! I'm having a bug with the PineTab2 virtual keyboard (Maliit) with two different Flathub packages (ungoogled-chromium and Xlog).

When I press a number with the virtual keyboard, the "shift" version of that number is actually entered into the UI. For example, when pressing 3, # is entered, or 4, $ is entered, etc.

I've left the state of the PineTab2 largely unchanged since receiving it — no major OS changes, etc.

Is anyone else able to reproduce this? If yes, where's the correct place to report this bug? Thanks!

I have the same for Firefox. Installed with pacman, not flatpak. Also I am using Plasma Mobile, not sure if that is relevant.

[Surehand53]

Hello! I'm having a bug with the PineTab2 virtual keyboard (Maliit) with two different Flathub packages (ungoogled-chromium and Xlog).

When I press a number with the virtual keyboard, the "shift" version of that number is actually entered into the UI. For example, when pressing 3, # is entered, or 4, $ is entered, etc.

I've left the state of the PineTab2 largely unchanged since receiving it — no major OS changes, etc.

Is anyone else able to reproduce this? If yes, where's the correct place to report this bug? Thanks!

I have the same for Firefox. Installed with pacman, not flatpak. Also I am using Plasma Mobile, not sure if that is relevant.

I have the suspicion now that it might be that the affected apps run X11 instead of Wayland?

i have set one parameter to start Firefox in Wayland mode and the keyboard issue as well some other niggles disappeared. Still no idea how to fix the other apps, but it might be worth investigating.

[docfufu]

Hello! I'm having a bug with the PineTab2 virtual keyboard (Maliit) with two different Flathub packages (ungoogled-chromium and Xlog).

When I press a number with the virtual keyboard, the "shift" version of that number is actually entered into the UI. For example, when pressing 3, # is entered, or 4, $ is entered, etc.

I've left the state of the PineTab2 largely unchanged since receiving it — no major OS changes, etc.

Is anyone else able to reproduce this? If yes, where's the correct place to report this bug? Thanks!

I have the same for Firefox. Installed with pacman, not flatpak. Also I am using Plasma Mobile, not sure if that is relevant.

I have the suspicion now that it might be that the affected apps run X11 instead of Wayland?

i have set one parameter to start Firefox in Wayland mode and the keyboard issue as well some other niggles disappeared. Still no idea how to fix the other apps, but it might be worth investigating.

Great information, switched chromium and Firefox to Wayland mode and and it worked like a charm

[mtomaschett]

I am using Brave browser; Wayland flag worked great for a while. Problem seems to be back with Brave v1.52.130.

Suggestions?