Numpad/NumLock not working on Whonix 18.1.4.2 (LXQt)

VirtualBox
1

Hi there!

I’m experiencing an issue where my Numpad is not working on Whonix 18.1.4.2 (LXQt version). I am using a Portuguese (Brazil) ABNT2 keyboard layout.

When I try to configure it via “Keyboard and Mouse” settings, I get the message: “LXQt input settings are currently unsupported under Wayland”.

I have already tried adding numlockx on & to my ~/.config/labwc/autostart, but it didn’t work (likely due to the Wayland/Labwc transition). The Numpad works perfectly fine on Whonix 17 (XFCE) with the same VirtualBox settings.

Is there a specific way to force NumLock on at startup for Labwc in this version?

Thanks!

1 Like
2

LXQt’s input device settings currently don’t work under Wayland unfortunately. However, you can configure input device settings using labwc’s configuration file. See:

Search for ‘numlock’ to find the setting you’re looking for. The labwc configuration file should be placed at ~/.config/labwc/rc.xml (you will likely need to create the ~/.config/labwc directory, then save the file within it). A config file that will probably work is:

<?xml version="1.0"?>
<labwc_config>
  <keyboard>
    <numlock>on</numlock>
  </keyboard>
</labwc_config>
4 Likes
3

I find that sometimes my numpad does not work, but usually it does work. It might be an upstream virtualbox issue.

2 Likes
4

I couldnt reproduce the issue on my end but i have documented the steps in case its useful:

@rogmen if you can report back your experience that would be great.

3 Likes
5

Hi. Thanks for the reply, but it is still not working.

I have noticed a very specific behavior: The numeric keypad works perfectly in Whonix-Gateway-LXQt, but it rarely works in Whonix-Workstation-LXQt.

Special characters like áéíóú, àèìòù, âêîôû, ãẽĩõũ on the BR-ABNT2 layout are working fine. Mathematical symbols around the numpad ( / * - + ) also work as expected.

However, the numbers (0-9) on the numpad do not work at all in the Workstation, regardless of whether NumLock is ON or OFF. It seems the compositor or the input handler is not registering the numerical input from those specific keys, even though the same hardware and layout configuration work fine on the Gateway.

Has anyone experienced this discrepancy between the two VMs?

1 Like