Whenever I start vmware-player, it displays: Unable to open the /usr/lib/vmware/licenses/site license directory: No such file or directory Patching the ebuild to create that directory at install makes that issue go away. I have attached a patch for the ebuild currently in portage.
Assignee: matt@whitlock.name did not match anything Please fix that in metadata.xml.
What version? Why player needs a license? You accept it when you download the product. I'm not aware of "site" license. Last time I checked there was none.
All versions of vmware player want a site license directory. If there is no site license, VMWare Player will complain if that folder is not present whenever a virtual machine is opened. This has been an issue since I started using VMWare Player several months ago, but I did not report it until now.
Richard, can you post your patch? I'm having the same issue using 3.1.4 directly from the vmware overlay. (It also appears to be missing the thinprint client, but I think that's a separate issue, but I do only get the message about the site license directory when I have a virtual printer attached and try to boot along with the missing thnuclnt message.)
Created attachment 273667 [details] VMWare Player ebuild modified to fix site license issue It is a small change to the ebuild. I have attached the ebuild my from local overlay.
Awesome, thanks. I've filed a separate bug for the thinprint issue including my patch-hack for fixing it in bug 367799, in case someone finds the thinprint issue through this bug.
(In reply to comment #3) > All versions of vmware player want a site license directory. If there is no > site license, VMWare Player will complain if that folder is not present > whenever a virtual machine is opened. This has been an issue since I started > using VMWare Player several months ago, but I did not report it until now. I've checked vmware installation on ubuntu and did not find site license directory either. So, what's make your player so special?
(In reply to comment #7) > (In reply to comment #3) > > All versions of vmware player want a site license directory. If there is no > > site license, VMWare Player will complain if that folder is not present > > whenever a virtual machine is opened. This has been an issue since I started > > using VMWare Player several months ago, but I did not report it until now. > > I've checked vmware installation on ubuntu and did not find site license > directory either. So, what's make your player so special? The latest version of vmware player from the overlay does not appear to suffer from this issue, so further examination is probably a moot point, but I think that something in the file system was different between our systems on the older version. I am marking this as obsolete.
