The damage is in this case reversable, don’t worry. Just a bit of manual work. From live usb, cryptsetup to unlock, then mount the btrfs volumes, then chroot, then edit back the files and after that apply the changes (for fstab you need nothing special, for grub to regenerate with update-grub, for mkinitcpio.conf you need mkinitcpio -P).
Those are the steps, if you are stuck on some step just say.
2 Likes
Thank you @Teo, I’ve just edited my previous post, I got it working with a bit of messing around. I hadn’t done a chroot in ages and never on BTRFS so it took a bit of digging.
Thank you all guys for the great distro.
1 Like
Hi! Thank you for the thread. When using Linux 6.1, the Mesa update
mesa 1:26.0.6-1 -> 1:26.1.1-2
is causing my Plasma session to lose all the animation effects and become clunky, eventually unreliable as the session goes on.
Those are the logs from journalctl:
kwin_wayland_wrapper[1620]: amdgpu: DRM version is 3.49.0, but this driver is only compatible with 3.54.0 (kernel 6.6+) or later.
kwin_wayland_wrapper[1620]: MESA: error: amdgpu: ac_query_gpu_info failed.
I’ve updated the kernel to 6.18 and everything is working fine now, I just don’t understand why the kernel update did not happen automatically.
6.1 and 6.18 are both LTS kernels, so there is no need to upgrade 6.1 yet, because it’s still supported.
That said, it would indeed still be wiser to switch to 6.18 due to some changes in other parts of the system — e.g. systemd — which include features 6.1 did not have yet.
Thank you! In that case I just wanted to point out the incompatibility issue between Linux 6.1 and the new Mesa driver update.
1 Like
You don’t eventually have a built in intel graphic card from before 2011?
Yes, that would be one of those evolutionary changes warranting the move to 6.18. 
3 Likes
2 posts were split to a new topic: Should Manjaro maintain support for kernel 6.1?
You don’t eventually have a built in intel graphic card from before 2011?
No, no Intel, I’ve got a built in AMD and a NVIDIA graphic card:
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1)
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon Vega Series / Radeon Vega Mobile Series] (rev c6)
Hey sorry to say i have problems again, this time with the Computer running the Projector in the living room, i started noticing these wierd tears in text while using the Vivaldi browser.
didnt think much of it as we mostly used it for streaming and youtube, as the movies played fine with subtitles it was not a big deal. but started twitch and chat looked like this. It never became readable. i though it was a browser issue as firefox works fine, but i am also now seeing the issue in steam. but all other manjaro UI is perfectly fine. it is just Steam and Vivaldi that has trouple with displaying text.
the computer is a Old HP office pc with a integrated 2gen gpu and runs wayland now if that helps.
if any one has some advice i would greatly appreciated as i am a little stumped with this one.
It appears to be a problem with mesa on older Intel processors. 
1 Like
As Aragorn is pointing out, it seems to be a problem with he mesa package. The updated version of the package that fixes this issue is in unstable branch now. You can give it a try:
sudo pacman -U https://mirrors2.manjaro.org/unstable/extra/x86_64/mesa-1:26.1.2-1-x86_64.pkg.tar.zst
I think it should resolve your problem. If, for some reason, it gives you any other problem, you can go back with:
sudo pacman -Suu
I don’t have the problem, but I have installed the new package just to try it, and at least I don’t notice any side effects.
@frossett130: Even if your problem seems to be different, you can also try the new package to see if it solves anything.
4 Likes
A post was split to a new topic: [404] not found error for package changes in stable update 2026-05-27
I was too brave and tried again pamac on the command line. It crashed after 3 minutes while downloading. Nevertheless, the update (not only this, but the last three ones) continued in the background. The final entry in pacman.log was “running ‘xorg-mkfontscale.hook’”, the same final entry as at my last crashing pamac update in February.
No issues after rebooting. Anyhow, next time I will use pacman instead.
2 Likes
It’s what I always recommend, followed by an AUR helper if needed. 
. . .
7 Likes