The package glibc is essential to correct operation and cannot be removed using this tool

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

Is your view similar?

rpm -qa glibc\*

glibc-locale-base-2.31-150300.63.1.x86_64
glibc-extra-2.31-150300.63.1.x86_64
glibc-locale-2.31-150300.63.1.x86_64
glibc-32bit-2.31-150300.63.1.x86_64
glibc-2.31-150300.63.1.x86_64
glibc-lang-2.31-150300.63.1.noarch
glibc-devel-2.31-150300.63.1.x86_64

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/

What is the correct terminology please?

1 Like

@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…

1 Like
rmp@W9020:~> date
Thu  4 Jan 15:06:34 GMT 2024
rmp@W9020:~> ls -l /var/lib/rpm
lrwxrwxrwx 1 root root 26 Aug 14 11:40 /var/lib/rpm -> ../../usr/lib/sysimage/rpm
rmp@W9020:~> ls -l /usr/lib/sysimage/rpm
total 313244
-rw-r--r-- 1 root root  10006528 Jan  3 17:51 Basenames
-rw-r--r-- 1 root root     24576 Jan  3 17:51 Conflictname
-rw-r--r-- 1 root root   4857856 Jan  3 17:51 Dirnames
-rw-r--r-- 1 root root      8192 Dec 30 22:04 Enhancename
-rw-r--r-- 1 root root      8192 Dec 30 22:04 Filetriggername
-rw-r--r-- 1 root root     45056 Jan  3 17:51 Group
-rw-r--r-- 1 root root     57344 Jan  3 17:51 Installtid
-rw-r--r-- 1 root root    139264 Jan  3 17:51 Name
-rw-r--r-- 1 root root     77824 Jan  3 17:51 Obsoletename
-rw-r--r-- 1 root root 296697856 Jan  3 17:51 Packages
-rw-r--r-- 1 root root   6742016 Jan  3 17:51 Providename
-rw-r--r-- 1 root root     45056 Jan  3 17:51 Recommendname
-rw-r--r-- 1 root root    921600 Jan  3 17:51 Requirename
-rw-r--r-- 1 root root    233472 Jan  3 17:51 Sha1header
-rw-r--r-- 1 root root    143360 Jan  3 17:51 Sigmd5
-rw-r--r-- 1 root root     16384 Dec 30 22:04 Suggestname
-rw-r--r-- 1 root root    733184 Jan  3 17:49 Supplementname
-rw-r--r-- 1 root root      8192 Dec 30 22:04 Transfiletriggername
-rw-r--r-- 1 root root      8192 Dec 30 22:04 Triggername
rmp@W9020:~> ls -l /var/cache/zypp/solv/@System/
total 4412
-rw-r--r-- 1 root root      52 Jan  3 17:51 cookie
-rw-r--r-- 1 root root 4395701 Jan  3 17:51 solv
-rw-r--r-- 1 root root  111236 Jan  3 17:51 solv.idx
rmp@W9020:~>

The zypper metadata change timestamp looks recent enough. Do you still see the wrong installed version?

zypper se -six glibc

It indeed has a name: Permanently Disable KDE Plasma's Update Manager? - #14 by karlmistelberger

1 Like

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.

3 Likes

As requested:

zypper se -six glibc

Loading repository data...
Reading installed packages...

S  | Name  | Type    | Version          | Arch   | Repository
---+-------+---------+------------------+--------+-------------------------------------------------------------
i+ | glibc | package | 2.31-150300.63.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15

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.

Good. So apparently the problem solved itself.

So, can anyone explain what might have caused the problem, and what might have fixed it?

Thank you all for your input.

1. The applet does cause trouble.

Encountered numerous issues. Issues documented (a small fraction of encountered issues):

https://forums.opensuse.org/search?q=software%20update%20%40karlmistelberger%20order%3Alatest

Removing the applet keeps the trouble away.

2. PackageKit does cause trouble.

Encountered numerous issues. Issues documented (a small fraction of encountered issues):

https://forums.opensuse.org/search?q=packagekit%20%40karlmistelberger%20order%3Alatest

Removing PackageKit keeps the trouble away.

3. No trouble encountered with zypper dist-upgrade (on Tumbleweed) and zypper update (on Leap).

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.

Let’s focus on the OP’s issue.

1 Like

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:

  1. Installing or removing software | Start-Up | openSUSE Leap 15.5

  2. Managing software with command line tools | Reference | openSUSE Leap 15.5

Graphical tools are nice. The catch is the complexity hidden from the user. Issues as the above one are hard to assess due to poor user awareness.

I am sorry that my question turned into an argument!

I’m still none the wiser as to what caused this, but thankfully it has now resolved.

Thanks to everyone for their input.

No worries - the heated debate is not on you - you should not feel that you should not have asked the question.

Very glad that the issue is resolved now for you. :smiley:

1 Like