xinput clients receive input even when the window manager is getting mouse input

[Vincenzo Ciancia]

Binary package hint: xorg

If I use gimp or xournal with my tablet, and drag their windows using alt+tablet stylus (as if it was alt+mouse1click) they still receive input while I drag the window, resulting in messed drawing over my work.

[Timo Aaltonen (tjaalton)]

Do you have this problem with 7.10 or Hardy alpha3?

[Vincenzo Ciancia (vincenzo-ml)]

I am now using gutsy and I still have this problem.

[Timo Aaltonen (tjaalton)]

What driver does the stylus use? Seems to be a bug on the driver, or the xserver.

[Vincenzo Ciancia (vincenzo-ml)]

The driver is xserver-xorg-input-wacom but I am unsure it is not a general bug of xinput - or even of the window manager which is capturing alt+click (in any case this happens both with metacity and compiz).

[Timo Aaltonen (tjaalton)]

Can you get a screenshot of the problem so that I'll understand it better. Is it like if the cursor is left to the position where you started the alt-dragging?

[Andrew Stromme (astromme)]

This happens to me too. On gutsy, it would draw long lines all over my paper and on Hardy (snapshot 01-21-08) it makes a big blob where I initially put my mouse down.

(Also, where would I report a bug in what seems like XInput? You'll see on the screenshot that my pen marks are all messed up and blocky. They were NOT like this with Gutsy and linuxwacom-0.7.8. Same version of Xournal and it happens with all programs.)

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Vincenzo Ciancia (vincenzo-ml)]

This is still the same in intrepid ibex alpha 5.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Vincenzo,

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 82110

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

[Bryce Harrington (bryce)]

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.

[Vincenzo Ciancia (vincenzo-ml)]

Dear Bryce,

the problem still occurs in Lucid, but only for mouse scroll events. This can be easily verified by opening xournal, enabling Options->Use xinput and then, over its main window, press Win+mousewheel to use compiz. If the scrollbar in xournal is visible (that is, if the document /can/ actually scroll), it will scroll.

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for posting this bug.

Does this issue occur in Maverick?

[Vincenzo Ciancia (vincenzo-ml)]

Yes.

[Vincenzo Ciancia (vincenzo-ml)]

When I reported this bug first, I didn't know very well how bug worked. Therefore I didn't forward upstream myself. That's the only sane thing that can be done to such a bug - it's 2 years old. So someone please report upstream.

I will instead unsubscribe, because of Bug #405350 and my decision to stop cooperation which was consequential.

[Daniel Polehn (dpolehn-gmail)]

Can we get this either confirmed to still be an issue or fixed?