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 920385 - Unable to map the esc key using xsetwacom.
Summary: Unable to map the esc key using xsetwacom.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-wacom
Version: 6.4
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: rc
: 6.5
Assignee: Peter Hutterer
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 960058
TreeView+ depends on / blocked
 
Reported: 2013-03-12 00:51 UTC by Parthasarathi Susarla
Modified: 2018-12-04 15:07 UTC (History)
5 users (show)

Fixed In Version: xorg-x11-drv-wacom-0.16.1-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 07:27:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1568 0 normal SHIPPED_LIVE xorg-x11-drv-wacom bug fix update 2013-11-20 21:40:03 UTC

Description Parthasarathi Susarla 2013-03-12 00:51:28 UTC 
Description of problem:
Unable to map the Escape key to one of the buttons on a Wacom Cintiq 22HD pad. All other modifier keys work (alt/ctrl etc.).

Version-Release number of selected component (if applicable):
xorg-x11-drv-wacom-0.16.1-3.el6.x86_64 on Red Hat Enterprise Linux 6

How reproducible:
Consistent.


Steps to Reproduce:
1. Try and set escape to one of the buttons on the Wacom tablet:
   $ xsetwacom --set "Wacom Cintiq 22HD pad" Button 13 "key  Esc"
The command doesn't return any error, but the key isn't mapped.

  
Actual results:
Running a get results in a null:
$ xsetwacom --get "Wacom Cintiq 22HD pad" Button 13
key +(null) -(null) 

Expected results:
The button on the pad should be mapped to Escape

Additional info:

Output from xev:

KeyPress event, serial 34, synthetic NO, window 0x8600001,
    root 0x1f5, subw 0x0, time 946082789, (89,118), root:(3636,1033),
    state 0x10, keycode 8 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x8600001,
    root 0x1f5, subw 0x0, time 946082789, (89,118), root:(3636,1033),
    state 0x10, keycode 8 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False
Comment 1 Peter Hutterer 2013-03-12 04:19:44 UTC 
Verified, upstream fix is xf86-input-wacom-0.17.0-3-ge604e4e
Comment 6 Peter Hutterer 2013-07-01 01:54:04 UTC 
MODIFIED

xorg-x11-drv-wacom-0.16.1-4.el6 is available in brew
Comment 11 errata-xmlrpc 2013-11-21 07:27:27 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.

http://rhn.redhat.com/errata/RHBA-2013-1568.html
Note You need to log in before you can comment on or make changes to this bug.