Running Fedora 12, having issues running VMware Player
 

I just loaded Fedora 12 and am having issues running VMware Player. App installed, but upon launching it, the screen simply disappears and nothing happens. Anyone else seen this and know a fix? Thanks!

-T

Open a terminal window and type
vmplayer

and see what it says.
Copy the results here.

Here it is:
[root@tjlloyd-chiftss tjlloyd]# vmplayer
Failed to get value for `/desktop/gnome/interface/accessibility': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to get value for `/desktop/gnome/interface/accessibility': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Logging to /tmp/vmware-root/setup-18104.log
filename: /lib/modules/2.6.31.12-174.2.22.fc12.i686/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 1BBFFDFF731D21908BB9AF6
depends:
vermagic: 2.6.31.12-174.2.22.fc12.i686 SMP mod_unload 686
filename: /lib/modules/2.6.31.12-174.2.22.fc12.i686/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
srcversion: BFFA2F36690BB84A717DE24
depends:
vermagic: 2.6.31.12-174.2.22.fc12.i686 SMP mod_unload 686
filename: /lib/modules/2.6.31.12-174.2.22.fc12.i686/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 400149ED038D22A87322D56
depends:
vermagic: 2.6.31.12-174.2.22.fc12.i686 SMP mod_unload 686
parm: root:The directory the file system redirects to. (charp)
filename: /lib/modules/2.6.31.12-174.2.22.fc12.i686/misc/vmci.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: 10CF7904714E1EDA4361B9F
depends:
vermagic: 2.6.31.12-174.2.22.fc12.i686 SMP mod_unload 686
filename: /lib/modules/2.6.31.12-174.2.22.fc12.i686/misc/vsock.ko
supported: external
license: GPL v2
version: 1.0.0.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: BC1943DCE52AE461DCC2D43
depends: vmci
vermagic: 2.6.31.12-174.2.22.fc12.i686 SMP mod_unload 686
filename: /lib/modules/2.6.31.12-174.2.22.fc12.i686/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 1BBFFDFF731D21908BB9AF6
depends:
vermagic: 2.6.31.12-174.2.22.fc12.i686 SMP mod_unload 686
Failed to get value for `/desktop/gnome/interface/accessibility': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to get value for `/desktop/gnome/interface/accessibility': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to get value for `/desktop/gnome/interface/accessibility': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to get value for `/system/http_proxy/use_http_proxy': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to get value for `/system/proxy/mode': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Hmmm, have a look at this thread :
http://communities.vmware.com/message/1296461#1296461

otherwise :
http://communities.vmware.com/thread/214933

Worth looking at ?

Also :
http://jingfenghanmax.blogspot.com/2...s-setting.html

I would check to see if SElinux is running restrictively too.