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 651614 - wacom settings lost if device is unplugged and plugged back in
Summary: wacom settings lost if device is unplugged and plugged back in
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: wacomcpl
Version: 6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Peter Hutterer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 21:55 UTC by Bryan Mason
Modified: 2018-11-14 16:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-01 21:15:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 624560 0 urgent CLOSED wacom control panel functions are not working 2021-02-22 00:41:40 UTC

Description Bryan Mason 2010-11-09 21:55:40 UTC
Description of problem:

    In the latest wacom driver packages, we noticed that the wacom
    settings are lost if the device usb is uplugged and plugged back
    in. We have several cintiqs set up in a dual screen environment
    and the xsetwacom mappings using wacomcpl is lost each time we
    uplug the device. We have cintiqs hooked through a kvm switch
    between two machines.

Version-Release number of selected component (if applicable):

    wacomcpl-0.9.0-5.bz624560.1.wdas.el6.x86_64
    xorg-x11-drv-wacom-0.10.5-8.bz624560.1.wdas.el6.x86_64

How reproducible:

    Unknown.

Steps to Reproduce:

    1. Set up a cintiq in a dual screen (twinview) setup.
    2. Map the cintiq to itself.
    3. Unplug the cintiq usb and plug it back in.
  
Actual results:

    Cintiq mappings are lost.

Expected results:

    Cintiq mappings should not be lost.

Comment 3 Peter Hutterer 2010-11-15 03:08:44 UTC
This is an inherent problem with the design of wacomcpl.

Wacomcpl applies the settings as they are selected through the commandline utility xsetwacom and at the same time appends them to the $HOME/.wacomcplrc file which is executed as part of the X init process. When devices are added or removed at runtime, the wacomcplrc file does not get executed and the device settings stay at the default settings.

The proper solution to this would be to add a daemon that monitors device additions and removals but that's a rather tricky addition given the current code (and one more daemon to be aware of).

Comment 5 RHEL Program Management 2010-12-01 21:15:15 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 6 Peter Hutterer 2010-12-01 22:12:03 UTC
As a workaround, the settings applied by wacomcpl can be re-applied manually to the device by running the $HOME/.wacomcplrc script.

Comment 10 Peter Hutterer 2011-03-17 23:40:57 UTC
On another note, I would like to point out that the configuration created by wacomcpl can be made permanent by moving the respective options into an InputDevice section or an fdi file.

for example, if wacomcplrc contains the line 
  xsetwacom set "Wacom Intuos4 6x9" Button1 "5"

This translates into
  Option "Button1" "5"
in the matching xorg.conf section

or into an fdi file like this

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.product" contains="Wacom Intuos4 6x9">
      <merge key="input.x11_options.Button1" type="string">5</merge>
    </match>
  </device>
</deviceinfo>


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