https://bugs.kde.org/show_bug.cgi?id=283130

[Cyrille Berger Skott]

On Tuesday 08 November 2011, Boudewijn Rempt wrote:
> > going to do switcheroo from mouse to pen stylus  (id:  0 )  
> > going to do switcheroo from pen stylus  (id:  0 )  to eraser
> > stylus  (id:  0 )   going to do switcheroo from eraser stylus  (id:  0
> > )  to pen stylus  (id:  0 ) going to do switcheroo from pen
> > stylus  (id:  0 )  to eraser stylus  (id:  0 )
> >
> > 
> >
> > This is the same on Ubuntu:
> > 
> >
> > going to do switcheroo from  to  
> > going to do switcheroo from  to  
Hum...

We are either facing a but in xinput2, in qt/xinput2 or in the wacom driver. 
If it were not for the report of a problem in gimp/painter, I would have 
blamed qt/xinput2...

It might be tricky to know exactly where it is. There is a utility called 
"xinput" (in the xinput package on ubuntu/debian, not sure for opensuse), if 
you run "xinput list" you should get something like:

⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=10   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                     id=11   [slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet eraser                id=13   [slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet touch                 id=14   [slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet stylus                id=15   [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)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=9    [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=12   [slave  keyboard (3)]
    ↳ ACPI Virtual Keyboard Device              id=16   [slave  keyboard (3)]

If it does not, then it is either a bug xinput or the driver.

Then to know if the problem is in Qt/xinput2, an other possibility is to 
compile a clean/unpatched qt, and check if it works or not.

-- 
Cyrille Berger Skott