Multiples of the same add-on installed

Rocky Linux Tech Help
1

Not sure if something is off with my installation, but I have multiples of the same add-on installed in the Software app as same versions and/or as different versions.

Please take a look at what I have in my “Installed” → “Add-ons” in the Software app (I’ve added the versions into an image):

Screenshot-20240602200758-599x1158
Screenshot-20240602200758-599x1158599×1160 73.6 KB

If I query rpm for “mesa”, for example, here’s the output I get:

$ rpm -qa mesa\*
mesa-libGLU-9.0.1-6.el9.x86_64
mesa-libgbm-23.3.3-1.el9.x86_64
mesa-libglapi-23.3.3-1.el9.x86_64
mesa-filesystem-23.3.3-1.el9.x86_64
mesa-dri-drivers-23.3.3-1.el9.x86_64
mesa-vulkan-drivers-23.3.3-1.el9.x86_64
mesa-filesystem-23.3.3-1.el9.i686
mesa-libGL-23.3.3-1.el9.x86_64
mesa-libEGL-23.3.3-1.el9.x86_64
mesa-libxatracker-23.3.3-1.el9.x86_64
mesa-libglapi-23.3.3-1.el9.i686
mesa-vulkan-drivers-23.3.3-1.el9.i686
mesa-libgbm-23.3.3-1.el9.i686
mesa-libEGL-23.3.3-1.el9.i686
mesa-dri-drivers-23.3.3-1.el9.i686

The versions are off from what the Software app shows (maybe different versioning used?), but even if were just that the versions were off, the results show two results of each (“.x86_64” and “.i686”), while I have three records of “Mesa” add-on installed.

I have one “openh264” installed:

$ rpm -qa openh\*
openh264-2.3.1-1.el9.x86_64

Is this something I should be worried about? I do get mce hardware errors occurring randomly:

19:16:17 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1715188575 SOCKET 0 APIC c microcode a20102b
19:16:17 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1715188575 SOCKET 0 APIC c microcode a20102b
19:16:17 kernel: mce: [Hardware Error]: TSC 0 ADDR 393a69100 MISC d012000000000000 IPID 100b000000000 
19:16:17 kernel: mce: [Hardware Error]: CPU 6: Machine Check: 0 Bank 1: bc800800060c0859

14:49:20 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1716641358 SOCKET 0 APIC b microcode a20102b
14:49:20 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1716641358 SOCKET 0 APIC b microcode a20102b
14:49:20 kernel: mce: [Hardware Error]: TSC 0 ADDR 359d82700 MISC d012000000000000 IPID 100b000000000 
14:49:20 kernel: mce: [Hardware Error]: CPU 13: Machine Check: 0 Bank 1: bc800800060c0859
14:49:20 kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1716641358 SOCKET 0 APIC a microcode a20102b
14:49:20 kernel: mce: [Hardware Error]: TSC 0 ADDR 359d82700 MISC d012000000000000 IPID 100b000000000 
14:49:20 kernel: mce: [Hardware Error]: CPU 5: Machine Check: 0 Bank 1: bc800800060c0859

All hardware tests (memtest, CPU test, GPU test, SSD test) run clear for multiple runs and several hours without any issues…

2

How exactly did you obtain and install those add-ons, I don’t see them on default Rocky 9.4 with GUI. I see mesa versions match ‘23.3.3-1.el9’.

I’m not convinced the hardware errors are related.

3

I don’t know where do these come from. I have Nvidia GPU installed with proprietary drivers.

Should I cleanup all the duplicates and clean install my drivers again?

But not all multiples of the same are GPU driver related. For example, I also have:
4× “Adwaita theme”
4× “QGnomePlatform”
3× “QGnomePlatform-decoration”
2× “Freedesktop Platform”
2× “GNOME Application Platform” (v 45 and v 46)
2× “English”

4

First, I don’t use GUI package managers, so can’t say anything about their quirks.

This is not “duplication”.

Most executables do depend on “shared objects” – dynamically linked libraries. The kernel of OS is built to use 64-bit instructions of the CPU, and so are (most) libraries and executables. These packages have the x86_64 arch.

However, there might still exist 32-bit executables that do depend on 32-bit libraries. The 32-bit libraries are not the “original” that were used in 32-bit hardware, but something that can interact with the current hardware and the 64-bit kernel. These packages have the i686 arch. All (library) packages do not have corresponding i686 package.

The default is to install no i686 packages. A dnf install mesa-libEGL would install only the x86_64 version. However, if one installs something that requires any i686 libraries, then those do get installed. After that dnf up mesa-libEGL naturally updates both mesa-libEGL.x86_64 and mesa-libEGL.i686.

5

Arch is clear to me, and I assumed two of those might have been from different arch versions, but there are three of them.

6

As I wrote, I have no clue on that. I’m also baffled that “versions” shown by GUI do not seem to match anything on the packages. (I have never seen a use for those GUI tools and your sample for sure does not change that.)