VirtualBox

Opened 13 years ago

Closed 13 years ago

#7888 closed defect (fixed)

Mouse stops moving when integration is enabled

Reported by: Sam Morris Owned by:
Component: guest additions Version: VirtualBox 4.0.0
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

When I suspended my VM, then upgraded to 4.0.0 and resumed, I found that although I could move the mouse around while mouse integration was enabled, clicks always registered as if they were at the top-left pixel of the screen.

I shrugged, and rebooted.

Now, having used my VM for a while, it has happened again. The mouse cursor appears to move, but the guest always thinks that clicks occur at the same screen location.

xev reveals that no MotionNotify events are being sent by the X server. So I guess the communication between the X server and the MI mouse is being lost. If I disable MI then the PS/2 mouse works normally.

Attachments (3)

missing mouse wintermute-2011-01-30-10-30-46.log (54.2 KB ) - added by Sam Morris 13 years ago.
virtualbox log
Xorg.0.log (29.0 KB ) - added by Sam Morris 13 years ago.
Xorg.0.log
xorg.conf (109 bytes ) - added by Sam Morris 13 years ago.
xorg.conf

Download all attachments as: .zip

Change History (13)

comment:1 by Frank Mehnert, 13 years ago

Some more words about your guest: Which Linux version is that and which version of guest additions are installed? And could you please attach a VBox.log file of such a VM session?

comment:2 by Sam Morris, 13 years ago

I still had guest utils 3.2.12 installed. The guest uses Debian's 2.6.32-5-amd64 kernel.

I'll attach a log when I can reproduce this again.

comment:3 by Michael Thayer, 13 years ago

An Xorg.x.log and xorg.conf from the guest would also be helpful.

by Sam Morris, 13 years ago

virtualbox log

by Sam Morris, 13 years ago

Attachment: Xorg.0.log added

Xorg.0.log

by Sam Morris, 13 years ago

Attachment: xorg.conf added

xorg.conf

comment:4 by Sam Morris, 13 years ago

FYI, both 'cortana' and 'yrro' are me. One is logged in in my host machine, the other in my guest VM.

comment:5 by Michael Thayer, 13 years ago

Is this something that is always triggered after guest restore from a saved state?

in reply to:  5 comment:6 by Sam Morris, 13 years ago

Replying to michael:

Is this something that is always triggered after guest restore from a saved state?

No. It's very rarely triggered. I have only seen it when restoring from a saved state the first time I upgraded to 4.0; once, when restoring from a saved state saved with 4.0; and once more, while using the VM normally.

comment:7 by Michael Thayer, 13 years ago

Then I can assume that the Xorg.0.log file is not from a run of the X server in which this problem occurred?

comment:8 by Sam Morris, 13 years ago

I'm pretty sure it is, I attached the file right after I ran into the bug.

comment:9 by Michael Thayer, 13 years ago

If you can reproduce this with the following environment variable set on the host:

VBOX_RELEASE_LOG=+main.e.l3

you will get a lot (!) of additional information about mouse events in the log file. That might give us an additional clue. If I understood correctly from comment 6, you have also seen this happen when you hadn't just resumed a VM?

Of course, any recipe about how to reproduce this would be very helpful.

comment:10 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

No response, closing.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use