KDE is now broken. A few seconds after login the plasma wayland session crashes, killing all apps. Plasma restarts in a diminished mode, showing a Plasma Renderer icon in the system tray. Clicking on it a window opens with non-antialiased text asking which renderer to use for qtquick. From that moment on the wayland session keeps crashing periodically.
in dmesg:
mdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 243.010903] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 243.010904] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 243.010905] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 243.010906] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 243.010907] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 243.010908] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 243.010910] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 243.010911] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 243.010912] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ 243.010913] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[ 243.010914] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[ 243.010915] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[ 243.010916] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[ 243.010918] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[ 243.010919] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
[ 243.013735] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
[ 338.015858] pcieport 0000:00:02.4: AER: Corrected error received: 0000:06:00.0
[ 338.015887] nvme 0000:06:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 338.015893] nvme 0000:06:00.0: device [15b7:5025] error status/mask=00000001/0000e000
[ 338.015900] nvme 0000:06:00.0: [ 0] RxErr (First)
[ 340.014837] pcieport 0000:00:02.4: AER: Corrected error received: 0000:06:00.0
[ 340.014942] nvme 0000:06:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 340.014948] nvme 0000:06:00.0: device [15b7:5025] error status/mask=00000001/0000e000
[ 340.014954] nvme 0000:06:00.0: [ 0] RxErr (First)
[ 340.014966] pcieport 0000:00:02.4: AER: Corrected error received: 0000:06:00.0
[ 355.514989] pcieport 0000:00:02.4: AER: Corrected error received: 0000:06:00.0
[ 355.515088] nvme 0000:06:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 355.515094] nvme 0000:06:00.0: device [15b7:5025] error status/mask=00000001/0000e000
[ 355.515101] nvme 0000:06:00.0: [ 0] RxErr (First)
[ 355.515117] pcieport 0000:00:02.4: AER: Corrected error received: 0000:06:00.0
[ 362.515845] pcieport 0000:00:02.4: AER: Corrected error received: 0000:06:00.0
[ 362.515866] nvme 0000:06:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 362.515872] nvme 0000:06:00.0: device [15b7:5025] error status/mask=00000001/0000e000
[ 362.515878] nvme 0000:06:00.0: [ 0] RxErr (First)
Addendum… most likely the issue was the packages in the nonfree.eu repo that I had enabled to get hardware video encoding.
similar to mine. but the update-process crashed while updating. after downloading the installation started as usual but within it suddenly crashed the whole wayland-session. never had such a behaviour in any linux-updating.
After this update, keepass is not working, gives me Aborted (core dumped). I guess due to some update in mono.
UPD: Uninstalling and reinstalling the keepass package helped. Maybe it’s the same problem as in Arch " FS#78263 - [keepass] updating mono breaks keepass until its install file commands are run".
I voted “no issue” as in the end nothing was broken and everything’s great after a restart. But I can confirm what others mentioned above: If you’re on the KDE Plasma Wayland session, your desktop will crash in the middle of the update closing all applications on you. As a precaution I reinstalled Grub and the Kernel just in case pacman also crashed before reconfiguring those, if you want to be on the extra safe side you can do that using this command for your kernel version:
The update notifier shows you how many updates there are when it polls the mirror. It is not unusual for there to be (many) more updates once you start the update process if you do this before the update notifier’s next polling of the mirror.
Confirmed.
The only safe way to apply major updates like this is to completely log out of the GUI, switch to a tty, log in there, and update the system from the command line, like so…
sudo pacman -Syu && pamac update
This way…
only a bare minimum of shared libraries will be in use that are going to be overwritten by the update process; and…
you will be updating all your official repo packages first before everything else from the AUR, Snap, FlatPak and whatever else there is.
Also…
Always merge your .pacnew files.
If you want stability, don’t use Wayland as the display server for Plasma. Seriously, don’t, unless you’re willing to deal with breakage. Wayland is a work in progress and is still not production-ready when used with Plasma — it even still has issues underneath GNOME.
This update broken my cinnamon installation. Window manager (muffin) refuses to launch, says clutter doesn’t have any backends available.
edit:
it’s a problem with llvm-libs. Downgraded it to previous version (15.x) and cinnamon is working again (amdgpu). I’m using mesa nonfree repo, so it may be caused by olded mesa version (still 23.1.5 there).
My GNOME Wayland session would not start anymore because of the nonfree.eu mesa package that I had to uninstall and by reverting mesa to extra via sudo pacman -Syuu in order to make my system usable again.
No, definitely not the minority. Quite the opposite: it’s what almost everyone does. But if you’re updating the system from within the GUI, then a whole busload of shared libraries will be in use that are going to be overwritten, and this could cause serious problems.
Secondly, pamac is a work in progress, and it has serious issues — especially the GUI versions, although even the command-line version has its problems.
pacman on the other hand is the mature command-line-only package manager for Arch-based distributions, and you can use yay — which is equally mature — for installing AUR packages. But of course, yay does not handle Snaps or FlatPaks, so you may need to resort to (the command-line version of) pamac for those.
I’m using KDE Plasma, running on X11 and have tearing after the update. There is also a Plasma-Render warning. I have tried both, software renderer and OpenGL, but for both there is tearing when scrolling in firefox or watching videos.
Furthermore I cannot adjust under system settings/compositor the sync option. It has disappeared?
