RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1759619 - [Xorg Classic] Cannot Restore Wacom Tablet Screen Mapping
Summary: [Xorg Classic] Cannot Restore Wacom Tablet Screen Mapping
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mutter
Version: 8.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.2
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-08 17:17 UTC by Michael Boisvert
Modified: 2020-04-28 16:10 UTC (History)
2 users (show)

Fixed In Version: 3.32.2-22
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:09:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1766 0 None None None 2020-04-28 16:10:18 UTC

Description Michael Boisvert 2019-10-08 17:17:37 UTC
Description of problem: After mapping a tablet to one of your monitors, you cannot go back to using your Wacom pen tablet on both of your monitors. This is applicable to using either method of screen mapping.

Steps to Reproduce:
1. Create a setup with two monitors and a wacom pen tablet
2. Map the tablet to one of the monitors, move the pen around.
3. Try to restore the screen mapping to use both monitors.

Actual results: Screen mapping remains on the single, previously mapped monitor. 

Expected results: Screen mapping is unset and restored to both monitors.

Additional info: If you restart the session, the mapping goes back to both monitors (if you have it set to both). I didn't see anything in the journal or dmesg to pinpoint the issue, so I assigned it to mutter.

Comment 1 Michael Boisvert 2019-12-12 16:35:12 UTC
The problem has morphed a bit. I now cannot have a pen tablet mapped to span two displays at all, only one display or another. I can successfully map the tablet to either screen with the GUI or with the "switch monitor" button.

Comment 2 Carlos Garnacho 2019-12-13 22:29:13 UTC
Should be fixed in 3.32.2-22

Comment 4 Michael Boisvert 2019-12-17 15:38:21 UTC
Verified on mutter-3.32.2-26.el8.x86_64.

Comment 6 errata-xmlrpc 2020-04-28 16:09:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1766


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