One of the following pacakges is stopping reaching Graphical Target

General system Kernel, boot, graphics & hardware
1

I am running EOS+SDDM+Wayland+KDE 6. Of course, I have a timeshift with auto-snap enabled for before/after and upgrade.

Today, after the latest upgrade, one of the followings packages is killing the boot sequence from reaching the graphical target (SDDM).
Which one of the following packages is breaking my system?
Should I switch the mesa-tkg-git to the stable version?

:: Synchronizing package databases...
 endeavouros downloading...
 core downloading...
 extra downloading...
 multilib downloading...
 chaotic-aur downloading...
:: e[1mSearching AUR for updates...e[0m
:: e[1mSearching databases for updates...e[0m
 -> gimp-git: local (3.0.0.RC1.r2.g15f5b15-1) is newer than chaotic-aur (3.0.0RC2.r116.gd8a8d2f-1)
 -> google-earth-pro: local (7.3.6.10155-1.5) is newer than chaotic-aur (7.3.6.10155-1)
 -> mesa-tkg-git: ignoring package upgrade (25.0.0_devel.198512.fcaf0f25900-1 => 25.0.0_devel.199599.272ff275fa2-1)
 -> shortwave: local (1:3.2.0-1.3) is newer than extra (4.0.1-1)
 -> Orphan (unmaintained) AUR Packages: lib32-libdvdcss
 -> Flagged Out Of Date AUR Packages: directx-headers-git  lib32-openjpeg2  lib32-srt  pakbak-git  pkgtools  sddm-conf-git
 -> kfilemetadata5: local (5.116.0-2) is newer than AUR (5.116.0-1)

:: 26 packages to upgrade/install.
26  extra/clang                   18.1.8-5               -> 19.1.6-1
25  extra/compiler-rt             18.1.8-1               -> 19.1.6-1
24  extra/doxygen                 1.13.1-1               -> 1.13.2-1
23  extra/inxi                    3.3.36.1-1             -> 3.3.37.1-1
22  extra/kdevelop                24.12.1-1              -> 24.12.1-2
21  extra/lib32-rust-libs         1:1.83.0-2             -> 1:1.84.0-1
20  extra/liblphobos              3:1.40.0-1             -> 3:1.40.0-2
19  extra/lld                     18.1.8-1               -> 19.1.6-1
18  extra/llvm                    18.1.8-5               -> 19.1.6-3
17  extra/llvm-libs               18.1.8-5               -> 19.1.6-3
16  extra/openmp                  18.1.8-1               -> 19.1.6-2
15  extra/polly                   18.1.8-1               -> 19.1.6-1
14  extra/postgresql-libs         16.6-1                 -> 17.2-1
13  extra/pv                      1.9.25-1               -> 1.9.27-1
12  extra/pyside6                 6.8.1.1-2              -> 6.8.1.1-3
11  extra/qt5-tools               5.15.16+kde+r3-3       -> 5.15.16+kde+r3-4
10  extra/qt6-tools               6.8.1-1                -> 6.8.1-2
 9  extra/rust                    1:1.83.0-2             -> 1:1.84.0-1
 8  extra/shiboken6               6.8.1.1-2              -> 6.8.1.1-3
 7  extra/spirv-llvm-translator   18.1.8-1               -> 19.1.3-1
 6  multilib/lib32-clang          18.1.8-1               -> 19.1.6-1
 5  multilib/lib32-llvm-libs      1:18.1.8-1             -> 1:19.1.6-1
 4  multilib/lib32-mesa           1:24.3.3-1             -> 1:24.3.3-2
 3  multilib/lib32-vulkan-radeon  1:24.3.3-1             -> 1:24.3.3-2
 2  chaotic-aur/dxvk-mingw-git    2.5.2.r42.g7f4e25267-1 -> 2.5.2.r44.gd5832c307-1
 1  aur/gpu-viewer                3.10-1                 -> 3.10-2
2

Personal I would look if normal mesa work. I don’t know when that package is installed also.

3

First, I will switch mesa to the official stable and try again.

4

The normal lib32-mesa was there so you also got mismatch of versions on a sense

1 Like
5

I switched mesa to the version to the stable version from extra repo.
Rebooted and the system hangs before going to SDDM. I went v-term 3 and did a full update and rebooted and Voilà, the system is back online as before.
It is a mismatch version between mesa dev 25 and stable mesa 24.3.x,x

Thanks for all. I will mark this as resolved.

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.