https://bugs.kde.org/show_bug.cgi?id=411877
Nicolas Fella <nicolas.fe...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nicolas.fe...@gmx.de
--- Comment #12 from Nicolas Fella <nicolas.fe...@gmx.de> ---
(In reply to Oliver Sander from comment #11)
> FWIW, I have a very similar issue with a SMART Podium 500 device, which is
> an external screen with a stylus. I can also get it recognized as an
> absolute pointer device, but then KWin maps the pointer movement to the
> entire virtual desktop (which comprises the external screen on the left, and
> my built-in laptop screen on the right).
>
> This happens with Plasma 5.24.4 running wayland. The libinput people have
> been very helpful debugging this. There is lots of technical information at
> https://gitlab.freedesktop.org/libinput/libinput/-/issues/769
>
> Do you think this is the same issue, or should I open a separate report?
that is ... interesting.
If I'm reading
https://invent.kde.org/plasma/kwin/-/blob/master/src/backends/libinput/connection.cpp#L547
correctly it should always pick one output to apply (and sometimes the wrong
one)
Is the input split across both screens, Oliver, or is it exclusively on the
wrong one?
If it's the former this may hint at a somewhat unrelated issue
--
You are receiving this mail because:
You are watching all bug changes.
