Bug 493352

***
Wacom Co., Ltd CTL-472 [One by Wacom (S)] wayland cursor not update properly. Tool icons are wrong. Desktop cross icon bug.

i am using arch linux + plasma 6.1.5 wayland. Krita 5.2.3. When i using wacom CTL-472 on desktop icon apears cross icon. When i using krita and moving pen on my tablet for drawing icons are getting stuck not switching between of selected tools icons.



STEPS TO REPRODUCE
1. i start my computer with normal method
2. My computer is started, arch linux had started. Kde plasma has started properly. 
3. I reached to my desktop. My wacom ctl-472 tablet has been pluged to my computer with usb port. 

OBSERVED RESULT
The tablet cursor I should see on the desktop was not as it should be. The cursor of my drawing tablet was in the shape of a cross. And no matter where I moved it, it never turned into an arrow. When I opened Krita, it very rarely turned into an arrow. But this time it got stuck like that.

EXPECTED RESULT

I expect the cursor of my drawing tablet to work properly just as it does in X11, in other words, to take the form of selected tool icons. I don't expect a cross-shaped cursor on the desktop.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.1.5
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
I've searched all over the internet. Maybe I'll find a solution. A couple of places suggested opentabletdriver. I installed it following all the instructions to the letter but it still didn't fix it. The same problems persisted. Many places said that the problem is not in the gnome-shell environment, it works fine. I haven't tried it myself, but I believe it does, so it's probably a problem with the incompatibility of kde plasma's wacom tablet driver with plasma. Some say that the drawing tablet cursor icons and the kde plasma icons don't match correctly. In other words, maybe the permissions don't match. These are my research results. Going back in the history of the error logs, I found that the problem has been going on for almost 4 years. How can it be so many years without a fix. I think it will be solved soon, I believe.I look forward to your help and I thank and pray for you and your efforts in all your endeavors.