Hi everybody,

everything vmware-user works fine for me now, but when I start vmware-user in a terminal, I get:

GtK-WARNING **: In modul path "murrine" no theme engine could be found

This error message is repeated several times. Then comes

/usr/lib/vmware-tools/bin/xorg71/vmware-user: symbol lookup error: /usr/lib/libbonobo-2.so.0: undefined symbol: g_dgettext

This sounds serious enough to warrant an analysis. Do you agree? BTW: This is a stock 8.10 updated from a stock 8.04, latest update version. No fancy stuff installed, except MySQL and OTRS (www.otrs.org).

Any timely help is greatly appreciated. I'll post my vmxsock compile time error messages to the appropriate thread.

Thanx in advance

Jörg Maaß

Hi, Mark,

I installed a guest Ubuntu 8.10 in VMWare Server 2.0.0 running on Vista. When I went to install VMWare Tools, and got to:

But VMWare Tools doesn't seem to install on the Ubuntu 8.10 guest, when
I try to install the VMWare Tools on Ubuntu 8.10 guest it says "None
of the pre-built vmmemctl modules for VMWare Tools is suitable for your
running kernel. Do you want this program to build the vmmemctl module
for your system (you need to have a C compiler installed on your
system)?"

I just pressed <Enter> to accept the default <yes> answer. This worked for several of the modules, until:

The vmci module loads perfectly into the running kernel.
None of the pre-built vsock modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vsock module for
your system (you need to have a C compiler installed on your system)? <yes>
Extracting the sources of the vsock module.
Building the vsock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vsock-only'
make -C /lib/modules/2.6.27-9-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.27-9-generic'
CC [M] /tmp/vmware-config0/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config0/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config0/vsock-only/linux/util.o
/tmp/vmware-config0/vsock-only/linux/util.c: In function 'VSockVmciLogPkt':
/tmp/vmware-config0/vsock-only/linux/util.c:157: warning: format not a string literal and no format arguments
CC [M] /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyFromQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Detach" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Alloc" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyToQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config0/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-9-generic'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host. The rest of this software provided by VMware Tools is designed to work
independently of this feature. If you wish to have the VSOCK feature you can
install the driver by running vmware-config-tools.pl again after making sure
that gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution's
installation CD.
<Press the Enter key to continue.>

So, I press <Enter>, and the VMWare tools installer asks me about screen resolutions, and then does some other things, and then finally it summarizes:

Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Guest filesystem driver: done
Mounting HGFS shares: failed
Guest memory manager: done
Guest vmxnet fast network device: done
VM communication interface: done
Blocking file system: done
Guest operating system daemon: done
The configuration of VMware Tools 2.0.0 build-122956 for Linux for this running
kernel completed successfully.
You must restart your X session before any mouse or graphics changes take
effect.
You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.
You will need to either manually start /usr/bin/vmware-user or log out and log
back in to this desktop session to obtain the following features: guest
resolution fit, drag and drop, and file and text copy/paste. vmware-user is
configured to automatically start at a graphical login, but that won't take
effect until the next login.
To use the vmxnet driver, restart networking using the following commands:
/etc/init.d/networking stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/networking start
Enjoy,
--the VMware team

For those last commands, related to networking, I prefixed each command line with "sudo ", to run the command as an administrator.

Richard

After 12 1/2+ hours, I've finally found a solution, and finally got everything working under Ubuntu 8.10 guest OS.

For more detailed instructions (step by step) on how to get VMWare Tools working on Ubuntu 8.10 Guest OS, you can look at the following links:

I created a small tutorial here:

http://communities.vmware.com/message/1129103#1129103

A post by Mufasa in this link helped as well:

http://communities.vmware.com/message/887802#887802

This link was very useful as well:

http://laurentbois.com/2008/04/26/install-ubuntu-804-using-vmware-fusion-on-mac-os-x/

The one single link that helped the most by far was found here on the Ubuntu forums:

http://ubuntuforums.org/showthread.php?t=987631

Keep in mind that if you are running a x86 (32-bit) version of Ubuntu 8.10, then the files you need to download and use are different than the instructions on the Ubuntu forums. So look over the instructions on the Ubuntu forums (if you are using a 64-bit version of Ubuntu 8.10 guest OS), but if you are installing VMWare Tools on a 32-bit version of Ubuntu Guest OS then follow the very first link up at the top of this post, or the link here below:

http://communities.vmware.com/message/1129103#1129103

That should be enough to help you (step by step) get the VMWare Tools installed and running on Ubuntu 8.10 Guest OS (32-bit or 64-bit).

Mark

Richard,

I'm not sure about the "Theme Engine Module path" problems you are having. You may want to post this as a new Question in a separate thread (as an "Unanswered Question") and then cross-link in your new post back to this post, just for reference. I would probably just create a completely new post called "Theme Engine Module Path Problem with VMWare Tools in Ubuntu 8.10"

Something very easy for someone to find and do a keyword search on. Again, I don't work for VMWare, I'm just a "Community User" that is stumbling through the installation process as well. I would really need a bit of a clue from the VMWare Developers as to what is going on in your particular instance with the "Theme Engine module path" problem.

Maybe a VMWare Developer could chime in, and possibly offer a clue. I do apologize, but I didn't run across that problem (on a clean vanilla Ubuntu 8.10 LAMP Server install). So I'm not sure as to what the fix is for your path problem, but hopefully one of the VMWare Developers could help a bit more with the problem that you are having. At least you got the VMWare Tools installed! That's a good *first step*!

Mark

P.S. Please do post back your "fix" or "solution" if you ever do find a solution to the problem, just so that we have it here in the Community forums for "archival" purposes just in case anyone else runs into the same problem. I always try to post a detailed problem, and a detailed solution, just so the search engines can pick it up (and index it) for archive purposes. This way if anyone runs into the same problem with VMWare in the future, hopefully it will help them as well. Thank-you!

Alfredox,

I created a small tutorial here:

http://communities.vmware.com/message/1129103#1129103