| Summary: | app-emulation/vmware-workstation has incorrect default runtime configuration | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Chuck Wegrzyn <chuck.wegrzyn> |
| Component: | Current packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Chuck Wegrzyn
2008-06-30 15:45:20 UTC
Hi Chuck, First off, there's no way for an ebuild to specify what USE flags a dependent package must be built with. It simply isn't possible for one ebuild to affect another that way, and I'm fairly sure it's been designed like that. The best we can do is to give you a warning, so that you actually know how to fix the problem, rather than simply being told "Unknown symbol error" followed by some gibberish when you come to run the program (see bug 185444 and duplicates). Secondly, you have to run vmware as a user in the vmware group. I believe this is mentioned in the notes after vmware has been installed, where it also tells you to configure the system. Again, it would be difficult to allow non-vmware users to run vmware without either introducing vulnerabilities (by reducing the permissions necessary to run vmware) or by writing wrapper scripts simply to tell you something the ebuild notes have already told you. Please could you verify that running vmware as a member of the vmware group works correctly? If not, then you've got a real bug that we can investigate and try and solve. If it does all run correctly, there really isn't much to be gained from trying to protect the user if they don't follow the guidelines we've already provided. Hi All, In fact, I am having exactly the same problem. Although my system is a gradual update from 2007.0, I had a complete remove of the old workstation 5.5 and also removed all residual files in /etc/ and /opt directories. 1181 After a clean emerge of vmware-workstation 6.5.0.118166 followed by an emerge vmware-modules and emerge --config vmware-workstation, the errors in the original bug appears when the "vmware" script is run. My user account is the member of the "vmware" group. Is this a bug of the ebuild? I do not have know. But based on your last comment, it seems that the issue is still open. Best, Afsar. (In reply to comment #1) > Hi Chuck, > > First off, there's no way for an ebuild to specify what USE flags a dependent > package must be built with. It simply isn't possible for one ebuild to affect > another that way, and I'm fairly sure it's been designed like that. The best > we can do is to give you a warning, so that you actually know how to fix the > problem, rather than simply being told "Unknown symbol error" followed by some > gibberish when you come to run the program (see bug 185444 and duplicates). > > Secondly, you have to run vmware as a user in the vmware group. I believe this > is mentioned in the notes after vmware has been installed, where it also tells > you to configure the system. Again, it would be difficult to allow non-vmware > users to run vmware without either introducing vulnerabilities (by reducing the > permissions necessary to run vmware) or by writing wrapper scripts simply to > tell you something the ebuild notes have already told you. > > Please could you verify that running vmware as a member of the vmware group > works correctly? If not, then you've got a real bug that we can investigate > and try and solve. If it does all run correctly, there really isn't much to be > gained from trying to protect the user if they don't follow the guidelines > we've already provided. > Afsar, please double check that you've run etc-update or dispatch-conf, and that the file /etc/vmware/config is up-to-date. It should contain text entries that look as follows: libdir = "/opt/vmware/workstation/lib/vmware" bindir = "/opt/vmware/workstation/bin" Please check if those are present. If they're not, please try re-emerging vmware-workstation (in fact, upgrading to vmware-workstation-6.5.1, since 6.5.0 has now been masked), then make sure you do all the steps you mentioned *and* make sure you've run etc-update or dispatch-conf. Then if you're still having trouble, please paste the contents of /etc/vmware/config into this bug... |
