Ciore dump on zypper update

zypper dup --no-recommends

Warning: You are about to do a distribution upgrade with all enabled repositorie
s. Make sure these repositories are compatible before you continue.
See ‘man zypper’ for more information about this command.
Retrieving repository ‘repo-debug’ metadata ----------------------------------------------------------------------------------------------------]
Segmentation fault (core dumped)

not sure why this is happening.

Zypper is crashing this should not happen. Be sure you do not have mixed repos is in doubt show zypper lr -d

The following 26 patterns are going to be upgraded:
apparmor apparmor_opt base basesystem devel_gnome devel_kde_frameworks devel_qt5 enhanced_base enhanced_base_opt gnome_basis gnome_basis_opt kde kde_games kde_imaging kde_internet kde_multimedia kde_office kde_plasma kde_utilities
kde_utilities_opt kde_yast minimal_base sw_management sw_management_gnome x11 x11_opt

The following product is going to be upgraded:
openSUSE Tumbleweed 20180804-0 -> 20180925-0

The following 2 packages are going to be downgraded:
fonttosfnt libwayland-egl1

1944 packages to upgrade, 2 to downgrade, 31 new, 9 to remove.
Overall download size: 1.62 GiB. Already cached: 7.9 MiB. After the operation, additional 460.3 MiB will be used.
**Continue? [y/n/…? shows all options] (y): **y
**Do you agree with the terms of the license? [yes/no] (no): **yes
In cache GeoIP-data-1.6.12-2.1.noarch.rpm (1/1977), 16.5 KiB ( 0 B unpacked)
In cache Mesa-libglapi0-18.1.7-208.1.x86_64.rpm (2/1977), 170.1 KiB (194.3 KiB unpacked)
In cache akonadi-mime-18.08.1-1.1.x86_64.rpm (3/1977), 27.9 KiB ( 46.6 KiB unpacked)
In cache alsa-oss-1.1.6-2.2.x86_64.rpm (4/1977), 40.3 KiB ( 91.9 KiB unpacked)
In cache apparmor-docs-2.13-5.1.noarch.rpm (5/1977), 307.8 KiB (356.0 KiB unpacked)
In cache attica-qt5-5.49.0-1.1.x86_64.rpm (6/1977), 32.1 KiB ( 26.7 KiB unpacked)
In cache bash-completion-2.8-1.1.noarch.rpm (7/1977), 250.9 KiB (804.7 KiB unpacked)
In cache bash-completion-devel-2.8-1.1.noarch.rpm (8/1977), 37.2 KiB ( 292 B unpacked)
In cache bash-completion-doc-2.8-1.1.noarch.rpm (9/1977), 52.9 KiB ( 57.0 KiB unpacked)
In cache bdftopcf-1.1-1.3.x86_64.rpm (10/1977), 37.8 KiB ( 64.9 KiB unpacked)
In cache binutils-2.31-1.2.x86_64.rpm (11/1977), 5.7 MiB ( 45.0 MiB unpacked)
In cache boost-license1_68_0-1.68.0-1.1.noarch.rpm (12/1977), 39.0 KiB ( 1.3 KiB unpacked)
In cache branding-openSUSE-15.0-3.3.noarch.rpm (13/1977), 22.0 KiB ( 1.6 KiB unpacked)
In cache breeze5-cursors-5.13.5-1.1.noarch.rpm (14/1977), 318.2 KiB ( 5.2 MiB unpacked)
Retrieving package breeze5-wallpapers-5.13.5-1.1.noarch (15/1977), 21.2 MiB ( 21.6 MiB unpacked)
Retrieving: breeze5-wallpapers-5.13.5-1.1.noarch.rpm <1%>============================================================================================================================================================================\ (2.1 MiB/s)]Segmentation fault (core dumped)

Now I get this. Wow, this is fun!

~ # zypper lr -d
Repository priorities are without effect. All enabled repositories share the same priority.

| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service

–±-------------±-------------±--------±----------±--------±---------±-------±-----------------------------------------------------±-------
1 | repo-debug | repo-debug | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/debug |
2 | repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss |
3 | repo-oss | repo-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss |
4 | repo-update | repo-update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |

This could be caused by a corrupted rpm database. To fix that, and eliminate it as a culprit:


sudo rpm --rebuilddb

su -
Password:
mumble:~ # rpm --rebuilddb
mumble:~ # zypper dup --no-recommends
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
Loading repository data…
Reading installed packages…
Computing distribution upgrade…

The following 31 NEW packages are going to be installed:
boost-license1_68_0 freecell-solver-presets kernel-default-4.18.8-1.3 libKPimItinerary5 libKPimPkPass5 libSPIRV-Tools-suse7 libaom0 libboost_date_time1_68_0
libboost_filesystem1_68_0 libboost_iostreams1_68_0 libboost_regex1_68_0 libboost_system1_68_0 libboost_thread1_68_0 libcfitsio6 libcodec2-0_8 libfind3_0
libfreecell-solver0 libhdf5-103 libicu-suse62_1 libicu62_1-ledata libntfs-3g88 libpoppler79 libqalculate19 libraw19 librmt1_0 python2-pyxb python3-rpm python3-solv
rpm-config-SUSE sasl2-kdexoauth2-3 schily-rmt

The following 9 packages are going to be REMOVED:
libSPIRV-Tools-suse6 libgsystem0 libhdf5-101 libntfs-3g87 libraw16 libwayland-egl-devel python-pyxb star-rmt typelib-1_0-GSystem-1_0

The following 1944 packages are going to be upgraded:

The following 26 patterns are going to be upgraded:
apparmor apparmor_opt base basesystem devel_gnome devel_kde_frameworks devel_qt5 enhanced_base enhanced_base_opt gnome_basis gnome_basis_opt kde kde_games kde_imaging
kde_internet kde_multimedia kde_office kde_plasma kde_utilities kde_utilities_opt kde_yast minimal_base sw_management sw_management_gnome x11 x11_opt

The following product is going to be upgraded:
openSUSE Tumbleweed 20180804-0 -> 20180925-0

The following 2 packages are going to be downgraded:
fonttosfnt libwayland-egl1

1944 packages to upgrade, 2 to downgrade, 31 new, 9 to remove.
Overall download size: 1.62 GiB. Already cached: 7.9 MiB. After the operation, additional 460.3 MiB will be used.
**Continue? [y/n/…? shows all options] (y): **
**Do you agree with the terms of the license? [yes/no] (no): **yes
In cache GeoIP-data-1.6.12-2.1.noarch.rpm (1/1977), 16.5 KiB ( 0 B unpacked)
In cache Mesa-libglapi0-18.1.7-208.1.x86_64.rpm (2/1977), 170.1 KiB (194.3 KiB unpacked)
In cache akonadi-mime-18.08.1-1.1.x86_64.rpm (3/1977), 27.9 KiB ( 46.6 KiB unpacked)
In cache alsa-oss-1.1.6-2.2.x86_64.rpm (4/1977), 40.3 KiB ( 91.9 KiB unpacked)
In cache apparmor-docs-2.13-5.1.noarch.rpm (5/1977), 307.8 KiB (356.0 KiB unpacked)
In cache attica-qt5-5.49.0-1.1.x86_64.rpm (6/1977), 32.1 KiB ( 26.7 KiB unpacked)
In cache bash-completion-2.8-1.1.noarch.rpm (7/1977), 250.9 KiB (804.7 KiB unpacked)
In cache bash-completion-devel-2.8-1.1.noarch.rpm (8/1977), 37.2 KiB ( 292 B unpacked)
In cache bash-completion-doc-2.8-1.1.noarch.rpm (9/1977), 52.9 KiB ( 57.0 KiB unpacked)
In cache bdftopcf-1.1-1.3.x86_64.rpm (10/1977), 37.8 KiB ( 64.9 KiB unpacked)
In cache binutils-2.31-1.2.x86_64.rpm (11/1977), 5.7 MiB ( 45.0 MiB unpacked)
In cache boost-license1_68_0-1.68.0-1.1.noarch.rpm (12/1977), 39.0 KiB ( 1.3 KiB unpacked)
In cache branding-openSUSE-15.0-3.3.noarch.rpm (13/1977), 22.0 KiB ( 1.6 KiB unpacked)
In cache breeze5-cursors-5.13.5-1.1.noarch.rpm (14/1977), 318.2 KiB ( 5.2 MiB unpacked)
Retrieving package breeze5-wallpapers-5.13.5-1.1.noarch (15/1977), 21.2 MiB ( 21.6 MiB unpacked)
Retrieving: breeze5-wallpapers-5.13.5-1.1.noarch.rpm …<7%>=================================================================================================\ (3.1 MiB/s)]Segmentation fault (core dumped)

