GPD Win Mini keyboard keys in Mousemode not functional in 75.2-1

[Hyatice]

Hi!

I ran some updates to my Nobara install yesterday and afterward any keyboard buttons for mousemode stopped working. Still functional in the BIOS/Windows, but not in the OS.

After some tinkering, I found that downgrading inputplumber to 0.71.0-4.fc43 fixes the issue.

If I stop the inputplumber service with 75.2-1.fc43 installed, everything works (but it won't show up in inputremapper at that point - Though fwiw this issue happened even with inputremapper's service stopped.)

Thanks for your attention!

[pastaq]

The most recent changes to the win mini was #510.

@justinweiss do you mind helping figure out what's going on?

[justinweiss]

Oh! There's a switch on the back of the device that swaps between "gamepad" and "mouse" mode. In mouse mode, the gamepad controls send WASD / arrows and the right stick is a virtual mouse. I didn't even think about that, I don't think I've ever flipped that switch before.

It looks like this clause is probably blocking those keyboard events:

InputPlumber/rootfs/usr/share/inputplumber/devices/50-gpd_winmini.yaml

Lines 35 to 40 in 4edffae

	- group: keyboard
	blocked: true
	evdev:
	name: " Mouse for Windows"
	phys_path: usb-0000:63:00.3-3/input1
	handler: event*

I think I blocked it because it's the same device as the hidraw section above it (which we use in inputplumber to detect and debounce the L4/R4 buttons) and didn't want duplicate events. Is there a good way around that, so we can have both the hidraw and event* cooperate?

@Hyatice if you remove lines 30-40 from that file (these ones):

InputPlumber/rootfs/usr/share/inputplumber/devices/50-gpd_winmini.yaml

Lines 30 to 40 in 4edffae

	- group: keyboard
	hidraw:
	vendor_id: 0x2f24
	product_id: 0x0135
	interface_num: 1
	- group: keyboard
	blocked: true
	evdev:
	name: " Mouse for Windows"
	phys_path: usb-0000:63:00.3-3/input1
	handler: event*

and put it into /etc/inputplumber/devices/50-gpd_winmini.yaml, does it fix the problem? (you might also just be able to remove that blocked: line)

[Hyatice]

@justinweiss sorry for the really late reply on this, I removed the blocked: true line and restarted the service and can confirm it now works.

[pastaq]

@justinweiss we can add filtered events to that device and remove the blocked line to fix this