Bug 1160171

Confirmed. Seeing exactly the same

With a recently updated Tumbleweed and blender-2.81-2.1 and 
libOpenColorIO1-1.1.1-1.6 my blender starts without a problem but if you updated blender individually and it didn't pull in the updated libOpenColorIO1 then I will ensure that blender pulls in the library it was built with.
Please confirm that updating libOpenColorIO1 fixes this problem.

(In reply to Dave Plater from comment #2)
> With a recently updated Tumbleweed and blender-2.81-2.1 and 
> libOpenColorIO1-1.1.1-1.6 my blender starts without a problem but if you
> updated blender individually and it didn't pull in the updated
> libOpenColorIO1 then I will ensure that blender pulls in the library it was
> built with.
> Please confirm that updating libOpenColorIO1 fixes this problem.

Not sure how do I update libopencolorio further, I upgrade the system with sudo zypper dup, I did not update blender individually.

My current install is 
Information for package libOpenColorIO1:
----------------------------------------
Repository     : openSUSE-Tumbleweed-Oss                                                    
Name           : libOpenColorIO1                                                            
Version        : 1.1.1-1.6                                                                  
Arch           : x86_64                                                                     
Vendor         : openSUSE                                                                   
Installed Size : 1.0 MiB                                                                    
Installed      : Yes (automatically)                                                        
Status         : up-to-date                                                                 
Source package : OpenColorIO-1.1.1-1.6.src

I have an older snapshot and updating libyaml-cpp0_6 which used to export the missing symbol was older. I updated to the latest and now I can reproduce this bug. Possibly a build service problem, I will investigate and fix

Added yaml-cpp maintainer to cc list

Not quite sure where the problem lies, installing libOpenColorIO1 from graphics solves the problem but it is identical to Factory and has built and published. Must be some (Temporary?) problem between Factory and Tumbleweed.

(In reply to Dave Plater from comment #6)
> Not quite sure where the problem lies, installing libOpenColorIO1 from
> graphics solves the problem but it is identical to Factory and has built and
> published. Must be some (Temporary?) problem between Factory and Tumbleweed.

Seems a library changed ABI without bumping it's so-version.. shame on upstream; in this case I assume it was yaml-cpp.

for snapshot 0106, I triggered a bunch of rebuilds (like OpenImageIO) - which hopefully solve this issue.

If not, I'll have to trigger more rebuilds based on what all comes down the line of yaml-cpp.

Can you please test once 0106 is released? (should happen in the next couple hours)

Created sr#761813 to graphics/OpenColorIO to ensure that libOpenColorIO1 pulls in the version of libyaml-cpp0_6 it was built against.

Latest update on TW fix the issue, Blender works now.

The requested symbol (YAML::detail::node_data::empty_scalar[abi:cxx11]()) was added in yaml-cpp-0.6.3, which does not break ABI, only removing it would.

Unfortunately, we have no ABI tracking in openSUSE, and the library versioning dependencies are only weak.

For Tumbleweed, we explicitly request people always use "zypper dup", but even that does not ensure a consistent system when using e.g. "zypper in foo" - some dependencies may be old, but are yet satisfied. Only "zypper in foo; zypper dup" is sufficient is most cases.

Created attachment 827308 [details]
libyaml-cpp/0.6.2_to_0.6.3/compat_report.html

(In reply to Stefan Brüns from comment #10)
> The requested symbol (YAML::detail::node_data::empty_scalar[abi:cxx11]())
> was added in yaml-cpp-0.6.3, which does not break ABI, only removing it
> would.
> 
> Unfortunately, we have no ABI tracking in openSUSE, and the library
> versioning dependencies are only weak.
> 
> For Tumbleweed, we explicitly request people always use "zypper dup", but
> even that does not ensure a consistent system when using e.g. "zypper in
> foo" - some dependencies may be old, but are yet satisfied. Only "zypper in
> foo; zypper dup" is sufficient is most cases.

What confuses me the most is after a slightly earlier zypper dup I had identical version and builds to the reporters of libOpenColorIO1 and blender but version 0.6.2 of libyaml-cpp0_6 which worked. I could only reproduce the bug by installing version 0.6.3 of libyaml-cpp0_6. If you look at the attached compat_report.html from abi-compliance-checker you will see that although the abi has only additions the api has 8 symbols added and 6 removed.
Anyway requiring the specific version of libyaml-cpp0_6 will prevent this until this is fixed.

This bug also affects Calamares. See 
https://github.com/calamares/calamares/issues/1312#issuecomment-587258287

Please follow bug 1200624 to get more info.

SUSE-RU-2022:2640-1: An update that has four recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 1160171,1178331,1178332,1200624
CVE References: 
JIRA References: 
Sources used:
openSUSE Leap 15.4 (src):    yaml-cpp-0.6.3-150400.4.3.1
SUSE Linux Enterprise Module for Desktop Applications 15-SP4 (src):    yaml-cpp-0.6.3-150400.4.3.1
SUSE Linux Enterprise Module for Basesystem 15-SP4 (src):    yaml-cpp-0.6.3-150400.4.3.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.