| Summary: | Stylus Mapping Not Able to Be Changed | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | theawkwarddreamer |
| Component: | kcm_tablet | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | aleixpol, josh |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Output of libinput list-devices as well as output from multiple libinput record | ||
|
Description
theawkwarddreamer
2025-11-24 21:49:20 UTC
Marking as duplicate as this may be related to a bug on our side. *** This bug has been marked as a duplicate of bug 508084 *** Crossposting from the other bug as I've found new information and it appears that my issue is not a duplicate of the other bug, so I'm moving relevant information here. I'm just hesitant to change the status myself as I'm not a developer and unsure of the etiquette. I attempted to change settings in `.config/kcminputrc` as a workaround while I wait for other possible fixes to end up on my machine, but even remapping supposedly every button on my stylus to right click does absolutely nothing. Touching the stylus to the screen is still left click. The side button is still middle click. Eraser erases. I have the following in my kcminputrc: [ButtonRebinds][TabletTool][ILIT2901:00 222A:5539 Stylus] 320=MouseButton,273 321=MouseButton,273 331=MouseButton,273 332=MouseButton,273 I assume that's the correct device as the header was created by me changing one of the GUI bindings to right click and then modifying the 0 to 331 in the file. Another update: ktabletconfig can now see my stylus, but states all the buttons are mapped to 273 like the kcminputrc file. I've ended up just remapping right click to middle click, which did work. I really wonder if it's something with styluses and 2-in-1s that cause the issue. OpenTabletDriver seems to be of no use to me at all as it seems to want an attached tablet to do anything. Will be going into their support discord to look more into this. |