vmware server2.02 workaround for karmic 9.10

[sdowney717]

still working for 2.02 vmware server
there are 3 issues to get this to work like it should,

1. one is getting it installed,
2. the mouse issue where you must export the setting, so it uses vmware shipped version of gtk
3. make sure kvm modules are not loaded or the virtual machines will hang
4. setting up shared folders, you can use drive maping in the windows guest to see ubuntu host shares. Sharing windows files in the guest will let ubuntu host see them as well. setup the network as bridged


for the mouse and kvm module issue, simply make a text file named launchVM.sh and make it executable with this inside.
After you get your VM working in the wmware server from the browser, you can launch it at any time by running launchVM.sh and it will present a list of machines to start. The web browser does not have to be even running.

gksudo /etc/init.d/libvirt-bin stop
sudo modprobe -r kvm_intel
sudo modprobe -r kvm
#!/bin/bash
################################################## ##############################
# Call VMWare Server's Remote Console in a clean GTK setup.
################################################## ##############################

# Clean GTK setup for VMWare
export VMWARE_USE_SHIPPED_GTK=yes

# Find console executable in Firefox plugins.
vmrc="$(find "$HOME/.mozilla/firefox" -name vmware-vmrc -type f -perm -111 | tail -1)"
[ -x "$vmrc" ] || exit 1

set -x
cd "$(dirname "$vmrc")" && "$vmrc" -h 127.0.0.1:8333

for the installation issue

http://blog.mymediasystem.net/uncate...-koala-x86_64/

VMware-server 2.0.1 Installation HOWTO for Karmic Koala (x86_64)
October 10th, 2009 by acmelab68

I was trying to install the VMware server 2.0.1 x86_64 on my new Karmic Koala (Ubuntu 9.10, kernel 2.6.31-13) server, but I’ve got a bunch of errors. Looking for an any-any patch haven’t been successful, but I’ve found an discussion thread, where the problem was solved. Unfortunately it sucks a bit going through the links and threads. That’s why here is a short and clear HOWTO with an already fixed patch:

First time installation

* Download or get VMware-server-2.0.1-156745.x86_64.tar.gz and unpack it.
* go into vmware-server-distrib and run vmware-install.pl.
* the process stops with an error. (... wait.h:78: error: conflicting types ... ).
Download and unpack this vmware-server.2.0.1_x64-modules-2.6.30.4-fix.tgz into the vmware-server-distrib directory.
Invoke vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh
* remove this directory: /usr/lib/vmware/modules/binary
* start vmware-config.pl
* This should leave you with a working VMware installation. Go now with your browser to https://localhost:8333 and enter your Serial Number under “Applications->Enter Serial Number“.

Reinstallation
If anything goes wrong, you can do the installation again. In order to do so, you need to do some steps manually on your console.

* first, delete the vmware modules

rm -rf /usr/lib/vmware/modules/

and if necessary (you’ll be told, if so):

rm -rf /lib/modules/2.6.31-13-server/misc/vm*

* If the vmware-config.pl aborts, because it can’t accomplish to shut down all vmware processes, kill all vmware processes manually.

kill -9 $( grep -i vm | awk '{ print $2 }' )

* rerun vmware-config.pl
* if somewhere in the installation process you should be asked:

“/usr/bin/vmware-config.pl“. Do you want this
program to invoke the command for you now? [yes]

you should answer: no
then run the patch vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh.
After this you run /usr/bin/vmware-config.pl

Empty Browser Remote Console Problem

Sometime it happens, my Firefox 3.5.3 doesn’t show anything, if I try to start https://localhost:8333. If I should take a wild *** guess, this is all due to my multiple installation attempts of the VMware server itself. Or is it just buggy?
I noticed, that actually three different approaches (sometimes in combination) lead to a relief.

* Don’t use hostnames, but IPs only in your browser. E.g: https://127.0.0.1:8333/ui instead of https://localhost:8333/ui
* Restart the vmware-hostd (your running VM’s won’t be affected <- bold statement, don’t you think?).

/etc/initd.d/vmware-mgmt restart

If the process number stays unchanged, and a log entry in /var/log/vmware/hostd-x.log indicates an already running vmware-hostd, kill the process manually, because it seams to hang:

killall -9 vmware-hostd

* Uninstall the VMware remote console Plug-in:

