Closed u0m3 closed 10 years ago
Sorry I didn't get the notification faster, u0m3. Can you run "bash -x ./vmware -i" please and post the results?
The check that's failing is looking for the vmware-vmx in an internal variable called $ULIB - I think it may be getting that wrong on your platform. Running this as non-root will run the appropriate code for me to see what it's choosing for your $ULIB value.
My primary VMware system is a Kubuntu 14.04 box, so your vmware-vmx is in the same location, with the same permissions as mine: rob@kubuntu4:~/workspace/vmware-bumblebee$ ls -l /usr/lib/vmware/bin/vmware-vmx* -rwsr-xr-x. 1 root root 897 Jun 11 10:56 /usr/lib/vmware/bin/vmware-vmx -rwsr-xr-x. 1 root root 24410904 Jun 11 10:06 /usr/lib/vmware/bin/vmware-vmx-debug -rwsr-xr-x. 1 root root 19530384 Jun 11 10:06 /usr/lib/vmware/bin/vmware-vmx.real -rwsr-xr-x. 1 root root 14499064 Dec 4 2013 /usr/lib/vmware/bin/vmware-vmx.real.17443 -rwsr-xr-x. 1 root root 22260400 Jun 11 10:06 /usr/lib/vmware/bin/vmware-vmx-stats
So the ULIB variable is the most likely culprit.
[alex@thor ~]$ sudo bash -x /home/alex/bin/vmware -i
+ ACADAPTER='/sys/bus/acpi/drivers/ac/ACPI0003\:00/power_supply/AC/online'
+ BATTERY='/sys/bus/acpi/drivers/battery/PNP0C0A\:00/power_supply/BAT0'
+ FORCE3D=a
+ DO3D=n
+ echo -i
+ egrep -q -w '(help|h|\?)'
+ '[' 1 -eq 0 ']'
++ which gksudo
which: no gksudo in (/sbin:/bin:/usr/sbin:/usr/bin)
+ '[' -x ']'
++ which gksudo
which: no gksudo in (/sbin:/bin:/usr/sbin:/usr/bin)
+ SUDO=' -k'
+ determineos
++ uname -p
+ ARCH=x86_64
++ which dpkg
which: no dpkg in (/sbin:/bin:/usr/sbin:/usr/bin)
+ '[' ']'
++ which rpm
+ '[' /bin/rpm ']'
+ OStype=rpm
+ '[' -f /etc/redhat-release ']'
+ DISTRO=rhel
+ LIB32=/lib
+ ULIB32=/usr/lib
+ LIB64=/lib64
+ ULIB64=/usr/lib64
+ NVIDIA_DEST32=/usr/lib/linux-gnu
+ NVIDIA_DEST64=/usr/lib64/x86_64-linux-gnu
+ '[' x86_64 = x86_64 -o x86_64 = amd64 ']'
+ ULIB=/usr/lib64
+ LIB=/lib64
+ NVIDIA_DEST=/usr/lib64/x86_64-linux-gnu
+ '[' -z /usr/lib64 ']'
+ '[' -z /lib64 ']'
+ '[' -z rhel ']'
+ '[' -z /usr/lib64/x86_64-linux-gnu ']'
+ export ARCH
+ export DISTRO
+ export OStype
+ export ULIB
+ export LIB
+ export NVIDIA_DEST
+ echo -i
+ egrep -q -w '(yes|y|f|force)'
+ '[' 1 -eq 0 ']'
+ echo -i
+ egrep -q -w '(n|no)'
+ '[' 1 -eq 0 ']'
+ echo -i
+ egrep -q -w '(i|install)'
+ '[' 0 -eq 0 ']'
+ '[' root = root ']'
+ installvmx_script
+ '[' -x /usr/lib64/vmware/bin/vmware-vmx ']'
+ echo 'ERROR: vmware-vmx is not executable!'
ERROR: vmware-vmx is not executable!
+ echo 'Don'\''t know how to continue!'
Don't know how to continue!
+ exit 16
Also I should have mentioned that I am using Fedora 20 kernel 3.14.8-200.fc20.x86_64. And as a side note, Fedora does not seem to have gksudo.
I've downloaded Fedora 20 so I can check out a few locations in a VM. I'll check in an update later today - please try that when you see it post, and let me know if it fixes it. You're actually seeing 2 problems (the check for gksudo should fall down to gksu, which is installed by default, and it's not picking that up).
u0m3: I'm having a hard time getting my Fedora system running - is there a "/usr/lib64" on your system that's a real directory, like my script is expecting? I'm going to check in a change that simply assumes that for now, but will be looking for feedback. Thanks.
u0m3 - please let me know if v 1.5 fixes these issues for you. Please re-open this issue if they don't.
I received this error while installing:
vmware-vmx permissions: