[Touch-packages] [Bug 1519082] Re: Left mouse bottom stops working

2015-11-24 Thread path
Chris, I tried using a different kernel and an older installation. The left mouse button error occurred again in each case. I connected this keyboard and mouse to a windows 10 system and the left mouse button stopped working at times yet again. Simply, this isn't a software bug at all. Let alone

[Touch-packages] [Bug 1519083] [NEW] Left mouse bottom stops working

2015-11-23 Thread path
Public bug reported: At times the left mouse events stop working. After a short moment the left mouse button starts working again. I'm using a Bluetooth mouse that connects to a dongle in a usb port. I was looking at the mouse events in three different test. As it turns out the mouse events

[Touch-packages] [Bug 1519082] [NEW] Left mouse bottom stops working

2015-11-23 Thread path
Public bug reported: At times the left mouse events stop working. After a short moment the left mouse button starts working again. I'm using a Bluetooth mouse that connects to a dongle in a usb port. I was looking at the mouse events in three different test. As it turns out the mouse events

[Touch-packages] [Bug 1519083] Re: Left mouse bottom stops working

2015-11-23 Thread path
*** This bug is a duplicate of bug 1519082 *** https://bugs.launchpad.net/bugs/1519082 I was trying to click the submit bottom? Since the report of 1519082, I booted into the 4.2.0-16-generic kernel. My left mouse button seems to work well so far. I guess the error is in the linux image

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

2015-11-22 Thread path
This is really hard to spot but if you keep clicking for a minute you'll notice that the /proc/interrupts doesn't does change when the mouse events stop appearing in the xinput test and /dev/input/mouse0 outputs. Add in a third terminal to my simple test frame work with this command: watch -d -n

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

2015-11-22 Thread path
I got the same problem. This appeared when I did an update in 15.04. I thought that upgrading to 15.10 would solve the problem. So on and so forth. I gave it a little test. If you know your mouse device in 'xinput --list' try to test it with xinput --test %id%' where %id% is your mouse device id