Kitty stopped working after the update.
segmentation fault (core dumped) kitty
Fortunately, it was resolved by reverting to the previous version of the mesa package (1:25.2.3-2).
And works again !!! 
Moderator edit: Removed unnecessary screenshots of text
… until you get in trouble again as your are running an unsupported only partially upgraded system 
Updated from testing branch 2025-11-27, with NVIDIA + KDE + Wayland
Everything is fine except one minor issue : the window would flash a little when close it.
This was mentioned earlier; apparently disabling and re-enabling the window effect should fix it.
Hey there!
Before I do my update I have a pair of questions regarding the mkinitcpio v40
My current hooks in my mkinitcpio.conf file are as follows
HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth filesystems fsck)
With the apparent change to systemd from Arch (I assume I’m going to be getting a pacnew yelling at me to change to that), am I able to do my update, reboot and then change my hooks to the systemd specific hooks from the pacnew (looking at the wiki to fully make sure of course), regenerating the .conf file and be all good? Or are there additional steps/packages that need to be done to have systemd boot?
Also in the opening post
Does this specifically need to be done? From what I can gather, this only removes a functionality so can this just be safely ignored if you want to keep (or don’t know if you want to keep) the ‘fallback’ functionality?
Thank you!
Is ip_tables intentionally left out of the 617_rt kernel? The update broke my docker service which relies on it. Apart from that, everything went smoothly. 
apparently disabling and re-enabling the window effect
I searched through earlier posts, but didn’t find how to do it.
I reset all the settings in System Settings - Desktop Effects with no luck.
Hi @schlabonski and welcome to the Manjaro Community!
Is there a particular reason you are using a rt Kernel? … These are not generally recommended outside of specific use cases, e.g. audio production. 
@siberianhusky I’ll have to have a 
and see if I can find the post; it might have been moved to its own thread. 
I’m used to it; my computer is already quite old. Over time, I’ve fixed several situations like this. If it stops working, then I’ll look for another terminal that does.
Here it is: Graphic artifacts after 2025-12-08 Stable Update - #4 by pwx
CC: @BG405
Hi
On KDE desktop, I have two issues :
~/.var … with flatpak runFor the wine app, downgrading wine, wine-mono or using wine-staging did not change anything. Feels like related to wayland thingies. Moreover, compiling from the aur wine32 or wine-stabletaking ages… I had to work today, no time to wait for it lol.
I created a testing account and have the same problem with the browsers not loading. I do have a notice on boot of “/var/lib/.config/sddm-greeter-qt6rc” not writeable which is dismissed by clicking OK.
Did you recompile the AUR package? I assume when you installed it, you had 48 GNOME still installed on your end …
Reporting successful update and no obvious problems (yet 
) on three systems,
thank you
Mode edit:- Details of those three systems not required. Removed.
You will need to rebuild your initramfs and update your boot loader. 
sudo mkinitcpio -P && sudo update-grub
That’s for the people who want to disable the creation of a fallback initramfs. By default, the fallback image will be created whenever the kernel is updated or a new kernel is installed.
[peter@TP460s ~]$ cat /etc/default/grub | grep CMDLINE
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=795fd5b5-a513-4e0f-bb22-5afffcc9f24d"
GRUB_CMDLINE_LINUX=""
[peter@TP460s ~]$ sudo blkid | grep swap
[sudo] Passwort für peter:
/dev/sda2: UUID="795fd5b5-a513-4e0f-bb22-5afffcc9f24d" TYPE="swap" PARTUUID="6b8ff837-02"
looks good to me
same here: ?
/etc/mkinitcpio.conf:
HOOKS=(base udev autodetect modconf kms block keyboard keymap resume filesystems fsck)
/etc/mkinitcpio.conf.pacnew:
HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystems fsck)
10 posts were split to a new topic: Encrypted system is not booting after stable update
@Jangadance and…you will get a pacnew disabling the preset otherwise.
It is not obligatory, but the fallback does not really serve a purpose (it is just an initramfs without the “autodetect” thus adding a 100mb more of all possible firmware and drivers…if ever needed one can just boot from usb, chroot and remove “autodetect” and regenerate - it will be the same)
My nvidia computer did not like the update.
If all 3 DP cables are connected the screen stays black, with two it works.
Edit:
Seems to be a bandwidth issue.
My OLED flickers when set to 240 Hz
Two laptops using Xfce edition on stable branch updated smoothly without any issue 
