Bug 1980812 - [RHEL 9] 22HD Touchscreen Incorrectly Controls Both Monitors
Summary: [RHEL 9] 22HD Touchscreen Incorrectly Controls Both Monitors
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-settings-daemon
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: beta
: ---
Assignee: Carlos Garnacho
QA Contact: Michael Boisvert
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-09 15:18 UTC by Michael Boisvert
Modified: 2023-07-26 14:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-09 07:27:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michael Boisvert 2021-07-09 15:18:10 UTC
Description of problem:

When using the Cintiq 22HD touch with a dual screen setup, the touchscreen is incorrectly mapped to the entire span of both monitors. It should just be limited to its own display. The stylus is correctly mapped.

How reproducible:

Always

Steps to Reproduce:
1. Install RHEL7.0
2. Create a dual monitor setup (laptop + 22HD)
3. Try using the touchscreen.

Actual results: The touchscreen incorrectly controls the entire span of both monitors.

Expected results: The touchscreen controls its own display regardless of a multi monitor setup.

Very similar to an old issue in RHEL7: https://bugzilla.redhat.com/show_bug.cgi?id=1029612

Comment 1 Michael Boisvert 2021-09-08 16:08:22 UTC
Still occurring in RHEL 9.0 Beta.

Comment 3 RHEL Program Management 2023-01-09 07:27:37 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 11 Michael Boisvert 2023-07-26 14:36:42 UTC
The 22HDT no longer exhibits the issue outlined in the description.


Note You need to log in before you can comment on or make changes to this bug.