I’m running cinnamon and just applied. Besides a couple of conflicts with AUR packages (which I just removed), so far so good.
1 Like
The manual install-grub / update-grub was necessary on my systems as well. Forgetting it landed me at the aforementioned symbol ‘grub_memcpy’ not found and required a live-ISO recovery.
Made an Update at my Notebook.
Seem all to be okay, of them I just starten and opend Programs.
Betriebssystem: Manjaro Linux
KDE-Plasma-Version: 6.5.3
KDE-Frameworks-Version: 6.20.0
Qt-Version: 6.10.1
Kernel-Version: 6.17.11-1-MANJARO (64-bit)
Grafik-Plattform: Wayland
Prozessoren: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Speicher: 16 GiB of RAM (15,4 GiB usable)
Grafikprozessor 1: Intel® UHD Graphics 630
Grafikprozessor 2: NVIDIA GeForce GTX 1650
Hersteller: MEDION
Produktname: P15609
Systemversion: N/A
After reboot one new other Update came up
Erstelle steam-native-runtime…
==> Erstelle Paket: steam-native-runtime 1.0.0.75-8 (Di 09 Dez 2025 00:57:54 CET)
==> Prüfe Laufzeit-Abhängigkeiten…
==> Fehlende Abhängigkeiten:
→ lib32-openssl-1.0
→ openssl-1.0
→ sdl2_net
==
Prüfe Buildtime-Abhängigkeiten…`
==> FEHLER: Konnte nicht alle Abhängigkeiten auflösen.
Seems lib32-openssl and openssl are 1.1 already installed
Seem sdl2_net is not installed
Edit : installed Kernel-Version: 6.18.0-1-MANJARO (64-bit)
Installed
Vorbereitung...
Synchronisiere Paketdatenbanken...
Aktualisierung von AUR...
Es gibt nichts zu tun.
Klone steam-native-runtime Build-Dateien...
Generiere Informationen zu steam-native-runtime ...
Überprüfe steam-native-runtime Abhängigkeiten...
Überprüfe lib32-openssl-1.0 Abhängigkeiten...
Überprüfe openssl-1.0 Abhängigkeiten...
Abhängigkeiten werden aufgelöst...
Interne Konflikte werden überprüft...
Klone openssl-1.0 Build-Dateien...
Generiere Informationen zu openssl-1.0 ...
gpg: Schlüssel D9C4D26D0E604491: Öffentlicher Schlüssel "Matt Caswell <matt@openssl.org>" importiert
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg: importiert: 1
gpg: Schlüssel D5E9E43F7DF9EE8C: 1 doppelte Signatur entfernt
gpg: Schlüssel D5E9E43F7DF9EE8C: Öffentlicher Schlüssel "Richard Levitte <richard@levitte.org>" importiert
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg: importiert: 1
Klone lib32-openssl-1.0 Build-Dateien...
Generiere Informationen zu lib32-openssl-1.0 ...
Herunterladen von sdl2_net (1:2.2.0-2) gestartet
Herunterladen von sdl2_net (1:2.2.0-2) beendet
Überprüfe Schlüsselring...
Integrität wird überprüft...
Paketdateien werden geladen...
Dateikonflikte werden überprüft...
Überprüfe verfügbaren Speicherplatz...
Installiere sdl2_net (1:2.2.0-2)...
without an error.
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
A post was merged into an existing topic: Discussion about the 2025-12-08 Stable Update
The keymap hook and the consolefont hook are not needed when you have sd-vconsole. keyboard is however still needed.
1 Like
Using Xfce, I also encountered the “F12 snag” with Guake Terminal. No big deal, just switched to another keyboard shortcut and it’s working fine. 
However, anyone who is using Zoom, look out.
Zoom (AUR) has qt5-webengine and qt5-remoteobjects as optional dependencies, which Yay will find as updates in the AUR and compile them from source.
Compile time is quite long, so if you are using Zoom from the AUR, grab yourself a good cup of coffee and watch your CPU do a workout. 
I just saw that zoom seems to be available as flatpak, so I might give it a try…
Update: I cancelled the compile, removed the Zoom AUR package and installed the Zoom flatpak.
Seems to work fine 
so I would definitely recommend the flatpak over the AUR package.
Keyboard is still needed for early keyboard support, keymap and consolefont are read from /etc/vconsole.conf when using sd-vconsole.
1 Like
Hmm, this doesn’t sound right. My guess is that your update process does not include steps for identifying orphans and/or foreign packages.
What can happen is that when Manjaro removes packages (like slowly phasing out kde5 / qt5) and you have AUR enabled… AUR becomes the source and that leads to the recompile you are talking about.
My preference is to use pacman (via terminal / tty), but you can also check via pamac (gui or cli) for orphans/foreign.
So right after I do a “system only” update via sudo pacman -Syu… I’ll check for orphans pacman -Qdt and foreign packages pacman -Qm…
any orphan I don’t recognise (manually use) I remove, which if it’s all is one command sudo pacman -Rns $(sudo pacman -Qdtq)
any foreign (AUR) package I know I did not manually install also gets removed… usually just type out the package names via sudo pacman -Rns package1 package2 etc
Only then do I update my AUR packages… pamac update -a
I imagine that if you follow an update process like this, you would not get surprised by other unintended packages being installed/updated from the AUR.
Did you have install-grub and update-grub installed prior to this update… and the hooks failed to run? If so, how did you apply the update? pacman?
Or they were not installed, you needed to install them, and because the update happened already (passed the hooks stage) you had to run them manually?
2 Likes
I have been fine so far. Rebuilt needed AUR packages as well
1 Like
In that case you should move it closer to the front of the array. The Arch Wiki suggests putting it before autodetect.
My Partner’s Starlite, my Dell Media Computer, and our SBK Manjaro Server. All updated without issue.
My Partner updated her device via pamac-manager, I updated the server and the media machine remotely over ssh with pacman, and later went the computer and ran pamac-manager to update flatpaks and AUR application (Mullvad), and updated the RT kernel to 6.17.x.
Everything seems to be running smoothly.
A really great update, from our point of view. Thanks.
5 Likes
Well worth the wait.
The only issue encountered was not related to Manjaro.
I use rEFInd Boot Manager in a multi-boot scenario – because the rEFInd package was also updated it was necessary to re-apply rEFInd to the $ESP:
Once the 2025-12-08 was completed I simply issued:
sudo refind-install
(followed by a reboot).
Thanks to @philm, @Yochanan and other unsung heroes behind the scenes for again delivering the goods amid pressure from many directions. 
5 Likes
You installed the last Zeta ISO and not the new Anh-Linh ISO which is found in the first post versioned 25.1-pre1. Get those and try again.
Or try to solve it by running install-grub followed by update-grub after the system update before rebooting your system.
Have you also seen this from Known Issues and Solutions in this very same topic?:
If you wish to continue using X11 you must install plasma-x11-session and reboot, to again be able to select the X11 session from SDDM.
Regards.
2 Likes
The update worked perfectly on multiple systems. Thank you for the long-awaited stable update.
3 Likes
yay has specific command variations to avoid these kinds of problems, if only people would use them. Using yay without any parameters, for example, installs both Manjaro Repo and packages sourced via the AUR as a chunky soup of software.
The responsible way to use yay is:
1. Update packages from the Manjaro repo(s):
yay -SyuN– or –yay -Syu --repo
2. Build/update software sourced via the AUR:
yay -Sua– or –yay -Su --aur
The important factor is to maintain separation between updating from Manjaro Repos and other foreign sources such as the AUR.
6 Likes
yes, I got stuck at boot with the error about memcpy and I had to fix it using install-grub and update-grub. however I didn’t need any external media to boot the computer to apply the fix. I used my notebook’s boot menu option with the F12 key and there was an option ‘Manjaro’. I booted it, applied the fix and done.
also, while upgrading, there were some dependency issues with aur’s ffmpeg-libfdk_aac v7 → v8. my solution was to remove ffmpeg-libfdk_aac and all of its dependants, update manjaro, and clean rebuild ffmpeg-libfdk_aac and install the removed dependants.
Haaaalp, it not wurkz! 
Just kidding — 995 packages, worth over 13 GiB of disk space after unpacking, but it went buttery smooth. 
Good work, @philm, @yochanan, @linux-aarhus, @oberon, et al.
7 Likes
I am having an issue with my login. As mentioned, X11 has been removed, which is a-okay, but I was also utilizing Gamescope (and associated packages) to log in, and it seems that that login method (Steam Big Picture Wayland) is no longer functional. It will take my login information, screen goes black, but rather than putting me into desktop I go right back to login screen. Ideas?
Mine was over 1000 packages and over 19GiB unpacked
But otherwise everything as “boring” as always. Not a single “little problem” I have to fix 
Thanks to the devs for the good work.
4 Likes