Description of problem: Some symbols in libglibmm-2.4.so.1 are C++ ABI only. This makes VMware Horizon Client for Linux application built against non-Fedora build of glibmm24 fail with unresolved symbols when attempting to run on Fedora 28. Version-Release number of selected component (if applicable): glibmm24-2.56.0-1.fc28.x86_64 vmware-horizon-client-4.9.0.9507999-1.x86_64 How reproducible: Always. Steps to Reproduce: 1. Install the latest VMware Horizon Client for Linux (64bit) https://my.vmware.com/web/vmware/details?downloadGroup=CART19FQ3_LIN64_490&productId=578&rPId=25730 2. Run vmware-view binary Actual results: $ vmware-view /usr/lib/vmware/view/bin/vmware-view-crtbora: symbol lookup error: /usr/lib/vmware/libcrtbora.so: undefined symbol: _ZN4Glib7ustring5beginEv Expected results: Application starts successfully like 4.8.0 did. Additional info: $ echo "_ZN4Glib7ustring5beginEv" | c++filt Glib::ustring::begin() glibmm24 provides this symbol, but in C++11 ABI version only: $ objdump -T /usr/lib64/libglibmm-2.4.so.1|grep _ZN4Glib7ustring.begin | awk '{ print $NF; }' | c++filt Glib::ustring::begin[abi:cxx11]() Only some symbols seem to have cxx11 ABI marker. For example, for ustring class: $ objdump -T /usr/lib64/libglibmm-2.4.so.1 | awk '{ print $NF; }' | c++filt | grep ustring|grep cxx11 |wc -l 42 $ objdump -T /usr/lib64/libglibmm-2.4.so.1 | awk '{ print $NF; }' | c++filt | grep ustring|egrep -v cxx11 |wc -l 347 Can this be "fixed" without recompiling the affected software? It's binary only and I have little hope of convincing VMware to provide a build for Fedora only. The closest they claim to support to Fedora is RHEL7.
I don't know the answer, but can you file this upstream at https://gitlab.gnome.org/GNOME/glibmm please? They understand the ABI issues best. Thanks!
Filed https://gitlab.gnome.org/GNOME/glibmm/issues/32 .
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.