ubuntu-x-swat team mailing list archive

[appultaart <appultaart@xxxxxxxxx>]

Hi Bryce,

I have re-tested this issue on Ubuntu Lucid 10.04. The bug is not
occurring: button assigning seems to work. Superb! Thanks for looking
into this, even with such an old reported bug.

Here is what I did to test:
(NB I have no access here to my old PC, I connected the Wacom Graphire4 pad to a laptop running Ubuntu 10.04, standard packages installed, standard settings)

1. The command "xsetwacom set pad Button1 "core key a"" did not work;
2. Command "xinput list" reported among other things a Virtual core pointer "Wacom Graphire4 4x5 pad, id=16 [slave pointer]"
3. I replaced that line with the 'pad' command of line 1:
    "xsetwacom set "Wacom Graphire4 4x5 pad" Button1 "core key a"
4. Pressing the pad's Button1 gives the output "a". No X-server restart.

(I noted that the "xsetwacom get "Wacom..." Button1" returns "1" instead
of "CORE KEY a" as it used to do. But, I don't mind this as the
assignment is working here....)

So I conclude that the X-server does not restart as initially reported
in this bug. Hence, I will mark it as "Fix Released".

** Changed in: xf86-input-wacom (Ubuntu)
       Status: Incomplete => Fix Released

-- 
Wacom graphire4 pad buttons: remap cause X-server restart
https://bugs.launchpad.net/bugs/229694
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in ubuntu.