When using the userpriv and usersandbox FEATUREs, vmware-workstation is installed incorrectly. The main executable is supposed to be suid root; its permissions include suid but the file is owned by portage:portage. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I'm not sure this is possible to fix. Vmware absolutely requires that a few of the binaries be SUID root, and as a non-root user, it is impossible to change the ownership of these binaries to root.
The files are still installed by root in the end...
Okay, I will move the relevant +s modifications into pkg_postinst
I had this same problem. Vmware will run fine as root, but not as a normal user. I tried moving the suid lines for vmware and vmware ping to the pkg_postinst section but the files are still owned by portage:portage. I dont understand the usersandbox and userpriv features enought to figure this out, so I just turned them off for the install. On a seperate point, one of the 4.0 builds needs to get unmasked since you can not get a new licence for the older 3.2 series. I also think there should be a einfo line that describes the init.d script. If some one can point me in the right direction for understanding usersandbox and userpriv I can work on this ebuild.
Please see the attachment to bug 20342. Does this fix the issue?
This is better, but the files still need to be chowned to root. Also, it seems to work fine when the vmware executable isn't SUID.
After these, it works fine: chown root:root /opt/vmware/bin/vmware chown root:root /opt/vmware/bin/vmware-ping chown root:root /opt/vmware/lib/bin/vmware-vmx chown root:root /opt/vmware/lib/bin-debug/vmware-vmx
New ebuild attached to bug 20342.
VMware binaries are now properly installed.
*** Bug 184524 has been marked as a duplicate of this bug. ***
