Description of problem: The symbol _ZN4YAML6detail9node_data12empty_scalarB5cxx11E (YAML::detail::node_data::empty_scalar[abi:cxx11]) is no longer provided by /lib64/libyaml-cpp.so.0.6. OpenColorIO-1.1.1-2.fc31's /lib64/libOpenColorIO.so.1 requires it, so this breaks OpenColorIO and applications that use it such as Blender. Version-Release number of selected component (if applicable): 0.6.3-1.fc31 does not have the symbol 0.6.2-3.fc31 has. How reproducible: 100% Steps to Reproduce: 1. Try to start blender from a terminal Actual results: blender: symbol lookup error: /lib64/libOpenColorIO.so.1: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11E Expected results: Blender's main window appears. Additional info: The symbol _ZN4YAML6detail9node_data12empty_scalarB5cxx11Ev (a parameterless function of the same name) exists instead in the new version only, so this is probably caused by this commit: https://github.com/jbeder/yaml-cpp/commit/774f25800e6f19f4b927023c85d1389af322da5e
I can confirm the bug, thanks for finding the problem. Unfortunately, reverting the commit that removes the symbol results in a different error: OpenColorIO Error: Error: Loading the OCIO profile '/usr/share/blender/2.80/datafiles/colormanagement/config.ocio' failed. The specified file does not appear to be an OCIO configuration.
Here's a fork of the RPM repo that reverts the commit: https://src.fedoraproject.org/fork/thofmann/rpms/yaml-cpp/c/54066695bcc9381ddf7c147cd333705d569a6ca9?branch=f31 I also unpushed the F30 update.
Updated OpenColorIO rebuilt for Yaml-cpp allowed Blender to start.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.