https://bugs.kde.org/show_bug.cgi?id=411877
lo...@kde.bt.alestan.publicvm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|5.16.4 |5.20.4
--- Comment #5 from lo...@kde.bt.alestan.publicvm.com ---
Yes, it's still a problem in 5.19 and 5.20. I assume in 5.21 as well (5.21 is
not available in gentoo yet), but I doubt this has been spontaneously fixed
after a year and 3 months.
It is Wayland specific. Under X11, touchscreen input is translated by the X
server into generic mouse input, so kwin doesn't interface with libinput
directly. Under wayland, kwin "talks" to libinput, using
libinput/connection.cpp. Line 614 is where the touchscreen is assigned to the
first screen if it can't guess which screen to use. Since I'm on gentoo, I
just tossed a patch into my user patches to hardcode it to the right screen.
As I wrote in my third message (2019-09-20), I'm happy to turn my patch into a
proper fix, since I have hardware which needs it and the programming skill to
write it, but I want to know there's a reasonable chance of getting the fix
included before I go to the work.
--
You are receiving this mail because:
You are watching all bug changes.
