Segmentation Fault on system update

English Install/Boot/Login
#1

I’m new to openSUSE but not Linux. I’ve been on various flavors Ubuntu for the last decade. I switched over to OpenSUSE Tumbleweed with the KDE desktop this weekend and like the system so far. However, the system presented a number of updates today in the notifications. I approved the update but it quit early in the process. So, I went to the terminal and was offered:

$ sudo zypper ref
Repository ‘Packman Repository’ is up to date.
Repository ‘libdvdcss repository’ is up to date.
Repository ‘packman’ is up to date.
Repository ‘openSUSE-Tumbleweed-Debug’ is up to date.
Repository ‘openSUSE-Tumbleweed-Non-Oss’ is up to date.
Repository ‘openSUSE-Tumbleweed-Oss’ is up to date.
Repository ‘openSUSE-Tumbleweed-Source’ is up to date.
Repository ‘openSUSE-Tumbleweed-Update’ is up to date.
All repositories have been refreshed.
bob@bob-ubuntu:~$ sudo zypper up
Loading repository data…
Reading installed packages…

The following 27 package updates will NOT be installed:
k3b kernel-default kernel-default-devel libavcodec57 libavfilter6 libavformat57
libavresample3 libavutil55 libgstadaptivedemux-1_0-0 libgstbadaudio-1_0-0
libgstbadbase-1_0-0 libgstbadvideo-1_0-0 libgstbasecamerabinsrc-1_0-0
libgstcodecparsers-1_0-0 libgstgl-1_0-0 libgstmpegts-1_0-0 libgstphotography-1_0-0
libgsturidownloader-1_0-0 libgstwayland-1_0-0 libmjpegutils-2_0-0 libpostproc54
libquicktime0 libsox3 libswresample2 libswscale4 mjpegtools sox

The following 13 NEW packages are going to be installed:
kernel-devel-4.10.12-1.2 kernel-source-4.10.12-1.2 kernel-syms-4.10.12-1.2
python2-dbus-python python2-decorator python3-asn1crypto python3-cffi
python3-cryptography python3-dbus-python python3-idna python3-pyasn1 python3-pycparser
python3-pyOpenSSL

The following 2 applications are going to be REMOVED:
Desktop “System Tray”

The following 3 packages are going to be REMOVED:
dbus-1-python dbus-1-python3 python-decorator

The following 91 packages are going to be upgraded:
avahi bundle-lang-gnome-en cups-pk-helper dconf gio-branding-openSUSE girepository-1_0
glib2-tools gsettings-backend-dconf gstreamer-plugins-libav gtk4-schema gzip
kernel-macros krb5 krb5-32bit libavahi-client3 libavahi-client3-32bit libavahi-common3
libavahi-common3-32bit libavahi-core7 libavcodec56 libavformat56 libavutil54
libcroco-0_6-3 libdconf1 libdns_sd libgio-2_0-0 libgirepository-1_0-1 libglib-2_0-0
libgmodule-2_0-0 libgobject-2_0-0 libgraphite2-3 libgthread-2_0-0
libjavascriptcoregtk-4_0-18 libmysqlclient18 libmysqlclient_r18 libmysqld18 libosip2
libosip2-devel libpango-1_0-0 libpostproc53 libreoffice libreoffice-base
libreoffice-base-drivers-mysql libreoffice-branding-upstream libreoffice-calc
libreoffice-calc-extensions libreoffice-draw libreoffice-filters-optional
libreoffice-icon-theme-breeze libreoffice-icon-theme-galaxy
libreoffice-icon-theme-hicontrast libreoffice-icon-theme-oxygen
libreoffice-icon-theme-sifr libreoffice-impress libreoffice-kde4 libreoffice-l10n-en
libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-share-linker
libreoffice-writer libreoffice-writer-extensions libswresample1 libswscale3
libupower-glib3 libwebkit2gtk-4_0-37 mariadb mariadb-client mariadb-errormessages
MozillaFirefox openSUSE-release perl-Config-Crontab polkit-default-privs
python3-chardet python3-cupshelpers python3-requests python3-urllib3 quilt sddm
sddm-branding-openSUSE shim system-config-printer system-config-printer-applet
system-config-printer-common system-config-printer-dbus-service tuned
typelib-1_0-Pango-1_0 udev-configure-printer update-desktop-files upower
webkit2gtk-4_0-injected-bundles

