double mouse cursor after installing 4.1.2
Posted: 19. Sep 2011, 16:14
I just upgraded to 4.1.2 on an OS X host and also installed the 4.1.2 extension pack. I have a Snow Leopard VM and a Leopard VM. On running either one I see two mouse cursors, one for the VM and one for the host. When the cursor is precisely in the center of the VM window, the cursors coincide. But as I move left from center, the VM cursor moves faster than the host cursor and thus I see two, the VM cursor to the left of the host cursor. Similarly in the right half of the window the VM cursor is to the right of the host. The same effect occurs in the vertical.
Before 4.1.2 I had noticed that when I moved the cursor from within the VM window to outside the VM window, the cursor stopped at the window boundary and it took extra movement before the cursor actually moved outside the window. This is consistent with the 4.1.2 cursor behavior in that the VM cursor gets to the boundary before the host cursor and thus the stall before the host cursor exits. The difference between 4.1.2 and before is now the host cursor is visible whereas before it was not.
I tried changing the mouse tracking setting in Preferences but this had no effect.
Is anyone else seeing this behavior? Any suggestions about how to fix this? Thanks.
Note: I also have an Ubuntu VM and this problem does not occur there.
Before 4.1.2 I had noticed that when I moved the cursor from within the VM window to outside the VM window, the cursor stopped at the window boundary and it took extra movement before the cursor actually moved outside the window. This is consistent with the 4.1.2 cursor behavior in that the VM cursor gets to the boundary before the host cursor and thus the stall before the host cursor exits. The difference between 4.1.2 and before is now the host cursor is visible whereas before it was not.
I tried changing the mouse tracking setting in Preferences but this had no effect.
Is anyone else seeing this behavior? Any suggestions about how to fix this? Thanks.
Note: I also have an Ubuntu VM and this problem does not occur there.