What happens if you first try only to update zypper?


zypper in -f zypper-log-1.14.8-2.1.noarch zypper-aptitude-1.14.8-2.1.noarch zypper-1.14.8-2.1.x86_64 zypper-lifecycle-plugin-0.6.1490613702.a925823-2.4.noarch

EDIT: And please post output between CODE tags, the # in the editor’s layout ribbon

Sorry I did not see this before: what happens if you disable the debug repo ?

mumble:~ # zypper in -f zypper-log-1.14.8-2.1.noarch zypper-aptitude-1.14.8-2.1.noarch zypper-1.14.8-2.1.x86_64 zypper-lifecycle-plugin-0.6.1490613702.a925823-2.4.noarch
Loading repository data…
Reading installed packages…
Forcing installation of ‘zypper-1.14.8-2.1.x86_64’ from repository ‘repo-oss’.
Forcing installation of ‘zypper-aptitude-1.14.8-2.1.noarch’ from repository ‘repo-oss’.
Forcing installation of ‘zypper-lifecycle-plugin-0.6.1490613702.a925823-2.4.noarch’ from repository ‘repo-oss’.
Forcing installation of ‘zypper-log-1.14.8-2.1.noarch’ from repository ‘repo-oss’.
Resolving package dependencies…
The following 3 NEW packages are going to be installed:
boost-license1_68_0 libboost_system1_68_0 libboost_thread1_68_0
The following 5 packages are going to be upgraded:
libsolv-tools libzypp zypper zypper-aptitude zypper-log
The following package is going to be reinstalled:
zypper-lifecycle-plugin
5 packages to upgrade, 3 new, 1 to reinstall.
Overall download size: 4.3 MiB. Already cached: 39.0 KiB. After the operation, additional 783.8 KiB will be used.
Continue? [y/n/…? shows all options] (y):
In cache boost-license1_68_0-1.68.0-1.1.noarch.rpm (1/9), 39.0 KiB ( 1.3 KiB unpacked)
Retrieving package zypper-log-1.14.8-2.1.noarch (2/9), 68.7 KiB ( 6.1 KiB unpacked)
Retrieving: zypper-log-1.14.8-2.1.noarch.rpm …[done]
Retrieving package libboost_system1_68_0-1.68.0-1.1.x86_64 (3/9), 43.9 KiB ( 22.4 KiB unpacked)
Retrieving: libboost_system1_68_0-1.68.0-1.1.x86_64.rpm …[done]
Retrieving package libboost_thread1_68_0-1.68.0-1.1.x86_64 (4/9), 82.0 KiB (179.5 KiB unpacked)
Retrieving: libboost_thread1_68_0-1.68.0-1.1.x86_64.rpm …[done]
Retrieving package libsolv-tools-0.6.35-1.1.x86_64 (5/9), 594.7 KiB ( 4.8 MiB unpacked)
Retrieving: libsolv-tools-0.6.35-1.1.x86_64.rpm …[done]
Retrieving package libzypp-17.7.0-1.1.x86_64 (6/9), 2.2 MiB ( 7.9 MiB unpacked)
Retrieving: libzypp-17.7.0-1.1.x86_64.rpm ------------------------------------------------------------------------------------[starting]Segmentation fault (core dumped)

I see that poster’s problem is crashing while downloading in all 3 logs, smells like a hardware issue to me. Or corrupted binaries. Or both.

Yea, go with the easy answer. The old corrupted binaries and hardware issue.

Try force install zypper from yast.

or download the rpm and use rpm to install bypassing zypper entirely

It’s visibly crashing while downloading packages. The odds of a hardware issue are very high, imho. Can you run a memory tester? Or prime95 in test mode?

