Ticket #7888 (closed defect: fixed)
Mouse stops moving when integration is enabled
| Reported by: | cortana | Owned by: | |
|---|---|---|---|
| Priority: | major | 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
-
missing mouse wintermute-2011-01-30-10-30-46.log
(54.2 KB) -
added by yrro 6 years ago.
- virtualbox log
-
Xorg.0.log
(29.0 KB) -
added by cortana 6 years ago.
- Xorg.0.log
-
xorg.conf
(109 bytes) -
added by cortana 6 years ago.
- xorg.conf
Change History
comment:2 Changed 7 years ago by yrro
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 Changed 7 years ago by michael
An Xorg.x.log and xorg.conf from the guest would also be helpful.
Changed 6 years ago by yrro
-
attachment
missing mouse wintermute-2011-01-30-10-30-46.log
added
virtualbox log
comment:4 Changed 6 years ago by cortana
FYI, both 'cortana' and 'yrro' are me. One is logged in in my host machine, the other in my guest VM.
comment:5 follow-up: ↓ 6 Changed 6 years ago by michael
Is this something that is always triggered after guest restore from a saved state?
comment:6 in reply to: ↑ 5 Changed 6 years ago by yrro
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 Changed 6 years ago by michael
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 Changed 6 years ago by cortana
I'm pretty sure it is, I attached the file right after I ran into the bug.
comment:9 Changed 6 years ago by michael
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 Changed 6 years ago by frank
- Status changed from new to closed
- Resolution set to fixed
No response, closing.
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?