https://bugs.kde.org/show_bug.cgi?id=521611
--- Comment #15 from David REVOY <[email protected]> --- Hi Joshua, Yes, this bug is a duplicate of https://bugs.kde.org/show_bug.cgi?id=506012 . I started to investigate with my really limited dev skill, but I'm doing near zero progress. Here are information that I saved. I'm sharing them in case you or someone else wants to jump on fixing it. Libinput Git repo: - Original libinput work item: https://gitlab.freedesktop.org/libinput/libinput/-/work_items/370 - MR in libinput: https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1218 Libinput API: - libinput_config_eraser_button_mode: switch an hardcoded eraser into a classic button: https://wayland.freedesktop.org/libinput/doc/latest/api/group__config.html#ga61a8a6fbe51996dc03056455db63f855 - Get the status of button an hardcoded eraser button (and more under): https://wayland.freedesktop.org/libinput/doc/latest/api/group__config.html#ga41d02ed89fd61f375d2dbb5d286a109a My thought and just an idea on the GUI: propose for each button a radio choice: o Eraser mode o Button In case the radio is set "Button", expose the current widget to apply a keyboard, mouse (etc) shortcut on it. Just some suggestion and sharing my notes, as this bug is for me hyper high and threaten my activity to do video review with FLOSS of tablet. (because now the udev-hid-bpf project leave the hardcoded eraser mode on device on purpose, now they know the option exist in libinput since end 2025 and they made the System Settings GNOME option for it at Red Hat/Wacom too.) -- You are receiving this mail because: You are watching all bug changes.
