Well, there is always a chance that it could cause harm.
As well as the packagers try doing their jobs, they may always overlook something, and sometimes it is only necessary to downgrade one or possibly two packages for certain users with certain hardware or certain configurations, while other users are not affected by the same problem.
In such a case, all users would be downgrading the pertinent package(s), whereas this may not be necessary or even desirable. Some people also add custom repositories to their /etc/pacman.conf — which is not officially supported as it may lead to breakage — and in those cases, extra caution is required.
It is therefore safer to not use -Syuu unless it’s absolutely necessary. pacman will tell you when it might be indicated to downgrade a particular package, and then running an extra pacman command with -Syuu — if necessary — won’t be such a problem.
A zero-dot version is used for rebuilds lower than package revision 1. When @Yochanan pushed firefox to stable branch the toolchain, especially gcc was older as the build of firefox. Hence some users had issues. Due to the demanding RAM usage to compile firefox, Mark had to buy first more RAM for his build machine. That done he is now able to compile firefox or chromium as needed. A web browser is kinda an OS of its own by now.
Yes, this downgrade definitely messed up my Firefox book marks menu toolbar. Luckily I was able to copy my .mozzila config file from my other computer, and restore it!
I had an issue updating with yay as it stopped mid-way (hangup after tunning build hook) and I rebooted leading to a kernel panick as initramfs was broken, had to chroot and reinstall the kernel. No biggie but just wondering if anyone else got any similar issues.
I do not understand however why this update uses a “let it break and then tell people how to fix” approach.
In addition, manjaro-kde-25.0.7-minimal-250812-linux612.iso gave me failed to start user login management and didn’t start so I had to use an older iso I thankfully had lying around.
I also stumbled about a black screen with Error: grub_is_using_legacy_shim_lock_protocol not found
even though install-grub was installed.
Since my system runs with btrfs, where manjaro-chroot seem to not work, I followed the instructions above and manually copied /EFI/Manjaro/grubx64.efi to /EFI/boot/ as bootx64.efi.
Booting from a Live-System I did:
sudo -i
mount /dev/nvme1n1p1 /mnt
cd /mnt/EFI
cp Manjaro/grubx64.efi boot/
cd boot
mv grubx64.efi bootx64.efi