Ticket #11665 (closed defect: obsolete)

Opened 4 years ago

Last modified 5 months ago

Mouse in guest OS has strange behavior on MAC OS X

Reported by: nim Owned by:
Priority: major Component: other
Version: VirtualBox 4.2.10 Keywords:
Cc: Guest type: all
Host type: Mac OS X


This problem has been there for some time during past several minor releases.

After several times of suspending/resuming, the mouse wheel function in guest OS behaves like that I pressed BACK button. The result is that when I scroll the mouse wheel, eg in Windows Explore or Linux File explore, the previous folder is scrolled into view. This also happens similarly in development tools I use daily.

I highly doubt that this is caused by close the host MacBook lid and open it.

There is one workaround - I have to suspend guest OSes, do logout and login, and resume the guest OSes; then the mouse works fine.

Change History

comment:1 Changed 4 years ago by michael

I take it you mean "several times of suspending/resuming" your host system. Do you have any software or settings on your host system which might be affecting mouse button mappings? And by "suspend guest OSes, do logout and login, and resume the guest OSes" do you mean save the guest states then log out of your user account on the host system? If so does it work without that last stage?

comment:2 Changed 4 years ago by nim

Sorry for my bad English. What I meant was:

  1. About suspending/resuming - suspending/resuming the *guest* OS. But after reading your comment, I think maybe it's also related to the host system which is MAC OS X 10.8.3 running on a MacBook Pro.
  1. Logout - Suspend the guest OS, logout my account on the host system.
  1. The weird mouse behavior only appears in the *guest* OS.

Hope this makes everything clear.

comment:3 Changed 4 years ago by nim

What dod you mean by "If so does it work without that last stage"?

Last edited 4 years ago by nim (previous) (diff)

comment:4 follow-up: ↓ 5 Changed 4 years ago by michael

I meant whether the work-around worked without the additional host logout - I take it after your clarifications that that is not the case. By suspending and resuming the guest OS, do you mean saving its state or telling the guest to suspend?

comment:5 in reply to: ↑ 4 Changed 4 years ago by nim

I mean saving VM state by suspending/resuming.

BTW, I don't get this mouse problem on Windows 7.

comment:6 Changed 4 years ago by michael

And how does closing the Mac lid come into this? Is that in addition to saving the guest states? Does this happen for a single guest or for several running simultaneously?

comment:7 Changed 4 years ago by nim

I think closing the lid also plays some part in the issue.

I usually run several guests simultaneously. But as long as I don't close the lid or sleep the Mac, the issue does not occur.

comment:8 Changed 4 years ago by michael

I'm afraid that I am having some difficulty grasping what is and what isn't happening here. Perhaps you could try observing this, and when you see it make a note of everything interesting you have done between the last time you saw the guest working correctly and the point when you saw that the guest was not working correctly? I would also be interested to know whether it occurs for several running guests simultaneously, or whether it can affect one running guest at a particular time but another not.

And have I understood correctly that when you see this issue, to work around it you have to suspend that guest, log out of your host (not reboot), log back in again and resume the guest? And that if you just suspend and resume the guest it doesn't help?

If you have trouble answering immediately please feel free to take a bit of time to observe.

comment:9 Changed 4 years ago by michael

See also ticket #11737.

comment:10 Changed 4 years ago by michael

Please take a look at my latest update on ticket #11737. It would be nice as well if you could attach a log file to this ticket (I am particularly interested to know whether you are using PS/2 or USB mouse emulation in the guest, which is one of the things the log file will tell me).

comment:11 Changed 3 years ago by nim

I have not had this problem for a long time. Please close this ticket.

comment:12 Changed 3 years ago by frank

Thanks for the feedback!

comment:13 Changed 5 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use