Bug 481693 - Touchscreen mapping does nothing when you have multiple monitors
Summary: Touchscreen mapping does nothing when you have multiple monitors
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: input (show other bugs)
Version: 5.93.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2024-02-22 19:01 UTC by Tej A. Shah, DMD
Modified: 2024-04-12 03:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tej A. Shah, DMD 2024-02-22 19:01:12 UTC
SUMMARY
***
Touchscreen mapping does nothing when you have multiple monitors
***


STEPS TO REPRODUCE
1.  Have 2 or more screens
2.  Have 1 of them be a touch screen
3.  Make sure all of them are independent (no cloning) 
4. Under touchscreen, set the "Target display" to be one of the displays (not automatic)
5. Use touch screen

OBSERVED RESULT
1. The mouse sill gets mapped to 3 different screens rather than that 1 screen

EXPECTED RESULT
Have the mouse mapped to that one screeen

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Using KDE Neon Testing 20240207-1524 
Using Plasma 6 and Wayland; I haven't tested for X11 yet but I can if need be
Comment 1 Tej A. Shah, DMD 2024-02-22 19:05:00 UTC
Video of problem: https://youtube.com/shorts/OCvdNAS4tuQ
Comment 2 Nate Graham 2024-02-23 22:09:53 UTC
Cannot reproduce on Plasma 6 Wayland with hardware capable of demonstrating the problem. I can choose which display I want to target, and that display is the only one that gets the touchscreen input.

What happens if you change the target display to another value that isn't "Automatic"? Does *anything* change, or is the tap still mapped to both screens?

Something unusual I notice in your screen recording is that the pointer is still visible when you tap. That's not expected on Wayland, and it's not what I see. Are you sure you're using Wayland?

Very cool setup, BTW.
Comment 3 Tej A. Shah, DMD 2024-02-23 22:17:14 UTC
(In reply to Nate Graham from comment #2)
Please see inline:
> Cannot reproduce on Plasma 6 Wayland with hardware capable of demonstrating
> the problem. I can choose which display I want to target, and that display
> is the only one that gets the touchscreen input.

For what it's worth, I am using a Viewsonic TD2210 resistive display. Resistive touchscreens tend to have a different Linux driver compared to a normal capacitive touchscreen. 

> 
> What happens if you change the target display to another value that isn't
> "Automatic"? Does *anything* change, or is the tap still mapped to both
> screens?

No, nothing changes. I can set it to any display including automatic and it still maps the same exact way. 

> 
> Something unusual I notice in your screen recording is that the pointer is
> still visible when you tap. That's not expected on Wayland, and it's not
> what I see. Are you sure you're using Wayland?

Yes, it is using Wayland. The thing about resistive displays is that it pretends to be a mouse but with absolute coordinates rather than relative coordinates. 

> 
> Very cool setup, BTW.

Thanks :-). My dental practice is right now using KDE/Plasma 5 and I am hoping to upgrade to Plasma 6 later this year once these kinds of issues are fixed.
Comment 4 Bug Janitor Service 2024-03-09 03:46:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Tej A. Shah, DMD 2024-03-13 15:23:07 UTC
Hi, what exact info would be helpful? 

(In reply to Bug Janitor Service from comment #4)
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least
> 15 days. Please provide the requested information as soon as
> possible and set the bug status as REPORTED. Due to regular bug
> tracker maintenance, if the bug is still in NEEDSINFO status with
> no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
> due to lack of needed information.
> 
> For more information about our bug triaging procedures please read the
> wiki located here:
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> 
> If you have already provided the requested information, please
> mark the bug as REPORTED so that the KDE team knows that the bug is
> ready to be confirmed.
> 
> Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2024-03-28 03:46:48 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2024-04-12 03:47:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!