tc1100 stylus buttons regression

[This is an automatic notification.]

Hi MyR,

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 573275

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 573275 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/573275

This was reported in Lucid.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

The source code that needs to be changed was already included and working properly in 9.10! It was presumably left out by accident; there is no other problem to diagnose.

The patch should probably be pushed upstream if possible. Can someone do that or tell me how?

Heya,

If you're still around you may want to look at this:

https://wiki.ubuntu.com/Bugs/Patches

Any news on this ?

Here's the patch

OK, so the patch doesn't quite work... that is that patch from Ubuntu 9.10.

Can you make it work?? I don't have any experience programming in C.

This patch is a little better but still doesn't work.

Now the buttons are giving me a:

MotionNotify event, serial 33, synthetic NO, window 0x3200001,
    root 0xfc, subw 0x0, time 161661, (76,26), root:(77,79),
    state 0x0, is_hint 0, same_screen YES

in xev

MyR, hmm yeah it looks like that patch got dropped somewhere along the line, but it's not clear why/when/how.

Unfortunately, the codebase has changed quite a bit since that patch was made, and it no longer applies.

I've taken a shot at rewriting the patch for the current codebase (well, as of natty), but I need you to test it to verify I've ported things properly. I've packaged it up in a PPA so it's easier for you to test. The PPA is here:

  https://launchpad.net/~bryce/+archive/jackfruit

If that restores the functionality for you, please report back here.

Thank you! thank you! thank you!! I will test it as soon as the package builds...

Thank you again for trying. However the package you made causes a crash every time a stylus button is clicked probably because of "xf86WcmEvent(common, 0, ds);". Otherwise the one you made is identical to my effort (posted above).

I guess we're both on the right track, but it still doesn't work. It doesn't seem to be sending the right event. Xev gives a MotionNotify event instead of ButtonPress when clicking the button. Any ideas or guidance for debugging would be very much appreciated!

Well I reapplied the patch I created and it's a little different than last time (due to xserver updates?). Now pressing the stylus button returns the cursor to the place it was before using the stylus.

I mean the cursor returns to the last spot it was while using the stylus, even though I moved it the the built-in mouse.
Sorry for all the messages.

I guess unless you spot the error to make it work right, probably the next best step would be to forward this issue upstream, to bugs.freedesktop.org.

...or to the wacom driver mailing list.

Alternatively, please collect a full backtrace from the crash and maybe I can decipher what's gone wrong.

See https://wiki.ubuntu.com/X/Backtracing for directions on collecting a full backtrace. Skip over the bits about apport and use the gdb method.

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.

Status changed to 'Confirmed' because the bug affects multiple users.

Using LUbuntu Precise (12.04) on my TC1100.

Using the stock install, there is absolutely no response whatsoever from the system when I trigger the three stylus buttons. Not when I cat /dev/input/*, nor out of xev.

I manually applied the second wcmISDV4.c.patch file listed under patches on the right. It *LOOKS* like the only difference between it and the other copy is that the second one contains the diff command on the first line. But I have to admit that I haven't diffed them to be certain. The position in the file is considerably offset from when the patch was originally generated. (new code inserted at line 787)

dpkg-buildpackage execution completed with non-error status.

Install the newly generated package and restart X. /dev/input/* still do not twitch when I trigger the buttons.
HOWEVER, when I run xev and trigger the buttons from top to bottom (or right to left, depending on the orientation of the screen) starting from rotate, I get:

MotionNotify event, serial 41, synthetic NO, window 0x2200001,
    root 0x152, subw 0x2200002, time 308508, (35,41), root:(57,334),
    state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 41, synthetic NO, window 0x2200001,
    root 0x152, subw 0x2200002, time 325562, (35,41), root:(57,334),
    state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 41, synthetic NO, window 0x2200001,
    root 0x152, subw 0x2200002, time 333829, (35,41), root:(57,334),
    state 0x0, is_hint 0, same_screen YES

----------
So, needless to say, I'm getting input, so it's an obvious step in the right direction, but I can't tell the three button presses apart from each other. I'm looking into what I need to do next to make the buttons useful, finally.

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".