#129 Pad not working after upgrade
Hi,
I have a small Bamboo with pad and touch. I'm using Debian/unstable. I just upgraded to X.org 1.6 and the Wacom X driver and tools to 0.8.3-2 (Debian 0.8.3.2-1).
I had a working setup where I used xsetwacom in the .xsession file to bind events to the Buttons and strip. I'm under the impression that only the pad stopped working, but you probably understand this better.
I first attempted to set the tablet with the HAL method, and after changing the property of the FDI file from 10 to 11, I got it to work. However, I could see no way to set the pad properties, at least nothing that caused the events to be sent when pressing the buttons, so I thought I was doing something wrong (and perhaps I was, but stay with me). I noticed that xsetwacom just complained that it couldn't set up the devices (but I think it's because it searches the device in the xorg.conf and finds nothing).
So I went back to my original set up in the xorg.conf file and xsetwacom now works, but to my surprise the pad still didn't work. Xev doesn't report any event when I press the buttons, or when I touch the up/down arrows on the strip. It does show events when I use the scroll in the strip/touchpad.
I noticed that some FDI was still setting up the main device with a keymapping and the evdev driver, so I removed it with hal-device. I switched back to the VT to reset the device, to no avail.
I'm attaching X's log grep Wacom.
Here are my settings:
/usr/bin/xsetwacom set pad Button1 "core key shift"
/usr/bin/xsetwacom set pad Button2 "core key alt"
/usr/bin/xsetwacom set pad Button3 "core key control"
/usr/bin/xsetwacom set pad Button4 "core key space"
/usr/bin/xsetwacom set pad striplup "core key up"
/usr/bin/xsetwacom set pad stripldn "core key down"
FWIW, the dump below is me scrolling the pad counter-clockwise. Clockwise is the same without the state 0x800 event (I don't really know the meaning of it):
ButtonRelease event, serial 34, synthetic NO, window 0x3a00001,
root 0x13c, subw 0x0, time 2153223, (71,53), root:(1184,937),
state 0x800, button 4, same_screen YES
MotionNotify event, serial 34, synthetic NO, window 0x3a00001,
root 0x13c, subw 0x0, time 2153223, (71,53), root:(1184,937),
state 0x0, is_hint 0, same_screen YES
ButtonPress event, serial 34, synthetic NO, window 0x3a00001,
root 0x13c, subw 0x0, time 2153275, (71,53), root:(1184,937),
state 0x0, button 4, same_screen YES
Log grep wacom
This is a bug in 0.8.3-2 that has been reported by Martin Raspaud at linuxwacom-discussion. It will be fixed in 0.8.3-3.