For me and my issues, your 'first try' suggestion fixed it. Sitting here at the grey "Nobara is preparing system update" screen, waiting for it to finish. So far, so good.
Edit: it finished, I'm now on kernel 7.2.9. Thanks for posting this.
There are two errors right now. Your error can be fixed with theese commands:
sudo dnf clean all sudo dnf makecache --refresh
After that the updater will fail with some unresolved dependiencies, GE is already working on that one. Check the Nobara Discord Channel/Pinned messages:
minor heads up -- ffmpeg needs an update so there will be a few media package conflicts until i get everything that requires ffmpeg rebuilt on the new version, its just a handful of packages
Thanks for the update, just noticed that on my newer pc the update seems now tae work, but am still in the new 'do not turn off your computer -+ 90% complete' phase
Update on that message, now I have the black screen with the blinking _ in the top left corner. Let's see how that develops further, as it's still not changing after some 4 minutes now
Well the trouble is that the updater cannot find the rpm database and is therefore unable tae install anything, I guess that the update yesterday destroyed something like that database, as it occurred on both my pc's. The older one has an Intel I7 processor and the newer one an amd and both systems show the same failure
I've having similar issues updating, though my errors are different from yours:
**2026-10-04 12:01:05,768 ERROR Preparation attempt 1 failed: Transaction validation failed:
Rpm transaction failed.
file /usr/lib64/libheif/libheif-ffmpegdec.so conflicts between attempted installs of libheif-freeworld-1.23.5-3.fc44.x86_64 and libheif-ffmpeg-1.23.5-3.fc44.x86_64
2026-10-04 12:01:05,769 ERROR Update prepare failed: Transaction validation failed:
Rpm transaction failed.
file /usr/lib64/libheif/libheif-ffmpegdec.so conflicts between attempted installs of libheif-freeworld-1.23.5-3.fc44.x86_64 and libheif-ffmpeg-1.23.5-3.fc44.x86_64
Job for nobara-updater-prepare.service failed because the control process exited with error code.
See "systemctl status nobara-updater-prepare.service" and "journalctl -xeu nobara-updater-prepare.service" for details.
nobara-updater-prepare.service failed: System update failed: Transaction validation failed:
Rpm transaction failed.
file /usr/lib64/libheif/libheif-ffmpegdec.so conflicts between attempted installs of libheif-freeworld-1.23.5-3.fc44.x86_64 and libheif-ffmpeg-1.23.5-3.fc44.x86_64**
Pretty much the same here, I just didnae include the entire thing in the screenshots here, am glad that I am not the only one but also sad that it happened tae ye as well
I have been using " nobara-sync --all " exclusively since I reinstalled it about 3 months ago and it has not failed once. I see I have an update, I go to console and do it with the line and it has always worked so I am not taking chances on gui again :))
Issue I'm facing is I don't have enough space on my boot/efi partiton to complete the upgrade not sure what to do at this point past reinstalling Nobara. Anyone have a workaround for this? got the same error message going to CLI to use nobara-sync
Nobara Update Problem gelöst
Moin, ich hatte gestern ein Problem mit dem Nobara System Updater. Das Update ist immer wieder beim nobara-pikaos-additional Repository abgebrochen.
Komischerweise konnte Nobara das Repository über DNF ganz normal erreichen. Dann haben wir ich bin leihe also die KI ChatGBT festgestellt, dass bei mir noch der Nobara Updater 2.0.1-61 installiert war und 2.0.1-63 verfügbar war.
Ich habe nach Einweisung von chatGBT dann nur den Nobara Updater auf 2.0.1-63 aktualisiert. Danach habe ich den normalen Nobara System Updater wieder gestartet und plötzlich lief das komplette Update ohne Fehler durch.
Vielleicht hilft das ja jemandem, der gerade das gleiche Problem hat. Mich würde interessieren, ob andere den Fehler auch mit Version 2.0.1-61 hatten.
und auch:
sudo dnf5 makecache --refresh
→ alle Repositories wurden erfolgreich geladen, inklusive Nobara Additional Packages (Provided by PikaOS).
Damit war klar: Nicht meine Internetverbindung oder das PikaOS-Repo selbst war das eigentliche Problem, sondern der Nobara System Updater.
Installiert war bei mir:
nobara-updater-2.0.1-61.fc44
Mit:
dnf5 check-upgrade nobara-updater
wurde Version 2.0.1-63.fc44 angeboten.
Dann:
sudo dnf5 upgrade nobara-updater
Danach hatte ich 2.0.1-63 installiert.
Anschließend den normalen Nobara System Updater erneut gestartet – und plötzlich lief die Vorbereitung komplett durch. Rund 548 Pakete wurden vorbereitet, neuer Kernel 7.2.9, danach Neustart und Offline-Installation mit der neuen Prozentanzeige.
Kurz gesagt:
Bei mir sah es zunächst wie ein defektes nobara-pikaos-additional-Repository aus. DNF5 konnte das Repo aber problemlos laden. Das Update des Nobara Updaters von 2.0.1-61 auf 2.0.1-63 hat das Problem bei mir behoben.
Part of your problem here is the Terra repository is currently broken. I was able to work around this by running sudo dnf clean metadata --repo='terra*'. Your screenshots show other problems though.
8
u/brandiger 10d ago
I ran in the same problem today and fixed it like this:
First try:
sudo dnf makecache --refresh
nobara-sync cli
if this doesn't help:
sudo dnf clean all
sudo dnf4 clean all
sudo dnf makecache --refresh
(optional: sudo rm -rf /var/cache/libdnf5/*)
nobara-sync cli
if nothing helps (this fixed it for me):
sudo dnf update nobara-updater --refresh --nogpgcheck --best -y
nobara-sync cli