Cursor Control in Ubuntu 10.04 alpha 1 workaround?

[loukingjr]

If anyone has a workaround to fix the host/guest cursor control that broke in Ubuntu 10.04 alpha, sure would be a help. And yes, I know what an Alpha means I'm typing on Ubuntu 10.04 alpha 1 now. works great except for the cursor issue.

[Perryg]

10.04 Mouse Integration was lost about a week ago just after a kernel update. I have not been able to track it down yet, but figure it was up to us to find it for our self since the OS is not anywhere near the place it needs to be for VBox to even want to figure it out. Of course I will pass along anything I find out

PS MI shows it is loaded and usable and so far no indications of it failing, it just does not work. Seamless is out of the question as you must use the host key to go in and out of the guest to host window.

[loukingjr]

thanks, I kind of figured it would be awhile. I just was all excited because 10.04 alpha 1 doesn't seem to have the same audio issues 9.10s do. one odd thing is, I tried VMware's Fusion 3.0.1 this morning and, near as I can tell, it doesn't have the "slow audio" issue with ubuntu 9.10s that VirtualBox does. It does have a host of other issues however. A least for $79.99 they throw in some problems lol

[Perryg]

As a temporary work around I have created an xorg.conf with the following in it. This should allow for MI until they get it all worked out.

As sudo:
1) create a file called /etc/X11/xorg.conf
2) add the following

Code: Select all

Section "InputDevice"
        Identifier  "VBoxMouse"
        Driver      "vboxmouse"
        Option      "CorePointer"
EndSection

This appears to work for me. However I would suggest that you also make a backup of the file in case the xorg.conf gets removed during the updates of the alpha.
Also this will require a reboot of the guest to take effect.

[loukingjr]

As a temporary work around I have created an xorg.conf with the following in it. This should allow for MI until they get it all worked out.

As sudo:
1) create a file called /etc/X11/xorg.conf
2) add the following

Code: Select all

Section "InputDevice"
        Identifier  "VBoxMouse"
        Driver      "vboxmouse"
        Option      "CorePointer"
EndSection

This appears to work for me. However I would suggest that you also make a backup of the file in case the xorg.conf gets removed during the updates of the alpha.
Also this will require a reboot of the guest to take effect.

that worked for me also. thanks, appreciate it

[3vi1]

Much appreciation to Perryg - That worked for me as well.

[dschlack]

The same thing happened to me only I'm using Ubuntu 9.10. Do you suppose this work around will work with Ubuntu 9.10?

[Perryg]

@dschlack,
It will not hurt to try. Make a backup of the original /etc/X11/xorg.conf it you have one and then either edit it or create it as shown above.
Just remember that if you make a mistake you will need to boot to the CLI to fix it (thus the reason for the backup).

[dschlack]

Thanks for the help, but unfortunately this work around didn't help. I can live with flicking the host key until a fix presents itself.

ds

[entelesis]

this worked for me with the alpha 3 release.

This problem has been identified as a confirmed bug-
https://bugs.launchpad.net/ubuntu/+sour ... bug/525558

with the following note:

Felix Geyer wrote on 2010-02-22:

The X Server in lucid switched from hal to udev input device auto-detection.
Unfortunately virtualbox doesn't yet provide an udev rule to handle the mouse integration.

hopefully, this will be addressed in the next release of vboxadditions - but it seems like it's simply a collision between the xorg plan to use hal instead of xorg.conf and the ubuntu plan to allow unloading hal. it seems to me to be desirable to unload hal on vm's, so we'll see how it plays out...

[decibyte]

A small workaround, as I just wrote in the Launchpad bug: I managed to get a cursor when I turned off Visual Effects in System > Preferences > Appearance.

[decibyte]

Oh, well... Adding the lines to xorg.conf was a way better idea. Now the seamless stuff also works.

[Perryg]

The fix is supposed to be in the next maintenance release.