Setting Wacom pen button to double click doesn't work

The above mentioned commands have to contain an additional 'add' after the 'xsetwacom'. But even with this little extra, it still doesn't work.

I have the same problem, but with a Graphire tablet. I tried both:

xsetwacom set stylus button3 "dblclick 1"

and setting it in xorg.conf:

Section "InputDevice"
        Driver "wacom"
        Identifier "stylus"
        Option "Device" "/dev/input/wacom"
        Option "Type" "stylus"
        Option "Button2" "3"
        Option "Button3" "dblclick 1"
EndSection

So it seems that this bug is not related to xsetwacom but to the wacom-driver that is shipped with Xorg...

-Levien

Closing invalid component.

Please try on hardy alpha2 + updates (new wacom-tools uploaded today).

Sorry for the delay, I only just installed Hardy due to lack of time (and disk-space for the update).
The wacom-tools method seems to work correctly now. However, adding

Option "Button3" "dblclick 1"

or

Option "Button3" "17"

to xorg.conf still does not work. When using the first form, X complains that the parameter value has to be numeric. However, the old numeric value 17 also does not work anymore. Seems as if the driver and the bit that parses the Xorg values are out of sync somehow, one expecting a numeric value while the other expects a string...

As a workaround, I've added the following command to my Session:

xsetwacom set stylus button3 "dblclick 1"

Where should I report the xorg.conf issue?

-L.

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

On Jaunty:

While looking at 'tail -f Xorg.0.log' I see that mappins that include a 'dblclick' are ignored while others are not.

E.g. the following work:
xsetwacom set "Wacom Graphire2 4x5" button2 3
xsetwacom set "Wacom Graphire2 4x5" button1 1

while this one does not:
xsetwacom set "Wacom Graphire2 4x5" button3 "dblclick 1"

I can confirm this on Jaunty. In Intrepid, this at least used to work:

xsetwacom set "Wacom Graphire2 4x5" button3 "dblclick 1"

But as of Jaunty, setting a button to "dblclick 1" or "17" seems to be broken, which is rather annoying. I haven't tried setting it in xorg.conf, as that already stopped working in Hardy. Moreover, Wacom tablets are now recognised through hald anyway (making them hotpluggable, which is nice).

-L.

It appears that any 'dblclick X' event is actually set up as 'dblclick 0'.
This can be confirmed by running:

xsetwacom get stylus button3

A way around this is suggested in http://ubuntuforums.org/archive/index.php/t-418203.html

xsetwacom set stylus button3 196609

This will set it to 'DBLCLICK 1'

However, on my 9.04 this setting still does not produce working double clicks in practice.

Confirming that value 196609 does not work on Ubunu 9.04:

erik@oosttop:~$ sudo tail -f /var/log/Xorg.0.log
(**) Wacom Bamboo: max y = 9225
(**) Wacom Bamboo: max z = 511
(**) Option "Button2" "3"
(**) Wacom Bamboo: button2 assigned to 3
(**) Option "Button3" "196609"
(**) Wacom Bamboo: button3 assigned to 196609
(**) Option "BaudRate" "9600"
(**) Wacom Bamboo: serial speed 9600
(II) XINPUT: Adding extended input device "Wacom Bamboo" (type: Wacom Stylus)
(==) Wacom device "Wacom Bamboo" top X=0 top Y=0 bottom X=14760 bottom Y=9225 resol X=2540 resol Y=2540

Still no double click behavior though.

Thank you for reporting this issue with wacom-tools, we are migrating all of these bug reports over to the xf86-input-wacom package as this replaces the older package in the development version of Ubuntu.

This would be a good point for you to re-test this issue against the new package to see if is still occurring. If not, you can mark it as Fix Released in Launchpad.

The problem still persists in Lucid when using xsetwacom. Also, I'm unsure as to where the wacom configuration settings should go now in the Xorg configuration files... The HAL fdi-stuff is deprecated as I understand, and wacom configuration now seems to be located in /usr/lib/X11/xorg.conf.d/10-wacom.conf. However, it contains InputClass sections rather than the old InputDevice sections. I have trouble finding any documentation on this new configuration, and don't want to break Xorg by messing around with it unknowlingly. Can anyone enlighten me? :-)

This is probably related to 570550 "Can't make Wacom button emit double-click when compiz enabled".

As suggested in bug #446943 I added the following two lines to the first section of /usr/lib/X11/xorg.conf.d/10-wacom.conf in Lucid:

Option "Button2" "3"
Option "Button3" "dblclick 1"

Button 2 now works as expected, but for button 3 Xorg still complains that the value should be an integer and refuses to work. When using the values 196609 or 17 Xorg does not complain, but double click events also don't work.
When using xsetwacom no errors are logged, but again the double click event is not emitted.

I also tested the xsetwacom method without compiz, but the result was the same. Also with Metacity I could not get double click events to work...

[This is an automatic notification.]

Hi Harm,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 112310

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 112310 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/112310

As I am not the original reporter, I've submitted a new bug report for Lucid as Bug #581663
I also found a workaround that was submitted a few months ago to one of the Ubuntu forums. It uses the X key-bindings to produce double click events. I did not test it yet: http://www.uluga.ubuntuforums.org/showthread.php?t=1366998

[Resetting to incomplete since we need a response from the original reporter on this].

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

It is confirmed in 10.04.

This seems to be fixed in 12.04, albeit with a new syntax. To assign a double-click to a button, either run something like:

xsetwacom --set "Wacom Graphire2 4x5 stylus" Button 3 "button 1 button 1"

(source: https://gist.github.com/i-e-b/2894651)

or better, create a file /usr/lib/X11/xorg.conf.d/10-wacom.conf with the following line:

Option "Button 3" "button 1 button 1"

This fixes the problem for me.