http://bugzilla.suse.com/show_bug.cgi?id=1168735 Bug ID: 1168735 Summary: [Tumbleweed] [20200402] RPM segfaults when installing glibc-locale (and some other pkgs) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@suse.de Reporter: dheidler@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 834966 --> http://bugzilla.suse.com/attachment.cgi?id=834966&action=edit zypper logfile zypper in -f glibc-locale Loading repository data... Reading installed packages... Forcing installation of 'glibc-locale-2.31-3.2.x86_64' from repository 'Haupt-Repository (OSS)'. Resolving package dependencies... The following package is going to be upgraded: glibc-locale 1 package to upgrade. Overall download size: 0 B. Already cached: 12.7 MiB. No additional space will be used or freed after the operation. Continue? [y/n/v/...? shows all options] (y): In cache glibc-locale-2.31-3.2.x86_64.rpm (1/1), 12.7 MiB (212.7 MiB unpacked) Checking for file conflicts: ...............................................................................................................................................................................[done] (1/1) Installing: glibc-locale-2.31-3.2.x86_64 ............................................................................................................................................................[error] Installation of glibc-locale-2.31-3.2.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command was killed by signal 11 (Segmentation fault). Abort, retry, ignore? [a/r/i] (a): When manually downloading the binaries from OBS and executing RPM like zypper would, I get the same result: 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--noglob' '--force' '--nodeps' '--' ~dheidler/Downloads/glibc-locale-2.31-3.2.x86_64.rpm %% 0.000000 %% 0.000000 %% 50.000000 Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.