Hi, during a zypper update, I stoped the update with <ctrl>+<c>. Seams to be that I stopped it during an updated of a required library (there was a segfault message visible). Now if I start "zypper", the following message is visible: zypper: error while loading shared libraries: libabsl_log_internal_check_op.so.2308.0.0: cannot open shared object file: No such file or directory According https://opensuse.pkgs.org/tumbleweed/opensuse-oss-x86_64/libabsl2308_0_0-202... the file should be available at https://ftp.lysator.liu.se/pub/opensuse/tumbleweed/repo/oss/x86_64/libabsl23... but it isn't. OK, so I downloaded the full folder with more than 2M files with: wget --no-parent -r https://ftp.lysator.liu.se/pub/opensuse/tumbleweed/repo/oss/x86_64/ --reject "index.html*" But still not there. I checked the dendencies but was not able to find the related package and installed all packages was there: # rpm -q --whatrequires zypper patterns-base-sw_management-20200505-47.1.x86_64 opi-5.0.0-1.1.noarch zypper-needs-restarting-1.14.68-1.4.noarch zypper-lifecycle-plugin-0.6.1601367426.843fe7a-3.8.noarch zypper-aptitude-1.14.68-1.4.noarch --> OK, I don't know if this is the right ones # rpm -qp zypper-1.14.68-1.4.x86_64.rpm --requires /bin/sh /bin/sh /bin/sh config(zypper) = 1.14.68-1.4 ld-linux-x86-64.so.2()(64bit) ld-linux-x86-64.so.2(GLIBC_2.3)(64bit) libaugeas.so.0()(64bit) libaugeas.so.0(AUGEAS_0.1.0)(64bit) libaugeas.so.0(AUGEAS_0.8.0)(64bit) libaugeas0 >= 1.10.0 libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.28)(64bit) libc.so.6(GLIBC_2.32)(64bit) libc.so.6(GLIBC_2.34)(64bit) libc.so.6(GLIBC_2.38)(64bit) libc.so.6(GLIBC_2.4)(64bit) libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.0)(64bit) libgcc_s.so.1(GCC_3.3.1)(64bit) libreadline.so.8()(64bit) libstdc++.so.6()(64bit) libstdc++.so.6(CXXABI_1.3)(64bit) libstdc++.so.6(CXXABI_1.3.5)(64bit) libstdc++.so.6(CXXABI_1.3.8)(64bit) libstdc++.so.6(CXXABI_1.3.9)(64bit) libstdc++.so.6(GLIBCXX_3.4)(64bit) libstdc++.so.6(GLIBCXX_3.4.11)(64bit) libstdc++.so.6(GLIBCXX_3.4.14)(64bit) libstdc++.so.6(GLIBCXX_3.4.15)(64bit) libstdc++.so.6(GLIBCXX_3.4.18)(64bit) libstdc++.so.6(GLIBCXX_3.4.20)(64bit) libstdc++.so.6(GLIBCXX_3.4.21)(64bit) libstdc++.so.6(GLIBCXX_3.4.26)(64bit) libstdc++.so.6(GLIBCXX_3.4.29)(64bit) libstdc++.so.6(GLIBCXX_3.4.30)(64bit) libstdc++.so.6(GLIBCXX_3.4.32)(64bit) libstdc++.so.6(GLIBCXX_3.4.9)(64bit) libxml2.so.2()(64bit) libxml2.so.2(LIBXML2_2.4.30)(64bit) libxml2.so.2(LIBXML2_2.5.0)(64bit) libxml2.so.2(LIBXML2_2.6.0)(64bit) libzypp >= 17.31.31 libzypp.so.1722()(64bit) libzypp.so.1722(ZYPP_plain)(64bit) procps rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsZstd) <= 5.4.18-1 --> This don't tell me the package name :-( Any idea how to repair zypper on a running system? PS: In worst case I need to boot a new install package and look it is possible to repair the system with an upgrade from an install disk Thanks Ulf