https://bugs.kde.org/show_bug.cgi?id=495107
--- Comment #6 from [email protected] --- So I finally had time to explore this more thoroughly and I managed to find a solid workaround that allows me to use the official XP-Pen driver without startup crashing. I basically had to add a udev rule to make libinput ignore the tablet. In /etc/udev/rules.d/99-ignore-my-device.rules, I used the following rule: ACTION!="remove", KERNEL=="event[0-9]*", ATTRS{id/vendor}=="28bd", ATTRS{id/product}=="0934", ENV{LIBINPUT_IGNORE_DEVICE}="1" For anyone having this problem and wanting to use the above workaround, you may want to find the device in "libinput list-devices" then check "udevadm info --attribute-walk --name=/dev/input/eventwhatever" to make sure the vendor and product attrs are the same. The same rule seems to have worked for both the dongle and the wired connection for me. Figuring out this workaround led me to some interesting oddities regarding how the tablet is initially identified, though. When the tablet is initialized normally, it will first show up as 3 devices: Hanvon Ugee Deco Pro MW Mouse, Hanvon Ugee Deco Pro MW Pen, and Hanvon Ugee Deco Pro MW Pad. (Hanvon Ugee is the parent company of XP-Pen). Once the XP-Pen driver takes over, these 3 devices are disabled (if they are not already disabled by a udev rule) and some new devices are added: XP-Pen Pen, XP-Pen Mouse, and XP-Pen Eraser. These devices have a different product (0002), but have the same vendor. Hope this helps. Also, if there's any way for me to add debugging info for the original KDE Plasma crashing problem that still happens with the initial Hanvon Ugee device, please let me know. -- You are receiving this mail because: You are watching all bug changes.
