Bug 1543631 - Wacom Expresskeys Remote not detected as "tablet" by GUI
Summary: Wacom Expresskeys Remote not detected as "tablet" by GUI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: control-center
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: 7.8
Assignee: Carlos Garnacho
QA Contact: Desktop QE
Jana Heves
URL:
Whiteboard:
Depends On:
Blocks: 1638517 1738389
TreeView+ depends on / blocked
 
Reported: 2018-02-08 20:50 UTC by Michael Boisvert
Modified: 2020-05-21 13:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Wacom Expresskeys Remote not detected as tablet The *gnome-shell* and *control-center* utilities do not detect unpaired *Wacom Expresskeys Remote* devices (EKRs). As a consequence, within the Wacom settings, there is no way to map the buttons on the *EKR*. Currently, *EKR* works only when it is paired to a tablet with a built-in pad.
Clone Of:
: 1638517 (view as bug list)
Environment:
Last Closed: 2020-05-21 13:00:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Michael Boisvert 2018-02-08 20:50:26 UTC 
Description of problem: The EKR that is part of the Wacom Cintiq 27QHD has a separate device that acts as the "pad" device. Within the Wacom settings, there is no way to map the buttons on the EKR. It only detects the 27QHD and not the EKR. 

I noticed in the Xorg log that the EKR is picked up without issue and running xinput list shows the device as well.

Steps to Reproduce:
1. Plug in Cintiq 27QHD
2. Open Settings -> Devices -> Wacom Tablet
3. Select Tablet at the top of the window. 

Actual results: No EKR, no buttons able to be mapped, etc.

Expected results: EKR detected and map-able.
Comment 4 Matthias Clasen 2018-02-19 20:04:01 UTC 
setting devack- to reflect the last comment
Comment 5 Red Hat Bugzilla Rules Engine 2018-02-19 20:04:06 UTC 
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.