(In reply to Richard Fan from comment #6) > (In reply to Max Lin from comment #5) > > This report seem to be dated, we did update qgis to 3.34.1 in Leap 15.6, > > could you please retest it on the latest snapshot? > > https://openqa.opensuse.org/tests/ > latest?arch=x86_64&distri=opensuse&flavor=DVD- > Updates&machine=64bit&test=extra_tests_gnome&version=15.6#step/qgis/21 > > New errrors below: > > > >Processing conflicts - 0 > >0| 2024-05-13 05:10:45 <3> susetest(17667) [zypp::solver] > SATResolver.cc(solving):865 So… Conflict > >Processing conflicts - 0 > >0| 2024-05-13 05:10:45 <3> susetest(17667) [zypp::solver] > SATResolver.cc(solving):865 Solverrun finished with an ERROR > >0| 2024-05-13 05:10:45 <2> susetest(17667) [zypp::solver] > SATResolver.cc(resolvePool):937 SATResolver::resolvePool() done. Ret:0 > >0| 2024-05-13 05:10:45 <1> susetest(17667) [zypp::solver] > Resolver.cc(problems):423 Resolver::problems() > >0| 2024-05-13 05:10:45 <1> susetest(17667) [zypp::solver] > SATResolver.cc(problems):1369 Encountered problems! Here are the solutions: > >0| 2024-05-13 05:10:45 <1> susetest(17667) [zypp::solver] > SATResolver.cc(problems):1369 > >0| 2024-05-13 05:10:45 <1> susetest(17667) [zypp::solver] > SATResolver.cc(problems):1373 Problem 1: > >0| 2024-05-13 05:10:45 <1> susetest(17667) [zypp::solver] > SATResolver.cc(problems):1374 ==================================== > >0| 2024-05-13 05:10:45 <1> susetest(17667) [zypp::solver] > SATResolver.cc(problems):1378 nothing provides 'libhdf5.so.103()(64bit)' > needed by the to be installed qgis-3.34.1-bp156.1.4.x86_64 > >0| 2024-05-13 05:10:45 <1> susetest(17667) [zypp::solver] > SATResolver.cc(problems):1379 ------------------------------------ > >0| 2024-05-13 05:10:45 <1> susetest(17667) [libsolv++] > PoolImpl.cc(logSat):131 solver statistics: 0 learned rules, 0 unsolvable, 0 > minimization steps > >EOL Yes, that is an known issue https://bugzilla.suse.com/show_bug.cgi?id=1224144, but it was a different issue than this report, and the hdf5 problem has been fixed in Build691.1, if you test it again now it should not happened.