The following product is going to be upgraded:
“openSUSE Tumbleweed”

91 packages to upgrade, 13 new, 3 to remove.
Overall download size: 285.6 MiB. Already cached: 4.9 MiB. After the operation,
additional 643.3 MiB will be used.
Continue? [y/n/…? shows all options] (y):

I said yes to start the update. Everything was downloaded, but the process locked up when checking for conflicts:

In cache gstreamer-plugins-libav-1.10.4-3.5.x86_64.rpm
(104/104), 197.4 KiB (476.1 KiB unpacked)
Checking for file conflicts: …<54%>==========================]^C
^C
Trying to exit gracefully…
Checking for file conflicts: …<54%>==========================|]Segmentation fault

I tried twice with the same result. Any ideas? I’m using the nouveau 1.0.15-34.2 video driver for nvidia if that matters. Appreciate any insights that anyone has.

#2

I am not sure I understand completely what goes wrong,but I see a few unusual things.

You seem to have the Packman repository two times. Remove one.

The libdvdcss repo does not change anymore, thus, after you installed from it, you can diasable it.

You seem to have the Source repo enabled. Is that on purpose?

And last but not least, Tumbleweed is not updated using

zypper up

but using

zypper dup --no-allow-vendor-change

Also I the KDE applet that shows you updates is rather useless in Tumbleweed. It will do the equivalent of zypper up (or at least tries do do that), but as said, that is not the way to go.

Maybe posting your repo list here might help people here to understand what you have:

zypper lr -d
#3

Thank you Henk. I don’t recall how the source repository was added, but I deleted it based on your observation. I also disabled the dvdcss repository. The packman repository is only on the YaST list once, so I’m not sure what happened there.

After making these corrections and using the command format that you provided, the update worked fine! Thank you so much for your help.

I have an unrelated question, if I may. I noticed that YaST2 does not always uninstall libraries/dependencies that were installed with a previously installed program. In Ubuntu, I used ‘apt-get autoremove’ to clean up orphans. Similarly, I could clean out the installation cache with ‘apt-get autoclean’. I cannot find a similar commands for zypper. How do I clean up the orphans and the installation cache?

Thank you again for your help!

#4

I talked about “disabling”, not “removing”. While you may not need the source repo at any time in the future, like the debug repo, it is added in disabled state at installation. So it is easy to enable when need arises.

You preferred not to post your repo list, thus any additional comment on it is a bit difficult.

I do not know anything about Ubuntu, thus comment on how things are done here compared to Ubuntu will ot come from me.
I assume you have used

man zypper

The question is asked here every now and then. Maybe try a search on the forums.

Removing packages that are installed as dependencies of packages that are installed, is a bit tricky. After some time of unspecified length) (hey can be dependencies of later installed packages and thus removing them will break those. They can even be not dependencies from any package, but only from the cat that the user wants to use them.
In YaST > Software > Software Management there is a VIEW Package Groups. There you will find at the bottom Orphanised Packages (or similar). I am not sure that is what you are looking for. IMHO those are packages that have no enabled repo anymore. There is also Not Needed (or similar, I have a Dutch translation here), not sure what that means.
Most people simply leae those. Most disks are large enough, no need to recover the space.

#5

YAST has a clean up under options in software management. From my use it will do a thorough job when things are uninstalled.

John

#6

Sorry, I misunderstood. I will get it back if I need it.

You preferred not to post your repo list, thus any additional comment on it is a bit difficult.

I did not post it because I got the update to work with your previous instructions. They are just the basic default repros plus packman. I’m not at that computer at the moment, otherwise I’d post them for you.

In YaST > Software > Software Management there is a VIEW Package Groups. There you will find at the bottom Orphanised Packages (or similar). I am not sure that is what you are looking for. IMHO those are packages that have no enabled repo anymore. There is also Not Needed (or similar, I have a Dutch translation here), not sure what that means.
Most people simply leae those. Most disks are large enough, no need to recover the space.

Thank you. I will check there. I like to keep the system as clean as possible. That’s just a personal preference.

Thank you again for all your help!

#7

Thank you! I will check that when I get home tonight.