Additions in 3.1.2 say they are 3.1.1, no mouse integration

[giorgio42]

Hi,

anybody else seeing this ? (more info later).

Cheers,
Georg

[SSCBrian]

The guest additions reporting the wrong version number is a known issue.

However, the lack of mouse integration is not. I'm not having any mouse integration problems with mine, what's your host platform and what version of Solaris are you running?

[randshuntzinger]

I am running OpenSolaris developer build 130 and I had a problem with mouse integration. It looks like the OpenSolaris update to build 130 removed the /usr/X11/lib/modules/input directory (and its contents). When I removed the old guest additions and attempted to reinstall I got the following message:

... lots of stuff ...
VirtualBox guest kernel module loaded.
Creating links...
Configuring X.Org...
cp: cannot create /usr/X11/lib/modules/input/vboxmouse_drv.so: No such file or directory
cp: cannot create /usr/X11/lib/modules/input/amd64/vboxmouse_drv.so: No such file or directory
Configuring client...
ERROR: attribute verification of </usr/X11/lib/modules/input/amd64/vboxmouse_drv.so> failed
pathname does not exist
ERROR: attribute verification of </usr/X11/lib/modules/input/vboxmouse_drv.so> failed
pathname does not exist
Configuring service...
Updating boot archive...
Done.
Please re-login to activate the X11 guest additions.
If you have just un-installed the previous guest additions a REBOOT is required.
Installation of <SUNWvboxguest> was successful.

Note thet the problem is that the directory where the mouse driver gets linked in missing. I created the input and input/amd64 directories and reinstalled the package. After doing that, it worked. I am not saying that this is the "correct fix", only that after doing so I got it to work. The workaround may get backed out with the next OS update for all I know.

For the record. The initial symptom I saw after the upgade was that the X11 display would try to start, fail, try again, etc. The clue was in the Xorg.0.log file, which indicated that the mouse driver couldn't be found.

Hope this helps.

-- Rand

[giorgio42]

Rand,

thank you very much for the tip. I will try the work around as soon as I can (actually tried right now and after several additional reboots, things are working again).

The issue makes me wondering what the the mode of cooperation is between OpenSolaris and VirtualBox developers.

Cheers,
Georg

[Ramshankar]

Hmm, I will look into this ASAP. Thanks for the report.

As for the version number being incorrect it was due to incorrect time in the build VM of the additions that caused this inconsistency. This will be addressed and is minor as only the version number on the package is wrong, the actual additions is 3.1.2 binaries. The mouse integration breakage with 130 is far more serious problem, we will try resolve it soon.

[evenson]

The same problem persists in snv_131.

I tried manually creating a directory to place the mouse driver, but the SUNWvboxguest installation reported that it failed to attach the kernel module.

[loukingjr]

having the same issue of course. 2010.3 snv_131

[rbuick]

I've just upgraded from snv_111b to snv_131, unfortunately it wouldn't boot to graphical login.
logging as normal user at the command prompt and typing:

startx

comes up with the attached.

[wfiveash]

I've just upgraded from snv_111b to snv_131, unfortunately it wouldn't boot to graphical login.
logging as normal user at the command prompt and typing:

startx

comes up with the attached.

I think this is a OpenSolaris bug. Check out this page: http://hub.opensolaris.org/bin/view/Main/discussions
for ideas as to the appropriate forum/mail list to find out about your issue.