VMware – Fedora 23 Breaks vmware app, and a Workaround..

Although VMware 12.0.1 was installed OK, the desktop app (/usr/bin/vmware) fails, with – frustratingly – no error shown..    According to various comments found, this is due to a change to GCC version 5.1.1 in Fedora 23..

Thanks to Vincent Cojot, on the sgros.blogspot.com blog, there is a slightly convoluted workaround, which basically involves replacing the VMware versions of the libgxxx modules with the Fedora 23 versions, and then forcing vmware to use these..

The shell command shown on the blog was messed up by formatting, so I just made the changes manually, as follows

As root, cd to /usr/lib/vmware/lib

then:

# cp -afv /usr/lib64/libgio-2.0.so.0.4600.1 libgio-2.0.so.0/libgio-2.0.so.0
# cp -afv /usr/lib64/libglib-2.0.so.0.4600.1 libglib-2.0.so.0/libglib-2.0.so.0
# cp -afv /usr/lib64/libgmodule-2.0.so.0.4600.1 libgmodule-2.0.so.0/libgmodule-2.0.so.0
# cp -afv /usr/lib64/libgobject-2.0.so.0.4600.1 libgobject-2.0.so.0/libgobject-2.0.so.0
# cp -afv /usr/lib64/libgthread-2.0.so.0.4600.1 libgthread-2.0.so.0/libgthread-2.0.so.0

The VMware libraries are each in their own individual directory, with the same name as that library..     Of course, the Fedora 23 library versions may change over time..

After that, run the vmware app forcing the use of the copied libraries:

# VMWARE_USE_SHIPPED_LIBS=force vmware

And..  vmware works again..

Robert Gadsdon.    November 4, 2015


Comments

VMware – Fedora 23 Breaks vmware app, and a Workaround.. — 4 Comments

  1. On Ubuntu 15.10, which suffers the same gcc5 issues, it was sufficient to just use:

    env VMWARE_USE_SHIPPED_LIBS=1 /usr/bin/vmware

    Which is probably just equivalent to your “force”, but I didnt have to copy any libraries into the vmware tree.

    • Thanks for the info.. I tried this on Fedora 23, but # vmware just gave a GTK warning, and then ended.. Still needs the ‘copied’ libs..

      RG.

  2. Same happens with openSUSE Tumbleweed (GCC 5.2.1 is used). Also vmmon needs to be patched for 4.3.0 for some reason.

Leave a Reply

Your email address will not be published. Required fields are marked *