27 Dec
2006
27 Dec
'06
7:28 p.m.
Eric Dondelinger wrote:
In the end, the issue is rather trivial - the
installation
of the player leaves a file "/etc/vmware/not_configured"
even though everything is configured as it should be.
It is sufficient to rename or delete the file, and vmplayer
will run.
Yes, if you go through the startup script it's easy to find. My case was
a little bit more twisted: I had 2 startup scripts running one after the
other. The first started ok, the second did nothing but touch that file.
VMWare ran fine but on the next reboot, I ran into the same issues as
you did.
So maybe you double-clicked when your KDE was set to a simple click?
Stop using GNOME ;-)
-pu