Wacom 22HD in ubuntu 12.04

[jdadams]

Well, that's interesting. I also have a Bamboo tablet, so I
plugged it in. Now I do have such a setting, and when I unplug
the Bamboo and plug in the 22HD it remains, and shows
the values:

settings-daemon/peripherals/wacom/usb:0x56a:0xfa
area [74699,2170,81390,51914]
display ['WAC','4146','825636144']
is-absolute (checked)

The area value is the same as that returned by xsetwacom
(see below).

By the way the performance of the calibration tool
has changed - it is better, but still off.

For the record here is the output of xsetwacom get 15 all

Option "Area" "74699 2170 81390 51914"
'Button' requires exactly 1 value(s).
Option "ToolDebugLevel" "0"
Option "TabletDebugLevel" "0"
Option "Suppress" "2"
Option "RawSample" "4"
Option "PressureCurve" "0 25 75 100"
Option "Mode" "Absolute"
Option "TabletPCButton" "off"
Option "Touch" "on"
Option "Gesture" "off"
Option "ZoomDistance" "0"
Option "ScrollDistance" "0"
Option "TapTime" "250"
Property 'Wacom Proximity Threshold' does not exist on device.
Option "Rotate" "none"
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Option "Threshold" "27"
Option "ToolType" "249"
Option "ToolSerial" "0"
Option "ToolID" "0"
Option "ToolSerialPrevious" "0"
Option "BindToSerial" "0"
Option "TabletID" "250"

[Favux]

lol Now isn't that special. Appears there is a bug somewhere.

I just checked my git clone of libwacom and Jason did add a cintiq22hd.tablet data file. See if you find that file in /usr/share/libwacom. It isn't in my Precise libwacom. Whether it is there or not it is still a bug that the keys and key values are invisible and suddenly appear when prompted by plugging in a BambooPT. I assume they will disappear again on a reboot.

Now the values you are seeing seem to reflect the Citiq's coordinates offset by the monitor a la MapToOutput.
So the mistake was using the Wacom applet to calibrate.

We've tried a couple of times to add a .tablet data file to /usr/share/libwacom. I assume there is some sort of data base registration when Gnome Control Center is compiled which is why just adding the data file doesn't work. If so I don't know how to update the registration, if that is even possible. Besides SourceForge is down right now. Well I guess I could attach the data file.

So that leaves setting things up through xsetwacom maybe using coordinates from xinput_calibrator. Since SourceForge is down the LWP mediawiki isn't available so see the HOW TO Setup a Wacom Tablet with Multi-Monitors.

By the way how off were the coordinates in the first place? You know, where you felt the need to calibrate.

Edit: Remove the .txt extension from the file.

[jdadams]

I put cintiq-22hd.tablet in place. What effect should that have?
Should I then be able to use the configuration gui?
(Edit: no, the file was not in /usr/share/libwacom).

The configuration was off about an inch or so, certainly
enough to require calibration.

[Favux]

I'm hoping that after a reboot when you go to the Wacom applet your Cintiq is identified by the applet and it now works correctly for you. If it then handles calibration correctly headache avoided. I can't remember if we tried it with a wacom tablet before. I know we have with several non-wacom tablets that had their pen on the wacom X driver. And their .tablet files didn't help.

[jdadams]

I don't want to get too excited, but this appears to have worked.
The configuration applet works fine, and the wacom entry appears
in the dconf-editor. I'm not counting my chickens because
it was working earlier today before all this started, but I'll
keep my fingers crossed.

Thanks so much!

[jdadams]

I'm on the verge of giving up. When I reboot I get the
wacom stuff to show up in dconf-editor about 1/2 the time.
The appropriate file is still in /usr/share/libwacom.
Even when it shows up in dconf-editor, I can only rarely
get the configuration tool to work. So I fell back to using
xsetwacom to configure the stylus, but often this doesn't
even work (do I need to use MapToOutput to enable this?)

[Favux]

I don't blame you. This is turning into more of a headache than it should be.

Since this is intermittent, while unlikely, it may be a hardware problem. First while you are trying to get things working don't plug the Cintiq into a usb hub. Use a usb port directly on the computer.

Are you booting with the Cintiq plugged in? To rule out a hardware problem does the Cintiq work correctly in another release or Distro? Or in another OS such as OSX or Windows?


If you've ruled out hardware the next step is to look at your Xorg.0.log in /var/log. Is it showing you error messages associated with the Cintiq, especially during hot plugging?

You can turn on debugging and generate more messages in the Xorg.0.log. Either in the wacom.conf in xorg.conf.d, see man wacom for the debugging options. Or you can do it using xsetwacom debugging parameters, see man xsetwacom in a terminal.

So I fell back to using
xsetwacom to configure the stylus, but often this doesn't
even work (do I need to use MapToOutput to enable this?)

This is what raises the red flag to me. Maybe you should expand a little more on the xsetwacom commands working intermittently? I assume the Cintiq's display isn't being treated as a separate X screen from the monitor correct? Which means there is a virtual screen composed of both screens. So yes, you would use MapToMonitor to account for the offset of the monitor.

What's the output of xrandr in a terminal? What video chipset are you using?

lspci | grep VGA

and/or

sudo lshw -C display

[jdadams]

It is plugged directly into a usb port on my Thinkpad T400s.
The Cintiq works fine on a mac.

A command such as
xsetwacom set 15 Area "0 0 95500 53500"
sometimes works, and the change appears in the output
of dconf editor. Other times it has no effect (and
I think these are correlated with times it doesn't
appear in dconf-editor). On at least one occasion
making the change directly in dconf-editor had the
desired effect.

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

root@atlas:/home/jda# lshw -C display
*-display:0
description: VGA compatible controller
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 07
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:45 memory:f2000000-f23fffff memory:d0000000-dfffffff ioport:1800(size=8)
*-display:1 UNCLAIMED
description: Display controller
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2.1
bus info: pci@0000:00:02.1
version: 07
width: 64 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: latency=0
resources: memory:f2400000-f24fffff

The display is not currently plugged in, but here is xrandr:


Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 304mm x 190mm
1440x900 60.0*+ 59.9 50.0
1360x768 59.8 60.0
1152x864 60.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)