https://bugs.kde.org/show_bug.cgi?id=509613
--- Comment #5 from Joshua Goins <[email protected]> --- > OK, I still don't completely understand. I hope you don't mind my continuing > to ask questions here - with the fragmentation of Wayland vs Xorg and > different Wayland compositors and the various drivers (libinput, proprietary, > OTD, digimend, ...) it's hard to find anyone with a similar setup. Let me > know if you're happier to talk elsewhere. No I'm totally fine with you asking questions in here! Actually, it may be better than a chatroom because these bug reports are public and more easily searchable :-) > To see if I can follow this Huion tool route, it would be useful to know more > precisely what it should actually change. In `libinput list-devices`, the > name of the device is suffixed with "Keyboard" but I assume this is just a > name. The capabilities are listed as "keyboard, pointer" - is it this > presentation from libinput that we are looking for, or something else? Correct, the name is made up by somebody (probably libinput?) and indeed it's the representation that has to change in order for our KCM to work. But libinput's capability field is *descriptive* not *prescriptive*, this is where my knowledge gets fuzzier - as libinput is quite complex - but the one who is actually in charge of determining what is a tablet pad vs a keyboard is actually udev. For example, I had to fix a bug where my tablet pad was erroneously being assigned as a joystick, however in your case there is no bug - for all intents and purposes it *is* a keyboard. (I'm assuming there is also keybinds for CTRL+Z and whatever.) > I am also trying to find somewhere to get information about the dials (which > are not even recognised by libinput) so while I'm abusing the issue tracker, > if you know somewhere good to discuss that, let me know... We do have complete support for dials, I added that in libinput. You won't be able to configure them until Plasma 6.5, and with your up-to-date Fedora install it should be recent enough to detect them in libinput list-devices. However the reason why they don't show up is the same reason as your tablet pad: it's probably in some "compatibility mode" where instead of regular dial events it's pretending to be a keyboard or something. If you try "libinput debug-events" what do they emit? -- You are receiving this mail because: You are watching all bug changes.
