When vmware-player is installed using the ebuild, it doesn't install thnuclnt, which is the thinprint client required for virtual printers to function properly inside virtual machines (sharing printers from cups). This is a problem because by default vmware-player will add a "virtual printer" to new machines it creates, which pops up an error message every time the machine boots about not being able to run thnuclnt. I've attached a patch for the ebuild that copies the necessary files to make this work, but it's definitely not completely optimal, so I would greatly appreciate some constructive input about how to make it better. Also, I'm pretty sure it doesn't need to copy the /etc/xdg stuff, but the original vmware-player installer did it, but our ebuild didn't, so I put it in just in case (wanted my virtual printers to work :P). Reproducible: Always Steps to Reproduce: 1. download vmware-player bundle 2. emerge vmware-player 3. create new virtual machine (ensuring that it has a virtual printer attached, but that should be the default) 4. boot the machine Actual Results: Error message before the BIOS loads about thnuclnt not being able to start, then the machine loads without virtual printer support. Expected Results: Machine loads with no error messages and a virtual printer attached.
Created attachment 273699 [details, diff] patch to vmware-player-3.1.4.385536.ebuild for installing thnuclnt properly Promised patch -- again, input would be appreciated, especially with regards to the static cups filter path I've included, since I'm sure there's a nice eclass or something to provide that properly.
matt@whitlock.name is not a known bugzilla user but still listed in metadata.xml.
Please use a newer version of the player, after all it's free. This bug is fixed since vmware-player-4.
