Arch Linux

betaminos

Member

Registered: 2024-01-04

Posts: 5

[SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

Hello there,

and sorry if this is not the place where to post this - it's the most suitable place I could find.
I have done a round of updates and was greeted by my normal console login instead of my KDE Plasma desktop.
Upon digging, I found that the updates seem to have changed a shared library - running journalctl | grep kwin_wayland_wrapper gives:

Jan 12 20:22:23 oxp kwin_wayland_wrapper[38026]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:23 oxp kwin_wayland_wrapper[38054]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:23 oxp kwin_wayland_wrapper[38063]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:23 oxp kwin_wayland_wrapper[38067]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:23 oxp kwin_wayland_wrapper[38071]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:23 oxp kwin_wayland_wrapper[38075]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:23 oxp kwin_wayland_wrapper[38079]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:23 oxp kwin_wayland_wrapper[38083]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:24 oxp kwin_wayland_wrapper[38087]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:24 oxp kwin_wayland_wrapper[38091]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jan 12 20:22:24 oxp kwin_wayland_wrapper[38095]: MESA-LOADER: failed to open dri: libLLVM.so.18.1: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)

I managed to fix it on my device by installing the most recent version of these packages in my cache (effectively downgrading them):
- lib32-llvm-libs
- llvm-libs
- llvm
- lld
The command I have used is for example: sudo pacman -U /var/cache/pacman/pkg/lib32-llvm-libs-18.1.8-1-x86_64.pkg.tar.zst

This has fixed the issue on my device and I hope this helps users facing a similar issue after the latest round of updates.
It seems to me that kwin expects this version of 18.1 whereas the update had pushed the version to 19.1.6.
For reference, yay is now showing (with the newer version having caused the issues on my device):

:: 4 packages to upgrade/install.
4  extra/lld                 18.1.8-1.1 -> 19.1.6-1
3  extra/llvm                18.1.8-10  -> 19.1.6-3
2  extra/llvm-libs           18.1.8-10  -> 19.1.6-3
1  multilib/lib32-llvm-libs  18.1.8-1   -> 1:19.1.6-1

Last edited by betaminos (2025-01-13 17:41:29)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,323

Re: [SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

This is not the correct fix, and will break a lot of other things. It's almost certainly caused by a partial update, either holding some updates back or having previously replaced repo packages with foreign ones.

betaminos

Member

Registered: 2024-01-04

Posts: 5

Re: [SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

This is not the correct fix, and will break a lot of other things. It's almost certainly caused by a partial update, either holding some updates back or having previously replaced repo packages with foreign ones.

I agree that this should not be the fix, and that the underlying source of the issue seems to be a partial update.
However, I have done several rounds of pacman -Syyuu over about an hour and have not been able to get any further updates.

seth

Member

Registered: 2012-09-03

Posts: 60,805

Re: [SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

pacman -Qikk kwin kwindowsystem
pacman -Qm
pacman-conf

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,323

Re: [SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

Add pacman -Qi mesa into that, that's the most likely issue

betaminos

Member

Registered: 2024-01-04

Posts: 5

Re: [SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

Add pacman -Qi mesa into that, that's the most likely issue

You are correct and I have just noticed what you meant by "foreign packages".
I am using mesa-git and today's round of updates did bring up a new version, which has solved my issue.

Thank you for your help.

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,577

Website

Re: [SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

Mod note: moving to AUR Issues

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,323

Re: [SOLVED] No GUI (KDE Plasma) after updates due to change in libLLVM.so

I am using mesa-git and today's round of updates did bring up a new version, which has solved my issue.

That was pure luck. When things are updated in the repos, it's *your* responsibility to rebuild any foreign packages that may need it. https://wiki.archlinux.org/title/Arch_U … g_packages
You can't count on the maintainer updating the PKGBUILD, or upstream commits, or anything else. YOU have to pay attention to what's happening in the repos and take appropriate action. If you are unwilling to take that responsibility, do not replace repo packages with AUR ones.