Been experiencing the same thing here. I lose the ability to click whenever I switch from the VNC viewer to say Firefox (so I can watch some SpaceInvader One ) and back to the VNC viewer. Keyboard input is still functioning.
This is happening with:
VNC Viewer 6.18.907
Tiger VNC 1.9.0
Unraid's browser based VNC viewer
VM logs from Unraid show a long string of:
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
**Update**
I am losing the mouse after applying some changes inside the Windows VM. This last time, I lost the mouse after enabling networking in Windows 10 so that I can access the user shares on the array.
2018-10-25 07:40:33.079+0000: Domain id=9 is tainted: high-privileges
2018-10-25 07:40:33.079+0000: Domain id=9 is tainted: host-cpu
2018-10-25T07:40:33.123658Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
Web search turns up:
Bug 1611984
qemu prompt "qxl_cursor: not implemented: type 1" when boot Win2008R2 guest
reported: 2018-08-03
https://bugzilla.redhat.com/show_bug.cgi?id=1611984
And:
https://patchwork.ozlabs.org/patch/965487/
Monochrome cursors are still used by Windows guests with the
QXL-WDDM-DOD driver. Such cursor types have one odd feature, inversion
of colors. GDK does not seem to support it, so implement an alternative
solution: fill the inverted pixels and add an outline to make the cursor
more visible. Tested with the text cursor in Notepad and Windows 10.
cursor_set_mono is also used by the vmware GPU, so add a special check
to avoid breaking its 32bpp format (tested with Kubuntu 14.04.4). I was
unable to find a guest which supports the 1bpp format with a vmware GPU.
The old implementation was buggy and removed in v2.10.0-108-g79c5a10cdd
("qxl: drop mono cursor support"), this version improves upon that by
adding bounds validation, clarifying the semantics of the two masks and
adds a workaround for inverted colors support.
Looks like the bug was patched and the commit pushed through September 3–5, 2018. I guess now we wait for Lime Tech to push through the update? Not sure how it works on their end. Either way we the end users will have to wait.
Fingers crossed.
**Update**
Using a RDP like Splashtop, the mouse works fine from the client and also from any USB mice that are pushed through to the VM.