vmware includes libpng.so.2, as far as I know it is used only to display the screenshot of a suspended machine (which is useful to me at least since I use a lot of vm's). However, it doesn't find the lib and displays errors: ** WARNING **: Unable to load module: libpixbufloader-png.so: libpng.so.2: cannot open shared object file: No such file or directory The problem is that vmware's code to discover library dependencies doesn't check the dependencies of the new libraries it adds to the LD_LIBRARY_PATH. As a workaround I linked /opt/vmware/lib/lib/libpng.so.2/libpng.so.2 to /usr/lib/libpng.so.2. I also come up with a somewhat nasty patch to /opt/bin/vmware that adds the right dir to LD_LIBRARY_PATH. Reproducible: Always Steps to Reproduce:
Created attachment 36543 [details, diff] patch against /opt/bin/vmware which checks libgdk_pixbuf dependencies The patch.
Sorry that this has been so long, but is this still the case with the latest vmware ebuild?
Yes I had to make the link in /usr/lib as above. vmware-workstation-4.5.2.8848-r1
*** Bug 63446 has been marked as a duplicate of this bug. ***
I know the error is slightly different between the 2 bugs, but I think the problem is the same. I am working on a new ebuild right now and hopefully iy'll fix the problem.
Try version 4.5.2.8848-r2 and see if this fixes your problem.
It doesn't. $ qpkg -I -v vmware app-emulation/vmware-workstation-4.5.2.8848-r2 * $ vmware ** WARNING **: Unable to load module: libpixbufloader-png.so: libpng.so.2: cannot open shared object file: No such file or directory ** WARNING **: Unable to load module: libpixbufloader-png.so: libpng.so.2: cannot open shared object file: No such file or directory ** WARNING **: Unable to load module: libpixbufloader-png.so: libpng.so.2: cannot open shared object file: No such file or directory ** WARNING **: Unable to load module: libpixbufloader-png.so: libpng.so.2: cannot open shared object file: No such file or directory ** WARNING **: Unable to load module: libpixbufloader-png.so: libpng.so.2: cannot open shared object file: No such file or directory
REOPEN
Created attachment 51561 [details, diff] vmware-bin.patch Here is my patch that I used successfully a while ago. It should take care of other possible awkward situations.
I know that this one seems to have been ignored, but I was wondering if this is a problem with VMware 5 or not. If this is only occurring in VMware 4, then I'll go ahead and add this patch to the latest ebuild for VMware 4, along with sending it upstream.
Seems fine now.
With 5.0 that is...
Sweet... thanks... I've fixed this in CVS for VMware 4.5 and revision bumped the package. I am unsure if this is required for VMware 3.x, but if anyone still uses it and wants to test it for me, then I'll gladly apply any necessary patches.
