Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

RocketTiger · 2015-08-01 12:10:33

Hello everyone,
I hope this is the right section...
My Wacom tablet (Bamboo Fun Pen&Touch, CTH-661) has started having problems with the buttons on the side of the pen and with the express keys on the pad. The buttons do work but they don't seem to be mapped correctly. It used to work perfectly, then I have spent some months without ever touching the tablet and when I tried to use it again a few days ago, I discovered it acted funny.
Right now, both buttons on the pen act like a normal left click, the top and bottom express keys seem to be left-clicking as well. I thought the two buttons in the middle did nothing, but I just accidentally noticed they are interpreted as page back and page forward by Firefox, I really have zero clues about where this comes from.
Everything else is alright: pressure sensitivity, eraser, touch, they all work correctly.

A long time has passed since I last used it and it worked, so I have performed several Arch updates since then... so I'm not sure what caused this. Kernel Driver? Xorg driver? Changes to config files I missed? Changes in packages? Update to Plasma5? I have no idea.
The pen buttons have always worked out-of-the-box for me, I had mapped the express keys through the KCM module which can be found in AUR, and it has always worked before. My searches so far have been useless, so any help you can give me will be appreciated.

If you need any command outputs tell me, I'm not really sure what would be useful.

$ xinput
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ FSPPS/2 Sentelic FingerSensingPad         id=15   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 6x8 Pen stylus           id=10   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 6x8 Pen eraser           id=11   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 6x8 Pad pad              id=12   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 6x8 Finger touch         id=16   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ USB Webcam                                id=13   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=14   [slave  keyboard (3)]

Thank you all in advance

nomorewindows · 2015-08-01 12:32:06

Have you tried messing around with xev? You may need to define the buttons in your DE/WM.

RocketTiger · 2015-08-03 07:29:51

Thanks for your reply.
I didn't know about xev, I tried to use it but I'm not sure what should I gather from it, any advice?
The only thing I managed to get from it is that the pad buttons are all detected as different buttons (called, like, button 5, 6, etc). When I tried I couldn't get anything from the stylus since xev records every slight pen movement and the times I press the buttons got lost in the output, but I just realized there's an --event option to filter button events, I might try that later (I don't have the tablet with me ATM)

You may need to define the buttons in your DE/WM.

I did that with the KCM module that I mentioned earlier. It's the kcm-wacomtablet-frameworks-git package from the AUR, it adds an entry about wacom tablets in the KDE System Settings. The settings are correct there, but they don't seem to work. The rest of the options do work, such as disabling and enabling touch, passing from absolute to relative positioning, etc, but the buttons mapping has no effect at all.

nomorewindows · 2015-08-03 18:14:09

Seems like I had to get the scancodes of the keys from xev, then use ?? (think of it in a minute) to reassign it to something useful that the DE/WM might recognize.

nomorewindows · 2015-08-10 01:14:18

Ah yes, setkeycodes may be needed to redefine your keys if they don't want to work with your DE/WM.

GRem · 2015-08-16 03:41:20

I just had this problem now that I updated several things. My 1st gen Bamboo Fun started using every button as button 1 (left click). Setting different click types in the KDE wacom config screen didn't help, although other things such as abs/rel mapping and all that stuff did work. So I'm pretty much on the same boat.

I downgraded xf86-input-wacom to the previous version, disconnected and reconnected the tablet, and now it's fine again. Changing the button mappings now works - I had to re-set them because the default pen tip action was set to nothing after the update, so I set it back to left-click.

Try downgrading the wacom driver.

Last edited by GRem (2015-08-16 03:42:22)

RocketTiger · 2015-08-26 12:32:14

Sorry for the late reply, I went on vacation for a while

GRem wrote:

I just had this problem now that I updated several things. My 1st gen Bamboo Fun started using every button as button 1 (left click). Setting different click types in the KDE wacom config screen didn't help, although other things such as abs/rel mapping and all that stuff did work. So I'm pretty much on the same boat.
I downgraded xf86-input-wacom to the previous version, disconnected and reconnected the tablet, and now it's fine again. Changing the button mappings now works - I had to re-set them because the default pen tip action was set to nothing after the update, so I set it back to left-click.
Try downgrading the wacom driver.

That might be it. My tablet is a 2nd gen so I guess it might be a bug affecting some old bamboo models. I just noticed there's a new update of the xorg wacom driver released a few days ago, I'm now doing a full system update and see if this has been fixed. Otherwise, I'll try downgrading the driver to 0.29

nomorewindows wrote:

Ah yes, setkeycodes may be needed to redefine your keys if they don't want to work with your DE/WM.

As GRem wrote, it's probably a driver issue, anyway I just verified that xev really seems to be reading all buttons as button1, except for the two middle pad buttons.

I will let you know how it goes with the driver update.
Thanks a lot for the help!

RocketTiger · 2015-08-26 16:27:18

Alright, updating the xorg driver to 0.31.0-1 solved the problem. Everything is back to normal

GRem · 2015-08-26 17:04:23

Alright, good to hear it!
Since it's fixed, I'll update mine now as well.

Arch Linux

#1 2015-08-01 12:10:33

Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#2 2015-08-01 12:32:06

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#3 2015-08-03 07:29:51

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#4 2015-08-03 18:14:09

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#5 2015-08-10 01:14:18

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#6 2015-08-16 03:41:20

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#7 2015-08-26 12:32:14

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#8 2015-08-26 16:27:18

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

#9 2015-08-26 17:04:23

Re: Wacom Bamboo Fun Pen&Touch problems with pen buttons and express keys

Board footer