Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
- After level 40 of pressure from a wacom tablet, pressure levels get inverted which results in nothing drawn
- Issue reproduced using PTZ-630 (Intuos 3) & PTH-660 (Intuos 4)
Where are you experiencing the behavior? What environment?
- PyQT4 and any application that uses QT
- xorg-x11-drv-wacom-0.34.2-2.el7.x86_64
How reproducible:
- always
Steps to Reproduce:
1. apply necessary pressure to pad
2.
3.
Actual results:
- sensitivity value gets inverted resulting in nothing being drawn
Expected results:
Additional info:
sosreport too large to attach
qt-4.8.5-15.el7_4.x86_64
qt-x11-4.8.5-15.el7_4.x86_64
kcm_wacomtablet-2.2.0-1.wdas.el7.x86_64
libwacom-0.24-1.el7.x86_64
libwacom-data-0.24-1.el7.noarch
xorg-x11-drv-wacom-0.34.2-2.el7.x86_64
kernel 3.10.0-693.5.2.el7.x86_64
Yes, I've checked on the Pressure2K option and this has helped, and is
included in latest wacom driver version.
------------------------------------------------------------
# rpm -qa xorg-x11-drv-wacom --changelog | head
* Thu Jun 01 2017 Peter Hutterer <peter.hutterer> 0.34.2-2
- Add Pressure2K option for backwards-compatibility with applications that
hardcode the previous pressure range (#1457024)
* Mon Mar 13 2017 Peter Hutterer <peter.hutterer> 0.34.2-1
- wacom 0.34.2 (#1401655)
* Mon Feb 27 2017 Peter Hutterer <peter.hutterer> 0.34.0-3
- Cancel timers on DEVICE_OFF to avoid potential invalid memory dereference
------------------------------------------------------------
In the process of testing I've managed to disable my keyboard; which
is likely just my mistake however, the pressure option does bring the
behavior for Qt back to a [0.0,0.9999) range as opposed to a range of
[0.0,0.498519897461) ∪ (-0.49951171875,0.0].
For future reference, using PyQt4's QtGui.QWidget, the tabletEvents
show pressure behavior seen in the attached pressure-example.png;
whereas with Pressure2K it will match the full normallized range of
[0.0,1.0], as seen in attached pressure-example-Pressure2K.png.
This can be applied per Jay's sourceforge commit message reference:
Section "InputClass"
Identifier "Wacom pressure compatibility"
MatchDriver "wacom"
Option "Pressure2K" "true"
EndSection
Making sure to use MatchDriver or MatchUSBID (corresponding to
beginning of the tablet id in lsusb output, such as "056a:*")
Section "InputClass"
Identifier "Wacom USB device"
MatchUSBID "056a:*"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Pressure2K" "true"
EndSection
Michael:
apologies for the delay, I was on vacation over the holiday period and this one came in after I had left the country already.
Note that the InputClass section as you posted above is very different to the one in the commit message.
Section "InputClass"
Identifier "Wacom USB device"
MatchUSBID "056a:*"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Pressure2K" "true"
EndSection
With this section you:
* match on the USB id with a wacom vendor ID
* match on the ..event* paths
* assign the wacom driver to those matched devices
* set the Pressure2K option
Wheres as the snippet in the commit message only adds the Pressure2K option to all devices that have the wacom driver assigned. This is considered the safer alternative as it leaves the actual matching of devices untouched or up to some other snippet. Provided the MatchDriver sorts higher than the snippet that assigns the wacom driver it should work just fine.
Either way, I'm marking this as duplicate of 1457024, it's the same issue and already shipped in the current release.
*** This bug has been marked as a duplicate of bug 1457024 ***