I agree - there’s something weird with the installation of glibc here - two versions, and one that is identified as being from @System (which I infer to mean that it was installed outside of zypper). That could well be confusing things here.
Specifically:
( 4/10) Removing glibc-2.31-150300.58.1.x86_64 ..............................................................................................................................................[error]
Removal of (143411)glibc-2.31-150300.58.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): i
My original suggestions is: “Deactivate “user friendly” GUIs and stick to KISS.” @KermitXYZ relied on the “system tray icon” and a mess was created as exposed at the end of post #19.
I experienced similar issues when using plasma5-pk-updates. No issues occurred during a decade when relying on plain zypper and performing thousands of upgrades and updates on dozens of machines. As a consequence I removed this package and PackageKit on all machines I am maintaining.
They don’t have the experience or background to understand the consequences of their action and if those consequences are things they can live with.
Running zypper --non-interactive dist-upgrade in Tumbleweed or zypper --non-interactive update can have unwanted consequences on rare occasions. Actions performed are easily undone by booting into a previous snapshot and running snapper rollback. No experience required.
So error message is correct, there is no glibc-2.31-150300.58.1 package and derivatives. Looks like zypper metadata is out of sync with RPM database. Show
date
ls -l /var/lib/rpm
ls -l /usr/lib/sysimage/rpm
ls -l /var/cache/zypp/solv/@System/
@KermitXYZ Your issue was not caused by any graphical tool. You can safely ignore Karls statement as it is not backed by facts (it is his personal opinion limited to his hosts…). The official openSUSE documentation even refers to graphical tools for Leap update (like GNOME package updater and so on…) and YaST online update:
SUSE offers a continuous stream of software security updates for your product. By default, the update applet is used to keep your system up to date.
It is FUD that graphical tools will cause issues like yours. The graphical tools use the same underlying commands (zypper, rpm). The only disadvantage of graphical tools is, that they are not the same verbose like commands in a terminal…
This may come as a surprise to you, but most new users to openSUSE have no idea what btrfs is, what snapper is or does, or how to rollback an installation. This is “the curse of experience” - you forget what it is to actually not have any experience with the tools you’re using, because you use them every day.
Again, please stick to information that actually helps with this user’s issue and follows best practices.
Previously I had problems with updates by using KDE’s “Plasma applet for software updates using PackageKit”. Using PackageKit is simpler than zypper or YaST, but PackageKit tries to solve collisions by itself, and it often does it in unoptimal way.
I think it is fair to say that what Karl sees on his systems is not something that should be called “false”. Whether it is applicable to this situation is another issue.
ILL PackageKit cannot update system components. Well, it can, but with some side effects. It installed new glibc packages, but couldn’t delete previous ones. Possibly because PackageKit uses glibc and cannot jump to updated version. It needs stop & start, but doesn’t do this.
And PackageKit runs with user privileges (?).
Zypper & YaST can update system components without troubles.
When you want to update system components, you can use zypper or YaST, and reboot after that.
Backend is packagekit.service running in the system slice, which is a sane procedure. Out of curiosity I upgraded Tumbleweed from 20231016 to 20240107 using the applet in the system tray. Needed to run twice, upgrading some 1400 packages and another 25.
openSUSE Documentation on system upgrade is available: