Want auto-configuration or gui configuration of Wacom tablets

Bug #215689 reported by nano
102
This bug affects 3 people
Affects Status Importance Assigned to Milestone
wacom-tools (Ubuntu)
Fix Released
Wishlist
Unassigned
xorg (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

By default, input devices like wacom tablets must be manually enabled in xorg.conf. This is how Xorg has worked by default.

In Feisty and some earlier versions, Ubuntu's dexconf would hardcode the Wacom tablet entries into all Ubuntu user's xorg.conf in order to make wacom tablets work out of the box on the few users systems that had them. This resulted in confusing warnings being emitted to the majority of users who did not have wacom tablets, and also caused bugs in other applications (notably rendering an important accessibility tool unusable), so after many, many requests by users the entries were disabled.

The unfortunate result is that this means wacom users have to once again manually configure this in xorg.conf if doing a fresh install. For people who upgraded from Feisty to Gutsy, this was not an issue since their xorg.conf was carried along unchanged.

In a way this trades one bug for another, but the "fix" for the original bug was just an ugly hack. When input hotplug works reliably (hopefully in time for Intrepid), it will no longer be necessary to require users to modify xorg.conf, but for now that is the standard way to do it.

[Original Report Follows]
Hi everyone,

My wacom table graphire worked OK in Gutsy Gibbons, I made a clean install of Hardy Heron, and now only the pen is working (but not the eraser and the pressure) i.e. the mouse is not working! I reinstalled wacom-tools and the xorg-wacom-.... packages several times and the xorg.conf wasn't touched!

Here is my xorg.conf

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "latam"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "vmmouse"
 Option "CorePointer"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Synaptics Touchpad"
EndSection[/CODE]

When i tried to make the same steps of adding
[CODE]
   InputDevice “cursor” “SendCoreEvents”
    InputDevice “stylus” “SendCoreEvents”
    InputDevice “eraser” “SendCoreEvents”

to the xorg.conf file section [CODE]ServelLayout[/CODE] and the other stuff around:

Section "InputDevice"
    Identifier "cursor"
    Driver "wacom"
    Option "Device" "/dev/input/wacom"
    Option "Type" "cursor"
    Option "Mode" "relative"
    Option "USB" "on"
EndSection
Section "InputDevice"
    Identifier "stylus"
    Driver "wacom"
    Option "Device" "/dev/input/wacom"
    Option "Type" "stylus"
    Option "Mode" "absolute"
    Option "USB" "on"
    Option "PressCurve" "50,0,100,50"
EndSection
Section "InputDevice"
    Identifier "eraser"
    Driver "wacom"
    Option "Device" "/dev/input/wacom"
    Option "Type" "eraser"
    Option "Mode" "absolute"
    Option "USB" "on"
EndSection

My Xorg collapsed! It only could work in a low, low resolution mode and the system freezes in the logout... So what can i do now? Do I should report this as a bug?

the output of ls -la /dev/input

 ls -la /dev/input/
total 0
drwxr-xr-x 4 root root 420 2008-04-11 07:45 .
drwxr-xr-x 12 root root 13960 2008-04-11 07:45 ..
drwxr-xr-x 2 root root 80 2008-04-11 07:45 by-id
drwxr-xr-x 2 root root 160 2008-04-11 07:45 by-path
crw-rw---- 1 root root 13, 64 2008-04-11 07:45 event0
crw-rw---- 1 root root 13, 65 2008-04-11 07:45 event1
crw-rw---- 1 root root 13, 74 2008-04-11 07:45 event10
crw-rw---- 1 root root 13, 66 2008-04-11 07:45 event2
crw-rw---- 1 root root 13, 67 2008-04-11 07:45 event3
crw-rw---- 1 root root 13, 68 2008-04-11 07:45 event4
crw-rw---- 1 root root 13, 69 2008-04-11 07:45 event5
crw-rw---- 1 root root 13, 70 2008-04-11 07:45 event6
crw-rw---- 1 root root 13, 71 2008-04-11 07:45 event7
crw-rw---- 1 root root 13, 72 2008-04-11 07:45 event8
crw-rw---- 1 root root 13, 73 2008-04-11 07:45 event9
crw-rw---- 1 root root 13, 63 2008-04-11 07:45 mice
crw-rw---- 1 root root 13, 32 2008-04-11 07:45 mouse0
crw-rw---- 1 root root 13, 33 2008-04-11 07:45 mouse1
crw-rw---- 1 root root 13, 34 2008-04-11 07:45 mouse2
lrwxrwxrwx 1 root root 6 2008-04-11 07:45 tablet-graphire4-6x8 -> event8
lrwxrwxrwx 1 root root 6 2008-04-11 07:45 wacom -> event8

the output of lsusb

 lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 413c:8126 Dell Computer Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 056a:0016 Wacom Co., Ltd
Bus 001 Device 001: ID 0000:0000

the output of wacdump /dev/input/wacom
08:29:29.611 ERROR: Failed to open /dev/input/wacom: Permission denied
WacomOpenTablet: Permission denied

Thanks in advance

Related branches

Revision history for this message
nano (adolfoaz) wrote :

This is fixed with the following /etc/X11/xorg.conf file:

---------------------------------------------------------------------------------
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "latam"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "vmmouse"
 Option "CorePointer"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "stylus"
        Option "Device" "/dev/input/wacom"
        Option "Type" "stylus"
        Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "eraser"
        Option "Device" "/dev/input/wacom"
        Option "Type" "eraser"
        Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "cursor"
        Option "Device" "/dev/input/wacom"
        Option "Type" "cursor"
        Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Synaptics Touchpad"
        InputDevice "stylus" "SendCoreEvents"
        InputDevice "cursor" "SendCoreEvents"
        InputDevice "eraser" "SendCoreEvents"
EndSection
---------------------------------------------------------------------------------

I dunno why, but it worked :) see http://ubuntuforums.org/showthread.php?p=4701832&posted=1#post4701832

This could not be put by default in Hardy Heron?

Adolfo

Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

This is broken in hardy and the tablet has to be configured manually. I can confirm this is an issue. Hardy does not detect my ThinkPad X61T as a tablet and does not enable the WACOM tablet / display by default. As a user, you must manually change your xorg.conf file.

Even a simple "enable stylus / disable stylus" in the gnome control panel would be a huge help.

For a point of reference:
OpenSuSE has a GUI configuration for "pointers" which handles mouse and tablet stylus configuration.

Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

I don't know if this should be filed under xorg-server or xorg-driver-synaptics instead

Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

This is my xorg.conf

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
       Option "CorePointer"
       Option "Device" "/dev/input/mice"
       Option "Protocol" "ExplorerPS/2"
       Option "Emulate3Buttons" "on"
       Option "Emulate3TimeOut" "50"
       Option "EmulateWheel" "on"
# Option "EmulateWheelTimeOut" "200"
       Option "EmulateWheelButton" "2"
       Option "YAxisMapping" "4 5"
       Option "XAxisMapping" "6 7"
       Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "stylus"
        Option "Device" "/dev/ttyS0"
        Option "Type" "stylus"
        Option "ForceDevice" "ISDV4" # Tablet PC ONLY
        Option "Button2" "3"
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "eraser"
        Option "Device" "/dev/ttyS0"
        Option "Type" "eraser"
        Option "ForceDevice" "ISDV4" # Tablet PC ONLY
        Option "Button3" "2"
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "cursor"
        Option "Device" "/dev/ttyS0"
        Option "Type" "cursor
        Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Driver "intel"
# Option "AccelMethod" "EXA"
# Option "MigrationHeuristic" "greedy"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Synaptics Touchpad"
        InputDevice "stylus" "SendCoreEvents"
        InputDevice "cursor" "SendCoreEvents"
        InputDevice "eraser" "SendCoreEvents"
EndSection

Bryce Harrington (bryce)
Changed in xorg:
importance: Undecided → Wishlist
Bryce Harrington (bryce)
description: updated
Revision history for this message
FriedChicken (domlyons) wrote :

It would be nice if Wacom graphic tablets would work with hotplugging without editing xorg.conf (especially as this needs a Xorg restart). I think this should be possible by the auto detection of Xorg

Revision history for this message
Rick @ rickandpatty.com (rick-rickandpatty) wrote :

> Hardy does not detect my ThinkPad X61T as a tablet and does not enable the WACOM
> tablet / display by default.

I recently installed Hardy on my Thinkpad X41 tablet, and also experienced the issue of a non-working stylus. I noticed that /dev/input/wacom was actually there and configured correctly after the install, but (as reported above) none of the necessary configuration for using it with X was present in xorg.conf. Luckily, I'd backed up my xorg.conf from a previous install so I didn't have to dig very far to discover what the problem was.

For tablet PC users (there will probably be more of us soon, as most educators I demonstrate tablet technology to really like it), this seems like a bug in the Ubuntu installer. Shouldn't there be some logic to say that if a tablet is detected at install time, then the user will most definitely want the default xorg.conf to contain the relevant bits enabling the tablet?

Or perhaps an ubuntu-tablet package, which installs wacom-tools (needed for rotation), a rotation applet or script, cellwriter, and xournal? As a bonus, it could configure gdm and gnome-screensaver with an on-screen keyboard so tablet users could log in and use the screen-lock feature without having to unfold the tablet.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

You could try this fdi-file (stolen from Fedora) and put it in /etc/hal/fdi/policy, to see how it works with the xserver in hardy:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- this is probably a bit imprecise -->
<deviceinfo version="0.2">
  <device>
    <match key="info.capabilities" contains="input">
      <match key="info.product" contains="Wacom">
 <merge key="input.x11_driver" type="string">wacom</merge>
      </match>
    </match>
  </device>
</deviceinfo>

remember to use an xorg.conf without wacom entries on it.

Iulian Udrea (iulian)
Changed in xorg:
status: Confirmed → Triaged
Revision history for this message
FriedChicken (domlyons) wrote :

