Incorrect or lost input device events

[BlackenedSky]

What is happening:

Since an upgrade to Jaunty (both via dist-upgrade and complete fresh install), after some time input events will begin to malfunction. For example, the 'super' key will cease to function, and mouse clicks will not match the current pointer position.

Expected behavior:

Keys carry on responding, and mouse click events are fired off with the correct co-ordinates, matching the current pointer position.

How to reproduce:

Unsure, as it is unclear what causes the behavior. HAL is running and a restart has no effect. A restart of the x-server (either gdm restart or via xerver kill hotkey) solves the issue until the next time it happens.

Other observations:

- Sometimes hotkeys will fail to function as well, such as alt+space, alt+tab etc. At the same time other hotkeys such as alt+f2 and multimedia keys (e.g. volumne up/down) will still function.
- When mouse clicks do not match the pointer position, they remain 'stuck' at the same co-ordinates of the last successful click. While the mouse cursor still moves, the location of the click events does not. Also, hover events fail to fire off except for those which occur within the same window control (e.g. address bar, text area, dialog) as that which is receiving the click events.
- This occurs with compiz both enabled, and disabled
- No logs show any errors (syslog,dmesg,Xorg.0,messages,debug) about any failures or errors at the time inputs malfunction.
- The recent kernel update (9th May) had no effect on the issue
- The input devices are USB decives. In my case, it is a wireless mouse/keyboard combination
- Hotplugging the receiver into either a new or same USB port does not resolve the issue
- The malfunctions did not occur in Intrepid, only in Jaunty
- A right click on the control(i.e. desktop/tab/panel/address bar) temporarily resolves the mis-alignment of click events, but this only lasts for 1 click, and requires that a content-menu is available at that location which is still receiving the events.

[BlackenedSky (caffeine-lord)]

After doing some more in depth searching, this appears to be a regression of bug #296167 . However, I am not using xinerama or twinview - I only have one monitor currently connected to by dual-head card.

Also see the following bug reports of the same issue:
https://bugs.launchpad.net/ubuntu/+bug/296167 (mentioned above)
https://bugs.launchpad.net/ubuntu/+bug/296118
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-mouse/+bug/290406
https://bugs.launchpad.net/ubuntu/+bug/362359

Some bugs also link to other bugs reporting the issue.

[Peter Leonard (pete-peteleonard)]

Former victim of bug #296167 here - this was fixed in 8.10 a few months ago. Upgraded to 9.04, and I'm seeing it again. Dual screen + Xinerama setup. Follow the previous thread for more info.

[Michiel Tukker (michiel-tukker)]

I can confirm this bug (exactly the same symptoms). I've tried several 'solutions' from other bug-reports, but no joy...

However, I read in the comments on bug #362359 (this comment: https://bugs.launchpad.net/ubuntu/+bug/362359/comments/29 ) that the bug was first noticed after installing a tablet. I unplugged my Wacom tablet, restarted X and everything is working again.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid or Maverick packages ?
Tanks in advance.

[Fabio Marconi (fabiomarconi)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Peter Leonard (pete-peteleonard)]

On 08/26/2010 04:07 PM, Fabio Marconi wrote:
> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Could you please provide the requested
> information? Thanks!
>
>
So since upgrading to Lynx, I have not seen the bug as described.

With that, I'm still having some issues with X, but I suspect the NVidia
drivers + Xinerama are the problem. Will create a new bug if I can
track it down better.

[Fabio Marconi (fabiomarconi)]

Thanks for the reply
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.