Ibex and VMware server g_thread_gettime error

[monarialx]

I've replaced some libraries under /usr/lib/vmware-server-console/lib with older ones (taken from Hardy).
- libglib-2.0.so.0
- libgmodule-2.0.so.0
- libgobject-2.0.so.0
- libgthread-2.0.so.0
- libXrender.so.1
- libgio-2.0.so.0 <== NEW
- libX11.so.6 <== NEW
I also patched /usr/lib/vmware-server-console/lib/wrapper-gtk24.sh to preload the NEW ones.

Now with

VMWARE_USE_SHIPPED_GTK="force" vmware-server-console

everything works again.

More details and files to download here.

HTH

[tvrtuscan]

Thanks monarialx that worked for me!!!

Had to change it a little for vmware rather than vmware console but I'm back up and running again now.

Nice one

[greldinard]

monarialx - thank you very much!
You were patient enough to sort it all out.
It works fine!

[willamowius]

The fact the sudo vmware works led me to a much simpler solution (and safer than the sudo):

Its enough to just

unset GTK_RC_FILES
unset GTK2_RC_FILES

I put that into a little script that starts vmware and everything is jolly fine again.

[tomeast]

Thanks willamowius! You're solution worked for me.

[drumz]

None of the other solutions worked for me except running it with:

sudo vmware

Since that worked that indicated it was either a permission issue or environment.

In my home directory over time I eventually issued these two commands:

rm -rf .vmware
rm -rf .gnome*

That did it for me, I can run it without getting the g_thread_gettime error. Please note that I'm a KDE user but I do have gnome installed so for those of you using Gnome you may just want to try removing the .vmware directory first, then if that doesn't work try moving the .gnome* directories someplace else.

Unfortunately I hadn't picked up on a permission error on my .vmware directory after running vmware with 'sudo vmware' so I went and just removed the .gnome* directories which may _not_ be necessary.....

[rmi]

roxius solution worked for me (sudo vmware).

therefore, the way to solve this problem, was to change the permissions of that library to 666 (rw for everyone). note that libgio-2.0.so.0 is probably just a symbolic link to a different file, in my case libgio-2.0.so.0.1800.2, and the permissions of the file the link points to are the ones that have to be changed.

that means, a possible permanent solution for everyone with that library error is:

sudo su
cd /usr/lib32/
ls -la

and check what file libgio-2.0.so.0 points to, it will be called <lib> in the following

chmod 666 <lib>
exit

hope that helps

[anandvaidya]

Hi All,

I'm running Kubuntu Jaunty 9.04 Alpha6 + updates.

I have vmware-server 1.0.8. I have used vmware-update-2.6.27-5.5.7-2 package to complete vmware installation. I had the same problem reported here ( ie. /usr/lib/vmware/bin/vmware: symbol lookup error: /usr/lib32/libgio-2.0.so.0: undefined symbol: g_thread_gettime)

I followed monarialx method and works fine for me.

briefly:

I have my old 8.10 working copy of vmware in /mnt/usr/lib/vmware/

as root:
cd /usr/lib/vmware/lib/
rsync -av /mnt/usr/lib/vmware/lib/libglib-2.0.so.0 .
rsync -av /mnt/usr/lib/vmware/lib/libexpat.so.0 .


as user:
export VMWARE_USE_SHIPPED_GTK=force; vmware

it spews tons of errors (ld.so complaining, but UI starts up)

I just wanted this to be documented here for Jaunty Jackalope 9.04

[locutus42]

Hi All,
<clip>
briefly:

I have my old 8.10 working copy of vmware in /mnt/usr/lib/vmware/

as root:
cd /usr/lib/vmware/lib/
rsync -av /mnt/usr/lib/vmware/lib/libglib-2.0.so.0 .
rsync -av /mnt/usr/lib/vmware/lib/libexpat.so.0 .


as user:
export VMWARE_USE_SHIPPED_GTK=force; vmware

it spews tons of errors (ld.so complaining, but UI starts up)

I just wanted this to be documented here for Jaunty Jackalope 9.04

You are da man! worked great and without any spewing errors for the vmware-server-console v1.0.4. FWIW, after seeing what Vmware v2 is like, I'll do what it takes to keep the 1.x stuff running.

Thanks tons.