Menu: Tools -> Add-ons -> Tag:Extentions -> “VMware remote console Plug-in” -> Button:Uninstall

and reinstall it again. Perform the first step.

* Remove the VMware’s SSL-Certificate:

Menu: Edit -> Preferences -> Section:Advanced -> Tab:Security ->Tab:Encryption -> Button:View Cerfiticates -> Authorities.

Scroll down, until VMware shows up. Select and delete all entries. Perform the first step
* Or follow a completely different approach described here

You can read a more complete error log of the failed VMWare server installation here.

make[1]: Entering directory `/usr/src/linux-headers-2.6.31-13-server'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:31:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:78: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:70: note: previous declaration of ‘poll_initwait’ was here
In file included from /tmp/vmware-config1/vmmon-only/./include/vmware.h:38,

use a social bookmark, e-mail or print this story

* Digg
* del.icio.us
* MisterWong
* StumbleUpon
* Google Bookmarks
* Technorati
* Facebook
* MySpace
* Live
* email
* Print

Tags: 9.10, error, HOWTO, istallation, karmic, koala, problem, server, ubuntu, vmware, x86_64.
1 Response to “VMware-server 2.0.1 Installation HOWTO for Karmic Koala (x86_64)”

1. Daniele

Works perfectly, thanks a ton!!

[LittleLebowski]

Followed the instructions exactly on a new install of 2.0.2 on a fresh install of Koala 64b and it still fails.

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmmon-only'
make -C /lib/modules/2.6.31-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic'
  CC [M]  /tmp/vmware-config4/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config4/vmmon-only/linux/driver.c:31:
/tmp/vmware-config4/vmmon-only/./include/compat_wait.h:78: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:70: note: previous declaration of ‘poll_initwait’ was here
In file included from /tmp/vmware-config4/vmmon-only/./include/vmware.h:38,
                 from /tmp/vmware-config4/vmmon-only/linux/driver.c:99:
/tmp/vmware-config4/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
In file included from /tmp/vmware-config4/vmmon-only/./include/vcpuset.h:103,
                 from /tmp/vmware-config4/vmmon-only/./include/modulecall.h:37,
                 from /tmp/vmware-config4/vmmon-only/./common/vmx86.h:33,
                 from /tmp/vmware-config4/vmmon-only/linux/driver.h:29,
                 from /tmp/vmware-config4/vmmon-only/linux/driver.c:101:
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:460:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:551:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:640:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:729:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:816:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:903:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:986:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1069:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1313:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_atomic.h:1796:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config4/vmmon-only/./include/vm_asm_x86_64.h:39,
                 from /tmp/vmware-config4/vmmon-only/./include/vm_asm.h:41,
                 from /tmp/vmware-config4/vmmon-only/linux/driver.c:103:
/tmp/vmware-config4/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config4/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config4/vmmon-only/./include/vm_asm.h:41,
                 from /tmp/vmware-config4/vmmon-only/linux/driver.c:103:
/tmp/vmware-config4/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config4/vmmon-only/linux/driver.c:119:
/tmp/vmware-config4/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined
/tmp/vmware-config4/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/tmp/vmware-config4/vmmon-only/linux/driver.c:1423: error: too many arguments to function ‘smp_call_function’
/tmp/vmware-config4/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/vmware-config4/vmmon-only/linux/driver.c:1987: error: ‘struct task_struct’ has no member named ‘euid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:1987: error: ‘struct task_struct’ has no member named ‘uid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:1988: error: ‘struct task_struct’ has no member named ‘fsuid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:1988: error: ‘struct task_struct’ has no member named ‘uid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:1989: error: ‘struct task_struct’ has no member named ‘egid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:1989: error: ‘struct task_struct’ has no member named ‘gid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:1990: error: ‘struct task_struct’ has no member named ‘fsgid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:1990: error: ‘struct task_struct’ has no member named ‘gid’
/tmp/vmware-config4/vmmon-only/linux/driver.c:2007: error: too many arguments to function ‘smp_call_function’
make[2]: *** [/tmp/vmware-config4/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config4/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config4/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please 
visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and 
"http://www.vmware.com/go/unsup-linux-tools".

Execution aborted.

[sdowney717]

did you do 3, 4, 5, 6?
looks like you did 1 and 2

1 * Download or get VMware-server-2.0.1-156745.x86_64.tar.gz and unpack it.
2 * go into vmware-server-distrib and run vmware-install.pl.
* the process stops with an error. (... wait.h:78: error: conflicting types ... ).
3 Download and unpack this vmware-server.2.0.1_x64-modules-2.6.30.4-fix.tgz into the vmware-server-distrib directory.
4 Invoke vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh
5 * remove this directory: /usr/lib/vmware/modules/binary
6 * start vmware-config.pl
* This should leave you with a working VMware installation. Go now with your browser to https://localhost:8333 and enter your Serial Number under “Applications->Enter Serial Number“.

[doug-M]

for the mouse and kvm module issue, simply make a text file named launchVM.sh and make it executable with this inside.
After you get your VM working in the wmware server from the browser, you can launch it at any time by running launchVM.sh and it will present a list of machines to start. The web browser does not have to be even running.

I tried this but I get:
extensions/VMwareVMRC@vmware.com/plugins/bin/vmware-vmrc: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory

libexpat.so.0 is in /usr/lib/vmware/lib/ so I added:
export LD_LIBRARY_PATH=/usr/lib:/usr/lib/vmware/lib/

Now I get:
extensions/VMwareVMRC@vmware.com/plugins/bin/vmware-vmrc: error while loading shared libraries: /usr/lib/vmware/lib/libexpat.so.0: cannot read file data: Error 21

The file wrapper-gtk24.sh in /usr/lib/vmware/lib jumps through lots of hoops to get an LD_LIBRARY_PATH.

Any ideas? All help appreciated.

My windows XP guest won't notice a ctrl-alt-ins to let me login as it is right now.

[sdowney717]

not sure why it does not work

i put a couple screen shots in showing how it brings up a server window for the vm's.

running the shell script in a terminal window for me shows this

scott@scott-desktop:~$ export VMWARE_USE_SHIPPED_GTK=yes
scott@scott-desktop:~$ vmrc="$(find "$HOME/.mozilla/firefox" -name vmware-vmrc -type f -perm -111 | tail -1)"
scott@scott-desktop:~$ [ -x "$vmrc" ] || exit 1
scott@scott-desktop:~$
scott@scott-desktop:~$ set -x
scott@scott-desktop:~$ cd "$(dirname "$vmrc")" && "$vmrc" -h 127.0.0.1:8333
++ dirname /home/scott/.mozilla/firefox/37a1mahz.default/extensions/VMwareVMRC@vmware.com/plugins/vmware-vmrc
+ cd /home/scott/.mozilla/firefox/37a1mahz.default/extensions/VMwareVMRC@vmware.com/plugins
+ /home/scott/.mozilla/firefox/37a1mahz.default/extensions/VMwareVMRC@vmware.com/plugins/vmware-vmrc -h 127.0.0.1:8333
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

[sdowney717]

that libpat file is in vmware only
perhaps vmware is still not installed properly for you?

"My windows XP guest won't notice a ctrl-alt-ins to let me login as it is right now."
i think any ctrl-alt key combination will not work since that takes away the mouse focus out of the vm.

[doug-M]

Maybe yours has an LD_LIBRARY_PATH set in your shell.
If you type env what does it show for LD_LIBRARY_PATH?

[sdowney717]

here is entire env

scott@scott-desktop:~$ env
ORBIT_SOCKETDIR=/tmp/orbit-scott
SSH_AGENT_PID=3195
TERM=xterm
SHELL=/bin/bash
XDG_SESSION_COOKIE=c5cf650c106dab20f6fd38f74ab4790 5-1257005239.566305-1827298449
GTK_RC_FILES=/etc/gtk/gtkrc:/home/scott/.gtkrc-1.2-gnome2
WINDOWID=73400324
GTK_MODULES=canberra-gtk-module
USER=scott
LS_COLORS=rs=0:di=01;34:ln=01;36:hl=44;37i=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01r=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42w=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31: *.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:* .zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01; 31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31: *.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*. ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz =01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp= 01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01 ;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01; 35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;3 5:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35 :*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:* .m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.n uv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb =01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=0 1;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35 :*.yuv=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:* .ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m id=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mp c=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=0 0;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
SSH_AUTH_SOCK=/tmp/keyring-o3zGLP/socket.ssh
GNOME_KEYRING_SOCKET=/tmp/keyring-o3zGLP/socket
SESSION_MANAGER=local/scott-desktop:@/tmp/.ICE-unix/3156,unix/scott-desktop:/tmp/.ICE-unix/3156
USERNAME=scott
DESKTOP_SESSION=gnome
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
PWD=/home/scott
GDM_KEYBOARD_LAYOUT=us
LANG=en_US.UTF-8
GNOME_KEYRING_PID=3141
GDM_LANG=en_US.UTF-8
GDMSESSION=gnome
SPEECHD_PORT=7560
SHLVL=1
HOME=/home/scott
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
LOGNAME=scott
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-X76veIgudd,guid=f1e6425071884500bda49e964aec60b8
XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/
LESSOPEN=| /usr/bin/lesspipe %s
DISPLAY=:0.0
LESSCLOSE=/usr/bin/lesspipe %s %s
COLORTERM=gnome-terminal
XAUTHORITY=/var/run/gdm/auth-for-scott-vI6xPO/database
_=/usr/bin/env
scott@scott-desktop:~$

[doug-M]

hmm so you have no ld-library-path
sry messing with vmware breaks my shift alt and ctrl keys right now so no caps.

so i found that /usr/lib/vmware/lib/libexpat.so.0 is actually a directory not a file, so adding /usr/lib/vmware/lib/libexpat.so.0 to the ld-library-path got it farther, after adding about 6 more paths to it, some in the firefox extensions directory, allowed it to start.

unfortunately no success.

i did notice one thing, it appears to be happier in the upper left corner of the console, i saw other people mentioning they have a 640x480 window where the mouse works. that might be what is happening to me.

also my firefox profile just got moved from 32bit to 64 bit, perhaps some old 32 bit stuff got left in there and not cleaned up.

any idea how to reinstall the 64bit plugin, i could try blowing away all the vmware stuff in my profile and re-installing.

[sdowney717]

the mouse issue is because our new linux gtk does not play right with vmware.
SO, vmware ships gtk's that do work. but you have to tell your application to use the vmware versions of gtk and not our standard 2.18 version of gtk.

the little script does that with vmware servers console.
there might be other ways to do thi and then you mouse will work properly.


follow the links in this thread to read up on it
http://ubuntuforums.org/showthread.php?t=1298781

http://communities.vmware.com/thread/235572?tstart=0

rustynail 7 posts since
Jun 25, 2008
7. Re: Serious Problem with KDE4 and Vmware Server (plugin) Oct 20, 2009 2:27 AM
in response to: F4bi1

http://www.pclinuxos.com/index.php?o...&topic=63219.0

Apparently there is some sort of change in these packages that cause problems with the plugin. This problem is effected by Kubuntu 9.10 as well (after all updates).

Apparently rolling back fixes the mouse focus problem.

gtk+2.0 (version 2.18.1-1pclos2009) downgraded to version 2.16.6-3pclos2009
libgdk_pixbuf2.0_0 (version 2.18.1-1pclos2009) downgraded to version 2.16.6-3pclos2009
libgtk+-x11-2.0_0 (version 2.18.1-1pclos2009) downgraded to version 2.16.6-3pclos2009
libgtk+2.0_0 (version 2.18.1-1pclos20092.16.6-3pclos2009) downgraded to version 2.16.6-3pclos2009

However I think your problem is something else. In Ubuntu -> Ubuntu a down arrow activates the "print screen" or whatever activate the screen capture tool. There is a quick fix floating around the net for the remote Ubuntu client (probably all Debian).


Re: Serious Problem with KDE4 and Vmware Server (plugin) Oct 20, 2009 3:25 AM
in response to: rustynail
Click to view rustynail's profile Novice rustynail 7 posts since
Jun 25, 2008
8. Re: Serious Problem with KDE4 and Vmware Server (plugin) Oct 20, 2009 3:25 AM
in response to: rustynail

Here is a temporary solution:

+#!/bin/bash ################################################## ############################## # Call VMWare Server's Remote Console in a clean GTK setup. ################################################## ############################## # Clean GTK setup for VMWare export VMWARE_USE_SHIPPED_GTK=yes # Find console executable in Firefox plugins. vmrc="$(find "$HOME/.mozilla/firefox" -name vmware-vmrc -type f -perm -111 | tail -1)" || exit 1 set -x cd "$(dirname "$vmrc")" && "$vmrc" -h 127.0.0.1:8333+