Try this:


zypper clean
zypper ref

and post the output here

And please post output of


df -h

And please post this between CODE tags, the # in the editor. Use Ctrl-Shift-V to paste, so that these colors that make things unreadable on a light background.

We need to find out if you’re not running in to a corrupted zypper cache, or a full filesystem.

To find out if it’s not a hardware problem, you could create a Live USB stick, and see if zypper segfaults inthere too.

looks like an issue with the encryption library on my server.

The following product is going to be upgraded:
openSUSE Tumbleweed 20180804-0 -> 20190201-0

The following 5 packages are going to be downgraded:
fonttosfnt 1.0.5+20170126.aead36f-1.6 -> 1.0.5-1.3
libKF5Syndication5 18.04.3-1.1 -> 5.54.0-1.1
libwayland-egl1 18.1.4-203.1 -> 1.16.0-3.2
python2-backports 4.0.0-3.1 -> 1.0.0-1.2
rpmdevtools 8.10-9.d_t.2 -> 8.10-3.2

The following 2 packages are going to change architecture:
python3-javapackages 5.2.0+git20180620.70fa2258-1.1 -> 5.3.0-2.2 x86_64 -> noarch
xorg-x11-libX11-ccache 7.6-20.6 -> 7.6-21.2 noarch -> x86_64

The following package is going to change vendor:
rpmdevtools 8.10-9.d_t.2 -> 8.10-3.2 obs://build.opensuse.org/devel:tools -> openSUSE

3649 packages to upgrade, 5 to downgrade, 101 new, 58 to remove, 1 to change vendor, 2 to change arch.
Overall download size: 2.38 GiB. Already cached: 2.7 MiB. After the operation, additional 987.8 MiB will be used.
**Continue? [y/n/…? shows all options] (y): **y
Detaching after fork from child process 7307.
/usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
/usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
**Do you agree with the terms of the license? [yes/no] (no): **yes
Detaching after fork from child process 7317.
/usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
/usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
**Do you agree with the terms of the license? [yes/no] (no): **yes
Detaching after fork from child process 7327.
committing
Detaching after fork from child process 7329.
Detaching after fork from child process 7331.
Detaching after fork from child process 7333.
In cache AdobeICCProfiles-2.0-155.14.noarch.rpm (1/3755), 2.5 MiB ( 5.4 MiB unpacked)
In cache GeoIP-data-1.6.12-2.2.noarch.rpm (2/3755), 13.0 KiB ( 0 B unpacked)
In cache Mesa-KHR-devel-18.3.1-210.2.x86_64.rpm (3/3755), 118.5 KiB ( 10.0 KiB unpacked)
In cache MozillaFirefox-branding-openSUSE-45-4.2.x86_64.rpm (4/3755), 12.2 KiB ( 8.4 KiB unpacked)
In cache akonadi-mime-18.12.1-1.1.x86_64.rpm (5/3755), 29.3 KiB ( 46.6 KiB unpacked)
Retrieving package alsa-docs-1.1.8-1.1.noarch (6/3755), 822.4 KiB ( 13.0 MiB unpacked)
Retrieving: media …[done]
Retrieving: alsa-docs-1.1.8-1.1.noarch.rpm ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[starting]Detaching after fork from child process 7337.
Detaching after fork from child process 7338.
Detaching after fork from child process 7339.
Detaching after fork from child process 7340.
Detaching after fork from child process 7341.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff57cf2b0 in X509_get_subject_name () from /usr/local/lib64/libcrypto.so.1.1

Hi
That would be likely due to the long delay between upgrading… 20180804-0 ==>>> 20190201-0

Looks like to me that you’ve got a mish-mash of rpms from different tumbleweed versions already. Be sure to use “zypper dup”.

I question some of the replies in this thread…

I have been trying about once a month to update my Tumbleweed install and today it finally worked. Have I done something, No. This happened once before but it took about 6 months for it to start working again.

First reported problem date: 20-Sep-2018
Working date: 30-Nov-2019

just tried zipper dup --no-recommends

and it updated.

Thank you to who ever fixed my issue, out there in tumbleweed land!!!