I've tried it out what Timo Aaltonen said, but it didn't work. Xorg loads a module "wacom" but no specific options for the pencil (absolute positioning) and nothing is added to xorg.conf.
GIMP also only detects a normal "configured input device" and special graphic tablet features don't work.

Revision history for this message
FriedChicken (domlyons) wrote :

Isn't it possible to let Jockey configure xorg.conf when he detects a wacom device?

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi adolfoaz,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

This is still an issue for me, I think lspci would not make sense here since I have a tablet pc with a serial connection (I don't know if internal or emulated).

Revision history for this message
Bryce Harrington (bryce) wrote :

[Not really necessary to have this opened against xorg; the wacom-tools task is sufficient]

Changed in xorg:
importance: Undecided → Wishlist
status: Incomplete → Invalid
Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

It would be appreciated if you could provide some clarification if there is something else we can track to indicate the status on resolving this issue.

Closing bugs without actually resolving the issue to the submitter(s) satisfaction is discouraging and happens all too often.

I would appreciate it, Bryce, if you could provide any information regarding where further information can be found regarding the resolution of our actual issue.

wacom-tools does not activate the tablet functionality of my X61t.

I have recently reinstalled with 8.10 and been testing the first Alpha of 9.04. This functionality is still not working out of the box.

Since you reference "the wacom-tools task is sufficient" can you please provide a link to where people that find this bug searching for resolution may find their resolution?

Thanks.

Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

Sorry -- Ignore my comment above... I see it's still a wacom-tools bug... I haven't had my first cup of coffee this morning.

I humbly offer my apology :)

Anyway -- on another note. Here's my lspci output.

Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

Ok -- I'm going to get my cup of coffee now... Way too early in the morning here :P

 I didn't run my last lspci with sudo ... here's my sudoed lspci

Revision history for this message
Loïc Martin (loic-martin3) wrote :

If you want to track the issue, there's a blueprint for Jaunty at https://blueprints.launchpad.net/ubuntu/+spec/wacom-tablets-ui

There's been a few discussions in ubuntu-devel-discuss, ubuntu-x, linuxwacom-discuss and linuxwacom-devel. Check the archives for October/November 2008. xorg mailing list has offered nothing (the person that proposed HAL and .fdi files for wacom tablets doesn't seem to have understood that HAL won't allow more than one device, and that it's not going to work).

As a quick summary, hotpluging won't allow a decent solution in the next few month, or even years (see the discussions), and nobody has even offered the beginning of a possible solution. So for the moment there's only xorg.conf.

Revision history for this message
ethana2 (ethana2) wrote :

__Don't forget the wizardpen driver.__ Wacom is too expensive for us normal folk.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package wacom-tools - 1:0.8.2.2-0ubuntu1

---------------
wacom-tools (1:0.8.2.2-0ubuntu1) jaunty; urgency=low

  * New upstream release. (LP: #355340)
  * Patch 100_allow_eraser.patch dropped, included in this version.
  * 100_fedora-fix-build.diff
    - Make the driver to build against xserver 1.6.
  * 101_fedora-fix-mapping.diff
    - No button 0 in the server, all offsets have to begin at 1.
  * 102_fedora-wcmmaxx.diff
    - Don't assign priv->wcmMaxX/Y back into common->wcmMaxX/Y.
  * 103_fedora-hal-setup.diff
    - Add a hal callout program to set up the device.
    (LP: #215689, #356091)
  * 104_revert-check.diff
    - Don't check the serial number, it breaks some devices.
  * Modify 10-wacom.fdi to include changes from Fedora. Should allow
    hotplugging (built-in) serial tablets. (LP: #337112)
  * rules:
    - Run autoreconf on build
    - xserver-xorg-input-wacom includes /usr/lib/hal/hal-setup-wacom
  * control:
    - autoreconf: add automake, libtool to build-deps.
    - hal-setup-wacom: add libhal-dev to build-deps.

 -- Timo Aaltonen <email address hidden> Tue, 24 Mar 2009 10:06:54 +0200

Changed in wacom-tools (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Very good news, thanks for this.

Is this fix in jaunty? Moreover, wacom-tools is currently not installed by default in jaunty, making the tablet the only non-autoconfigured device on my Toshiba M400. Should I file a bug about this?

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Sorry, I see the fix is in jaunty, remains the auto-install of the package.

Revision history for this message
Ryan Sinn (ryan-sinn) wrote :

running /usr/lib/hal/hal-setup-wacom produces the following error:

hal-setup-wacom: Failed to get UDI

the wacom pen works after install wacom-tools and rebooting (I can move the mouse with the pen) but I cannot find a GUI to configure it... all buttons on the pen = left (primary) click. Button 1, button 2 and button 3 all perform a primary / left click behavior.

Revision history for this message
Christophe Olinger (olingerc) wrote :

I guess the tablet GUI won't make it into Jaunty? Do Loic or Alberto have any news about this?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

No, it was unfortunately postponed for karmic.

Revision history for this message
MvW (2nv2u) wrote :

Hasn't made it into Karmic, Lucid or Meerkat.. Seems to be postponed till forever.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.