I have vmware-workstation 6.5 installed and it has been working fine with existing virtual machines. But I tried to create a new virtual machine, and as soon as I enter the menu item to create a new machine, it exited with no message that I could find. And I haven't been able to find any log files either.
I'm pretty sure this is some kind of path/permission issue -- I tried running vmware as "root" and it got into the machine creation dialog just fine. I think I'll go ahead and create the new VM as root just so I can get it built. In any event, the non-root user I am running as *is* in the vmware group, and the directory where I put VMs has group write for vmware, etc.
Created attachment 173403 [details]
Hiya Edward, according to a forum post this is caused by libsexymm. Could you please try uninstalling that, and see if you're then able to create virtual machines? If that works, could you please try rebuild libsexymm and let me know if it goes back to being broken or not? Thanks... 5:)
(In reply to comment #2)
> Hiya Edward, according to a forum post this is caused by libsexymm. Could you
> please try uninstalling that, and see if you're then able to create virtual
> machines? If that works, could you please try rebuild libsexymm and let me
> know if it goes back to being broken or not? Thanks... 5:)
1. I unmerged libsexymm and I can create virtual machines as non-root.
2. I re-emerged libsexymm and I can *still* create virtual machines as non-root!
Other possible clues:
I had a severe memory leak in Portage last night in "emerge -puvDN world". Portage was 2.2_rc15. I had to reboot the machine, and when I re-synced, it downgraded Portage to 2.1.6_rc2. I haven't bothered to check if this bug is in Bugzilla or tried to reproduce it.
vmware-workstation is the only thing using libsexymm:
DreamScape ~ # equery depends libsexymm
[ Searching for packages depending on libsexymm... ]
DreamScape ~ #
"revdep-rebuild" shows some breakage:
DreamScape ~ # revdep-rebuild -pv
* Checking dynamic linking consistency
[ 2% ] * broken /opt/vmware/workstation/bin/vmware-mount (requires libfuse.so.2)
[ 100% ]
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild I Rf ] app-emulation/vmware-workstation-126.96.36.199166 0 kB
Total: 1 package (1 reinstall, 1 interactive), Size of downloads: 0 kB
Fetch Restriction: 1 package
So it looks like there may be some other gotchas.
BTW, 6.5.1 is now available (bug 249068) and it looks like if you had 6.0, the 6.5.0 ebuild doesn't do a clean uninstall of 6.0.x (bug 248813) so whoever maintains the vmware-workstation ebuild has a good bit of testing to do. I ran into the unclean upgrade issues myself, but didn't file a bug because I may not have been running 6.0 from the ebuild -- I may have been using it straight from the VMware tarball.
I guess you can close this one as "unable to reproduce" :)
hmmm ... sys-fs/fuse was not even installed on my machine! Should it have been? I'm installing it now and re-emerging vmware-workstation
Installing sys-fs/fuse followed by re-emerging vmware-workstation seems to have fixed the revdep-rebuild complaints.
My guess is libsexymm needs gtkmm to have been built with USE="accessibility". If it hadn't been rebuilt after you enabled that, then vmware's precompiled binaries wouldn't have found the symbol (and everything would crash). I'm going to mark this as a duplicate of another bug...
As to clearing up the existing vmware conf directory, I'm not sure what to do about that, but I'll discuss it in the relevant bug. The mention of vmware-config.pl appears to be built into vmware even though they no longer ship it, so it looks like vmware have some testing to do too...
*** This bug has been marked as a duplicate of bug 235344 ***