How to install VMWare Player's i386.bundle for 32-bit Linux Host
'I've doewnloaded the VMWare Player i386.bundle to my 32-bit Ubuntu 12.04 system but don't know how to install it.
Please help. Thanks very much.
Julianloui
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
1. Run a terminal
2. Make the file exectutable:
chmod +x VMware-
3. Begin installation process
sudo sh VMWare-
Revision history for this message
|
#2 |
Hi, Lars H,
Thank you very much for your help. When I try to install VMW by following your instructions from the Downloads directory, I get the following erros after I enter the second command:
sudo sh VMware-
E: Unable to locate package VMware-
E: Couldn't find any package by regex 'VMware-
Julianloui
Revision history for this message
|
#3 |
Hi, Lar H,
I tried VMplayer on a Ubuntu 12.04 machine tonight and came across the same problem repeatedly. I first downloaded VMware-
chmod +x VMware-
sudo sh VMware-
VM-data outputs:
Extracting VMware Installer...done.
VM-errs outputs:
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
Gtk-Message: Failed to load module "canberra-
VMware Installer outputs:
One of your processors does not have the necessary 64-bit extensions to run VMware virtual machines.
I thought I picked 'VMware Player and VMware Player for 32-bit Linux' from the VMWare website.
Your help will be greatly appreciated as always.
Julianloui
Revision history for this message
|
#4 |
You should check in in your BIOS setup, there might be a setting to enable/disable virtual extensions.
Make sure it is enabled.
Revision history for this message
|
#5 |
Try to install build-essential from the package sources (apt-get install build-essential). Maybe there is a build tool missing.
Revision history for this message
|
#6 |
Hi, Manfred aand Lars,
My machine's BIOS does not show any feature related to virtual extensions. After I successfully ran your build-essential suggestion, Linux still output the same errors as I reported last time. Many thanks to your kind help.
Julianloui
Revision history for this message
|
#7 |
What make and model is your system, what CPU, what BIOS manufacturer and version?
Revision history for this message
|
#8 |
Hi, Manfred,
Here's the information on my system:
Product: HP d530 SFF
Processor: Intel Pentium 4, 2.666GHz/533 MHz
Memory: 1.024 GB
Hard drive: Seagate 40 GB
System BIOS: HP 786B2 v.1.11
I hope it helps. Thanks again.
Julianloui
Revision history for this message
|
#9 |
It seems that Intel Pentium 4 is not meeting the minimum requirements for running VMware Player 6.
see also
http://
Please cross check with the VMware internet pages.
Revision history for this message
|
#10 |
Manfred,
Thanks for giving me an excellent pointer. I've just downloaded VMware Player v3.1.6-744570 from http://
sudo apt-get install VMware-Player*
Julianloui
Revision history for this message
|
#11 |
Do not confuse the commands for the debian package management system (dpkg, apt..., synaptic, software-center) with the commands for manual installation of programs that you have downloaded in source form, or that are delivered in other format.
The command "sudo apt-get install packagename" tries to find a package with the given name in the standard Ubuntu repositories, or a PPA that you have enabled. In your case this is not applicable, as you have downloaded the VMware Player from another source.
I assume doing the "chmod ..." and "sudo sh ..." should already be enough for installing the VMware player executables in your system.
You should now be able to start the VMware with the command vmware or by locating this command in your dash or main applications menu (depending on what Ubuntu desktop version you are using).
Revision history for this message
|
#12 |
Manfred,
Even though I seemed to have successfully installed VMware Player from its source, I can't find or execute vmware from the command line. Nor can I find it in the entire Ubuntu system. Can you tell me where to look for it?
Thanks very much for distinguishing between installing resident Ubuntu packages and installing external source packages.
Julianloui
Revision history for this message
|
#13 |
The following commands should indicate where the VMware executables are located (if the name of the program to execute is VMware)
1. open a terminal and enter the letters vm and then hit the Tab key twice. This should list all commands that are available on your system and that start with vm
2. in a terminal enter issue the command
which vmware
This either will not produce any output at all, or will list the location of the vmware executable (probably /usr/bin/vmware)
3. issue the terminal commands
sudo updated
locate /vmw
locate /VMw
This should search your system for all files and directories that contain "/vmw" or "/VMw" in their fill name.
Did the "sudo sh VMw..." command give any warnings or error messages?
Revision history for this message
|
#14 |
HI, Manfred,
Thank you very much for your patient help.
I carried out all your instructions and still found no vmware player executable files. So I decided to re-install
VMware Player 3.1.6 as follows.
chmod +x VMware-
sudo sh VMware-
Lo and behold. LInux behaved differently this time and I was able to see
"Installing VMware 3.1.6
Installation was successful"
After I entered
vmplayer 1>vmplayer-data 2>vmplayer-errs
Linux output the following error message:
"Unable to build kernel module.
See log file /tmp/vmware-
<> <> <> Contents of vmplayer-data file:
topping VMware services:
VMware USB Arbitrator[71G done
VM communication interface socket family[71G done
Virtual machine communication interface[71G done
Virtual machine monitor[71G done
Blocking file system[71G done
make: Entering directory `/tmp/vmware-
make -C /lib/modules/
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/
CC [M] /tmp/vmware-
make[1]: Leaving directory `/usr/src/
make: Leaving directory `/tmp/vmware-
<> <> <> <> Contents of vmplayer-errs:
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Using 2.6.x kernel build system.
/tmp/vmware-
make[2]: *** [/tmp/vmware-
make[1]: *** [_module_
make: *** [vmmon.ko] Error 2
-------
* * * * By the way, I did ran VMware Kernel Module Update as suggested by vmplayer, but ot no avail and still got the above errors.
-------
Julianloui
Revision history for this message
|
#15 |
Manfred,
I forgot to mention that whenever I tried to install VMPlayer 3.1 using 'sudo sh ....', I never saw any system errors on the screen but then system silence can also signify zilch. That's why I was overjoyed this last time when I saw a positive system response
"Installing VMware 3.1.6
...
Installation was successful"
Julianloui
Revision history for this message
|
#16 |
1. To get rid of the 'Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine"' annoyances you could try
sudo apt-get install gtk2-engines-
2. You should not be astonished that you do not see any output when you redirect all syout and syserr to files.
3. Do you have the kernel source installed for the kernel that you are running?
what is the output of
uname -a
lsb_release -a
dpkg -l | grep headers
dpkg -l | grep essential
4. What is the contats of /tmp/vmware-
If that file is too large, please upload it to pastebin.ubuntu.com and provide the link that you get in this file.
5. Have you checked https:/
General remark: Your problem is more related to a specific third-party-
Revision history for this message
|
#17 |
Maybe I finally found a link with a proposed solution http://
Revision history for this message
|
#18 |
Manfred,
I was able to download the patch. But sudo ./patch-
"Sorry, this script is only for VMWare WorkStation 7.1.5 or VMWare Player 3.1.5. Exiting"
My previous 'zilch' comment was intended only for commands without output redirections, namely
commands not using '>filename' or '1>file-data' or '2>file-errs' as example. I use output redirections only to
capture the screen displays for later use, such as reporting findings to this forum.
Many thanks again.
Julianloui
Revision history for this message
|
#19 |
see http://
Revision history for this message
|
#20 |
Note, i guess there is a tyo error on the jainkkapil page, the command to find out the vm version should most probably be "vmware --version" instead of "vmwaree --version".
Revision history for this message
|
#21 |
Manfred,
# vmplayer --version
outputs
-------
"VMPlayer 3.1.6 build 744570".
-------
# gedit *.sh
outputs the following at the beginning of the .sh file:
-------
#! /bin/bash
# VMWare Workstation/Player _host kernel modules_ patcher v0.6.2 by ©2010 Artem S. Tashkinov
# Tailored and fixed vmblock patching for the 2.6.39 patch by Stefano Angeleri (weltall)
# Use at your own risk.
fpatch=
vmreqver=7.1.4
plreqver=3.1.4
vmreqver=7.1.5
plreqver=3.1.5
:
:
-------
QUESTIONS :
Message #19 tells me to update the values of vmreqver and pireqver in the .sh file before running
./patch-
1. Should I change only 3.1.5 to 3.1.6?
2. What value should I use with vmreqver?
Many thnaks again.
Julianloui
-------
Revision history for this message
|
#22 |
Yes, try putting "plreqver=3.1.6" into the file.
The value for vmreqver most probably is the value you get for "vmware --version"
Revision history for this message
|
#23 |
Manfred,
Even the web article's instructions are confusing, I did change pireeqver to 3.1.6 and then ran
vmplayer. I giot the same on-screen Gtk Warning in addition to the following familiar error message:
"Before you can run VMware, several modules must be compiled and loaded into the running kernel"
I never had any trouble downloading and running vmplayer on my WIndows XP MacBook laptop. However, vmware's performance has been very disappoinitng on that machine. I guess a better approach would be to buy a copy of VMware Player. But, as a beginner and retiree, I am not sure that I'm that interested in virtualization , or have an urgent need for it. In short, I am only trying to acquire a nodding acquaintance of the subject.
Many thanks for your generous help.
Julianloui
Revision history for this message
|
#24 |
Please provide the full error messages not just a summary!
1. What is the exact text og the GTK Warning? Is it still about murrine? have you tried "sudo apt-get install gtk2-engines-
2. Have you successfully applied the patch?
3. Have you installed the kernel headers and the build-essential packages? Please provide the output requested in comment #16
4. Have you tried recompiling the modules after applying the patch "sudo vmware-modconfig --console --install-all"
Revision history for this message
|
#25 |
Manfred,
Here's my response to your latest requests.
1. "sudo apt-get install gtk2-engines-
gtk2-engines-
2. I have not succeeded in applying the patch.
3. I havenot insyalle dthe kernel headers nor do I know how to. I've installed the build-essential package.
-------
"uname -a "
Linux qq 3.2.0-58-
-------
"lsb_release -a"
No LSB modules are available
-------
"dpkg -l | grep headers"
ii libdbus-1-dev 1.4.18-1ubuntu1.4 simple interprocess messaging system (development headers)
ii libpulse-dev 1:1.1-0ubuntu15.4 PulseAudio client development headers and libraries
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
-------
"dpkg -l | grep essential"
ii build-essential 11.5ubuntu2.1 Informational list of build-essential packages
-------
"ls /tmp/vmware-
No such file or directory. I can see subdirectory vmware-root directiry in /tmp but can't access it even with
sudo.
-------
4. sudo vmware-
Using 2.6.x kernel build system.
/tmp/vmware-
make[2]: *** [/tmp/vmware-
make[1]: *** [_module_
make: *** [vmmon.ko] Error 2
Unable to install vmmon
Manfred, that's about all I can do now. MAny thanks again.
Julian
Revision history for this message
|
#26 |
Ok, the required kernel header package and build-essential are installed.
Now the next step must be to apply the patch.
What is the output of
sudo ./patch-
(of course you have to cd to the right directory before)
Revision history for this message
|
#27 |
Manfred,
After I copied VMware3.1.0.patch as VMware3.1.6.patch into my home directory,
"sudo ./patch-
/usr/lib/
But "vmplayer" produced the same old VMware Kernel Module Updater message:
"Before you can run VMware, sveral modules must be compiled and loaded into th erunning kernel"
> > > > > Please see the following long murrine error output also:
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): Pango-WARNING **: Failed to load Pango module '/usr/lib/
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
That's all i can report at te moment. Thanks very much again.
Julianloui
Revision history for this message
|
#28 |
Manfred,
After I copied VMware3.1.0.patch as VMware3.1.6.patch into my home directory,
"sudo ./patch-
/usr/lib/
But "vmplayer" produced the same old VMware Kernel Module Updater message:
"Before you can run VMware, sveral modules must be compiled and loaded into th erunning kernel"
> > > > > Please see the following long murrine error output also:
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): Pango-WARNING **: Failed to load Pango module '/usr/lib/
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
That's all i can report at te moment. Thanks very much again.
Julianloui
Revision history for this message
|
#29 |
Manfred,
After I copied VMware3.1.0.patch as VMware3.1.6.patch into my home directory,
"sudo ./patch-
/usr/lib/
But "vmplayer" produced the same old VMware Kernel Module Updater message:
"Before you can run VMware, sveral modules must be compiled and loaded into th erunning kernel"
> > > > > Please see the following long murrine error output also:
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): Pango-WARNING **: Failed to load Pango module '/usr/lib/
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
That's all i can report at te moment. Thanks very much again.
Julianloui
Revision history for this message
|
#30 |
Manfred,
After I copied VMware3.1.0.patch as VMware3.1.6.patch into my home directory,
"sudo ./patch-
/usr/lib/
But "vmplayer" produced the same old VMware Kernel Module Updater message:
"Before you can run VMware, sveral modules must be compiled and loaded into th erunning kernel"
> > > > > Please see the following long murrine error output also:
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): Pango-WARNING **: Failed to load Pango module '/usr/lib/
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
That's all i can report at te moment. Thanks very much again.
Julianloui
Revision history for this message
|
#31 |
Manfred,
After I copied VMware3.1.0.patch as VMware3.1.6.patch into my home directory,
"sudo ./patch-
/usr/lib/
But "vmplayer" produced the same old VMware Kernel Module Updater message:
"Before you can run VMware, sveral modules must be compiled and loaded into th erunning kernel"
> > > > > Please see the following long murrine error output also:
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): Pango-WARNING **: Failed to load Pango module '/usr/lib/
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
That's all i can report at te moment. Thanks very much again.
Julianloui
Revision history for this message
|
#32 |
Manfred,
After I copied VMware3.1.0.patch as VMware3.1.6.patch into my home directory,
"sudo ./patch-
/usr/lib/
But "vmplayer" produced the same old VMware Kernel Module Updater message:
"Before you can run VMware, sveral modules must be compiled and loaded into th erunning kernel"
> > > > > Please see the following long murrine error output also:
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-gksu:3597): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): Pango-WARNING **: Failed to load Pango module '/usr/lib/
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
(vmware-gksu:3597): GLib-GObject-
That's all i can report at te moment. Thanks very much again.
Julianloui
Revision history for this message
|
#33 |
Ok.
1. Another attempt to cure the GTK-Warning and GLib-GObject annoyances:
sudo apt-get install --reinstall gtk2-engines gtk2-engines-oxygen libpango1.0-0
2. Back to your VMware Player:
It seems that the patch was not applied correctly, but the script prevents re-applying the patch if it has been done already once.
Meanwhile I found another version of the patch that should better fit to your version:
http://
http://
http://
What I recommend:
1. completely deinstall the vmware player software (with sudo vmware-uninstall)
2. check whether the vmware directories have been completele emptied/deleted
3. re-start the installation
4. apply the patch
Please provide the full output of steps 3 and 4.
Revision history for this message
|
#34 |
Manfred,
Thanks for getting to the bottom fo the matter.
Step 3: I installed VMWare Player 3.1 successfully per VMware Installer 1.1.
Step 4: 'sudo sh patch-modules_
"
patch-module_
patch-module_
patch-module_
patch-module_
Sorry, this script is only for VMWare Workstation 7.1.5 or VMWare Player 3.1.6 "
-------
But file patch_modules_
fpatch=
vmreqver=7.1.6
plreqver=3.1.6
Julianloui
Revision history for this message
|
#35 |
Manfred,
I'm reproducing lines 24 to 33 from the patch+modules_
24 unset product
25 -z "$vmver" ] && error "VMWare is not installed (properly) on this PC"
26 "$vmver" == "workstation$
27 "$vmver" == "player$plreqver" ] && product="VMWare Player"
28 "$vmver" == "workstation$
29 "$vmver" == "player$plreqver2" ] && product="VMWare Player"
30 -z "$product" ] && error "Sorry, this script is only for VMWare WorkStation $vmreqver or VMWare Player 31 $plreqver"
32
33 "`id -u`" != "0" ] && error "You must be root to run this script"
Julianloui
Revision history for this message
|
#38 |
Why do you post each message three times?
Seems a trivial error, try
sudo bash patch-modules_
Revision history for this message
|
#39 |
Manfred,
I am sorry that I failed to notice this redundancy when I finished my last response at the website.
-------
sudo bash patch-modules_
/usr/lib/
-------
sudo sh patch-module_
patch-modules_
patch-modules_
patch-modules_
patch-modules_
Sorry, this script is only for VMWare WorkStation 7.1.5 or VMWare Player 3.1.6. Exiting
-------
patch_modules_
1 #! /bin/bash
2. # VMWare Workstation/Player _host kernel modules_ patcher v0.6.2 by ©2010 Artem S. Tashkinov
3 # Tailored and fixed vmblock patching for the 2.6.39 patch by Stefano Angeleri (weltall)
4 # Use at your own risk.
5
6 fpatch=
7 vmreqver=7.1.5
8 plreqver=3.1.6
9
10 error()
11 {
12 echo "$*. Exiting"
13 exit
14 }
15
16 curdir=`pwd`
17 bdate=`date "+%F-%H:%M:%S"` || error "date utility didn't quite work. Hm"
18 vmver=`
19 vmver="
20 basedir=
21 ptoken=
22 bkupdir=
23
24 unset product
25 [ -z "$vmver" ] && error "VMWare is not installed (properly) on this PC"
26 [ "$vmver" == "workstation$
27 [ "$vmver" == "player$plreqver" ] && product="VMWare Player"
28 [ "$vmver" == "workstation$
29 [ "$vmver" == "player$plreqver2" ] && product="VMWare Player"
30 [ -z "$product" ] && error "Sorry, this script is only for VMWare WorkStation $vmreqver or VMWare
. Player $plreqver"
::
Julianloui
Revision history for this message
|
#40 |
I think there is progress.
I recommend to restart from the beginning:
What I recommend:
1. completely deinstall the vmware player software (with sudo vmware-uninstall)
2. check whether the vmware directories have been completely emptied/deleted, especially /usr/lib/
3. re-start the installation
4. apply the patch (with sudo bash...)
Please provide the full output of steps 3 and 4.
Revision history for this message
|
#41 |
Manfred,
I've just re-done your suggested steps and obtained the same errorr in lines 26-29 in Step 4. Steps 1 through 3 went OK. Thanks again.
Julianloui
Revision history for this message
|
#42 |
Please copy/paste the command that you give and the full output of the sudo bash ... command
Revision history for this message
|
#43 |
Manfred,
(1) Reproduced below are the bash command and its entire output:
sudo bash patch-modules_
/usr/lib/
(2) Linux keeps pointing out lines 26 through 29 as containing an 'unexpected operator' consistently. Do they provide any meaningful clues to my problem. Please see post #39 for details.
Many thanks again.
Julianloui
Revision history for this message
|
#44 |
What you are writing is contradictory.
The only output I see in item (1) in post #43 is '...already patched...', but you write in (2) about 'unexpected operator' messages.
When and where do you get that 'unexpected operator' message?
Revision history for this message
|
#45 |
2014-02-17:
Manfred,
I am copying #34 here in order to improve our communication. My latest post's second paragraph, namely Item (2) refers the "unexpected operator" error message resulting from running 'sudo sh patch-modules_
The 'unexpected operator' report has NOTHING to do with the 'sudo bash patch-modules_
Julianloui
=======
D U P L I C A T I O N o f P O S T # 3 4
Manfred,
Thanks for getting to the bottom fo the matter.
Step 3: I installed VMWare Player 3.1 successfully per VMware Installer 1.1.
Step 4: 'sudo sh patch-modules_
"
patch-module_
patch-module_
patch-module_
patch-module_
Sorry, this script is only for VMWare Workstation 7.1.5 or VMWare Player 3.1.6 "
-------
But file patch_modules_
fpatch=
vmreqver=7.1.6
plreqver=3.1.6
Julianloui
Revision history for this message
|
#46 |
I guess I was not clear enough. You should no more use "sudo sh patch...", because that gives the 'unexpected operator' error. You have to use "sudo bash patch..." instead as a full replacement for that.
"sudo bash patch..." now apparently gives 'patch already applied'. So it seems that the patch process is already completed.
What is now the output of
sudo vmware-modconfig --console --install-all
vmplayer
Revision history for this message
|
#47 |
Manfred,
I really hope that Launchpad.net will soon enable its users to edit their posts in order to improve communications. Not everyone is a top-notch speller or instant writer. What a shame that it has been dragging its feet for decades!
Look at all the Linux or Unix websites and see this one glaring difference. I wish I could go back to simplify some of my posts.
When one writes in the wee hours in the morning, errros are bound to creep up, especially when you reach my age. I've been retired from engineering for almost 20 years.
Julianloui
Revision history for this message
|
#48 |
=======
<> > OUTPUT and ERRORS: from 'sudo vmware-moduconfig --console --install-all '
=======
-------
<>----<> SCREEN OUTPUT :
-------
Stopping VMware services:
VMware USB Arbitrator[71G done
VM communication interface socket family[71G done
Virtual machine communication interface[71G done
Virtual machine monitor[71G done
Blocking file system[71G done
make: Entering directory `/tmp/vmware-
make -C /lib/modules/
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/
CC [M] /tmp/vmware-
make[1]: Leaving directory `/usr/src/
make: Leaving directory `/tmp/vmware-
-------
<>----<> SCREEN ERRORS :
-------
Using 2.6.x kernel build system.
/tmp/vmware-
make[2]: *** [/tmp/vmware-
make[1]: *** [_module_
make: *** [vmmon.ko] Error 2
Unable to install vmmon
<======
<>--<> 'vmplayer' produced following SCREEN ERRORS :
<======
Logging to /tmp/vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
(vmware-
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
ERROR: modinfo: could not find module vmmon
ERROR: modinfo: could not find module vmnet
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
Fontconfig error: "conf.d", line 1: no element found
Fontconfig warning: line 73: unknown element "cachedir"
Fontconfig warning: line 74: unknown element "cachedir"
Julianloui
Revision history for this message
|
#49 |
If you want my help you have to cooperate and provide the output that I ask for.
Please repeat all steps from comment #40
Revision history for this message
|
#50 |
Manfred,
Thank you very much for being so patient. I humbly and sincerely believe that I have done my very best to cooperate by giving you the data you asked for each time. Unfortunately, we've obviously failed to understand each other, probably due to our different backgrounds or the existence of a generation gap.
By the way, today I succeeded in a one day tearing down a Lunux computer totally until it was almost bare and rebuilt it from the bottom up. I diagnozed a marginal hard drive and a questionable CD-RW drive, erased a spare old hard drive before I used it to install Windows XP and Ubuntu 12.04 on the same machine. I also re-installed most major Linux packages that are essential to my daily needs.
Getting back to VMware Player3.1.6, I think it's best for me to cool it and re-assess the situation instead of
immersing myself in it day in and day out. This way I'll be able to see things more clearly and determine whether it'll still be worth my time to pursue it further.
Once again, I sincerely thank you for your generosity and infinite patience. I honestly believe that one day I'll be able to report back whether 3.1.6 is any good or how I've finally resolved this matter.
Julianloui
Revision history for this message
|
#51 |
Manfred,
Thank you very much for being so patient. I humbly and sincerely believe that I have done my very best to cooperate by giving you the data you asked for each time. Unfortunately, we've obviously failed to understand each other, probably due to our different backgrounds or the existence of a generation gap.
By the way, today I succeeded in a one day tearing down a Lunux computer totally until it was almost bare and rebuilt it from the bottom up. I diagnozed a marginal hard drive and a questionable CD-RW drive, erased a spare old hard drive before I used it to install Windows XP and Ubuntu 12.04 on the same machine. I also re-installed most major Linux packages that are essential to my daily needs.
Getting back to VMware Player3.1.6, I think it's best for me to cool it and re-assess the situation instead of
immersing myself in it day in and day out. This way I'll be able to see things more clearly and determine whether it'll still be worth my time to pursue it further.
Once again, I sincerely thank you for your generosity and infinite patience. I honestly believe that one day I'll be able to report back whether 3.1.6 is any good or how I've finally resolved this matter.
Julianloui
Revision history for this message
|
#52 |
This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.