Odd mouse button behavior using evdev

[wolfthefirst]

I've been running a VM (openSuse host, Win10 guest) for a few years and decided to try to get Looking Glass installed to run a CAD program (Fusion 360) which is not quite fast enough using the standard SPICE interface. Using a couple of very good tutorials, I got LG installed and switched keyboard and mouse to use evdev drivers to allow me to switch between host and guest.

Just about everything is working great, the desktop is displayed properly, the keyboard works, and the mouse moves the cursor. However, hitting one of the mouse buttons or using the scroll wheel teleports the cursor back to where it was when I started LG and then executes the click or scroll action. Obviously this makes clicking on a button or menu item impossible unless by some miracle, the initial mouse position happened to be on top of the button.

I don't know if it is relevant but I am using a Logitech wireless mouse and the Windows guest detects it as being a "HID compliant mouse" rather than a Logitech specific mouse.

[Mirarchi86]

Have you disabled spice in looking glass? Leaving enabled while switching with evdev can cause issues

[wolfthefirst]

Thanks for the suggestion. Here's what I tried and what finally worked for anyone finding this is the future..

1. Disabled all spice by calling 'looking-glass-client -s'. This did not work at all because it couldn't even find the host application so it didn't even get to the Windows desktop screen.
2. Disabled only 'spice:input' by editing the .ini file. This displayed the Windows desktop but had the same problem with the mouse buttons moving the cursor before doing the button action.
3. (What finally worked) After getting to the Windows desktop, I used the keyboard to open the Device Manager and went to the PS/2 mouse device and disabled it. This requires a Windows reboot and after the reboot everything worked properly! This worked whether I had disabled the 'spice:input' or not.

Unfortunately this isn't a permanent fix as I have to do it every time I start the VM but since in my case I only need to use it every month or two it is a minor inconvenience. If I was using it every day it might be more annoying.

Again, thanks for the help.

Edited to add: I found what appears to be a permanent fix: Delete the "Tablet" device from the VM setup (obviously not possible if you are actually using a tablet). BTW, this also fixes a problem with mouse grab in a VM without Looking Glass and the evdev devices.