virtualbox.org

Hi,

I've been using Virtualbox (version 2.1.0) recently trying out some things.
I'm bumping into this very annoying problem: after a while (I don't know what triggers is) my mouse won't work anymore.

My guess is it has something to do with the kernel being recompiled for virtualbox.

It's indepentent of the guest operating system: I have it both when I install Ubuntu (server or desktop) or Windows XP.
As far as I can see, it's pretty system-wide: it happens in Ubuntu 8.10 32bits and Ubuntu 8.10 64bits (as host)

When launching Virtualbox and running a virtual system, it happens pretty quickly. When I just launch Ubuntu 8.10 Server (32bits) without logging in, I don't seem to get into trouble that fast. But as soon as I log in, even in text mode and get some activity (sudo pica textfile), after a while, when releasing the mouse (right-ctrl), it actually shows in my host system ... the pointer moves around perfectly... but it doesn't react to any clicking.

This occurs both with my Logitech mouse and my Wacom tablet.
This occurs when using both version 177 or 173 from my nVidia display driver.
This occurs using both 64 and 32 bits version of Ubuntu 8.10

(just now - I only opened Virtualbox to view the exact version of Virtualbox, then closed the program again - I lost mouse control again.

When I log off and back on, I have mouse again.
When I switch users (but remain logged in), it isn't solved.

I'm using just the default settings when creating a virtualbox... (just add PAE for Ubuntu server)

I hope someone recognizes this problem and knows how to solve it (or can ask me some sensible questions as where to start looking)

If the device stops responding, check if the light of the mouse is still on (applies only to optical mouses, no old fashioned ball mouse or new laser mice). If it's off, then something shut down your USB mouse. Check your syslog and dmesg (/var/log) for more info. You can also check kern.log for some kernel info about your mouse or USB. What happens if you unplug the mouse and plug it back in (USB only).

Thanks for looking into this...

The mouse is still working: the pointer moves on the screen (and over some areas it even changes shape: over the "plasmoid" it's the text cursor - over the panel it's the arrow cursor)

So the mouse still works. Only thing not happening is actions connected to clicking (opening file, pushing button, scrolling down, changing focus, etc...

If I unplug the mouse and plug it back in ... the problem remains. I also tried that.

same problem here...

I can move the mouse pointer but no reactions on Mousebutton clicks in
Host and Client

The problem always shows if the VM is running 3-4 hours and affect the host, too.

Host: Ubuntu 8.10 Intrepid Ibex , Virtualbox 2.1.0
Guest: Win2000 and WinXP

is there a solution out there ?

P.S. I tried to replace the VirtualGuestAdditions with a older Version (2.0.0)
but same problem here

Hi,

since I'm not knowledgeable to solve it, all I can do is add extra information:

I've got Ubuntu 8.10 Server installed in a virtualbox too.

If this one is launched - but I don't actually do stuff in it - it keeps working well.
If I log in (text mode, afaik there are no VirtualGuestAdditions to be installed here) and use it for a while, I also get the mouse losing it's button-functionality.

For me this means it has nothing to do with the additions being installed or not, and it doesn't mean having Windows running in a VBox either (I do not know if have Windows "just installed" on a different virtualbox - without it being launched - could affect this, but I severely doubt it)
This bug happens much quicker, I must admit, when I'm launching my Windows box than when launching another (f.e. Linux Mint) box.

I am also having this issue running xp as a guest on a Fedora 9 host. I noticed another strange thing that I don't think has been mentioned here.

Even when I have released my mouse and keyboard from the guest, if I press alt to try to get a drop down menu from the VB window, the drop down for whatever window is active in the guest activates. It's almost as if the guest is not releasing the mouse or keyboard functionality completely. Then, of course, if I close the VB window all together the mouse button functionality still does not come back.

I have found a workaround and perhaps a potential culprit. I use a dual display. When I was having the problems described here, I had my display configuration set up the through Nvidia's display configuration utility to use "Seperate X screen". I changed that to TwinView and I haven't had a problem with the mouse since. This includes using VirtualBox which before immediately caused the mouse problem.