[SOLVED] VMware player on 14.2 (xfce): Failed to execute command "@@BINARY@@ %u".

apmount · 06-01-2017, 03:11 PM

Hello, after installing vmware player on Slackware 14.2 (xfce) I get this message when I try to run it through the xfce panel (Applications > System > VMware player). There isn't also an icon in the panel for vmware player.

When I start it through terminal, I get the following errors:

Code:

bash-4.3$ vmplayer

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",

(vmware-modconfig:7661): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce",
I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml"

player starts successfully though. Any ideas what possibly went wrong in the installation?

Just to mention that the first attempt to install vmplayer was unsuccessful (an error about USB or something like that) so I installed it with --ignore-errors

UPDATE: OK, after a restart everything seems to work normal. Everything? Not quite true, since i have to run after the command vmware-modconfig --console --install-all after each restart...Not that it is too big of an issue. I am thinking of having a script run this command at each restart...

kjhambrick · 06-03-2017, 04:16 AM

apmount --

I don't run xfce.

I am running Slackware64 14.2 + MultiLib with KDE 4 + the Oxygen Theme.

No such errors on 64-bit VMWare Workstation 12.5 or 64-bit VMWare Player 12.1 ...

Are you running Slackware64 or 32-bit Slackware ?

If Slackware64, do you run MultiLib ?

And how did you install VMWare Player ( SlackBuild, etc ) ?

I see a lot of hits in the google-plex about 'Gtk-WARNING **: Unable to locate theme engine in module_path' but none specifically referencing xfce ...

And I've never seen the proxy.xml message either.

Does everything seem to work in VMWare Player ?

If so, ignore the SPAM ?

-- kjh

P.S. I missed your update from yesterday. Something does not sound quite right, does it ?

With VMWare WorkStation, when I update my 4.4.x Kernel (

about weekly these days

), VMWare rebuilds the Kernel Modules automatically on the first boot into the New Kernel and then it 'just works'.

Just a wild-A** Guess: Are you perhaps running VMWare Player as root ?

apmount · 06-05-2017, 03:10 PM

@kjhambrick
sorry for the long time to answer (we had a day off here this monday), i am not trying to run this as a root. I have the player not the workstation. It really isn't much of a problem since I only have to issue this command (vmware-modconfig --console --install-all as root) at the beginning and everything works OK. when I try from the console to run it as root i get:

Code:

root@slack:~# vmplayer
No protocol specified

(vmware-modconfig:5169): Gtk-WARNING **: cannot open display: :0.0
root@slack:~#

Anyway, the icon now appears on the menu, so i start it from there, not from console. I just have to issue every time the above mentioned command. Probably I could insert it somewhere in the start script of the vmplayer, I am just too lazy to purse this further. Just run the command as root and go on

apmount · 06-13-2017, 04:31 PM

another test showed that if I run (as root) the

Code:

/etc/rc.d/init.d/./vmware start

then I do not have to run vmware-modconfig --console --install-all. Basically it is a similar thing. So, if this script runs as the system starts then probably everything is OK.