Bug 429714 - X11: When using an active stylus or touchscreen with multiple displays, the input is fed to both screens.
Summary: X11: When using an active stylus or touchscreen with multiple displays, the i...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 5.19.5
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 402247 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-11-27 09:23 UTC by tjmoores
Modified: 2021-10-07 14:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tjmoores 2020-11-27 09:23:34 UTC
SUMMARY
When using an active stylus or touchscreen with multiple displays, the input is fed to both screens.


STEPS TO REPRODUCE
1. Connect at least 1 auxiliary display to a laptop with active stylus support and/or a touchsceen.
2. Use the touchscreen/active stylus on the laptop display

OBSERVED RESULT
The cursor moves and interacts with windows on both the laptop's built in display and the auxiliary display. When using an active stylus on apps such as Xournal the content on the other display gets scrolled up and down as the stylus moves.

EXPECTED RESULT
The input is only fed to the content on the laptop's built in display & the content on the other display remains unaffected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon x86_64
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.75.0
Qt Version: 5.4.0-54-generic

ADDITIONAL INFORMATION
Laptop is a HP 15-ds0002na. Active stylus is a HP 1MR94AA.
Comment 1 Nate Graham 2021-10-06 19:19:12 UTC
Confirmed on X11, not present on Wayland.
Comment 2 Nate Graham 2021-10-06 19:22:18 UTC
*** Bug 402247 has been marked as a duplicate of this bug. ***
Comment 3 Vlad Zahorodnii 2021-10-07 10:01:49 UTC
Why was this bug moved to kwin? Please report this bug to xserver developers.
Comment 4 Nate Graham 2021-10-07 14:25:48 UTC
Because plasmashell wasn't the right place for it either, and not all of us are window manager developers with perfect insight into what layer of the stack a given bug lives in?

BTW UPSTREAM is the correct resolution for bugs that are legitimate but upstream of KWin.