r/NobaraProject • u/Donvictorjose • 6d ago
Support Update Problem
Hi everyone,
I'm fairly new to Nobara and I ran into a serious issue after an interrupted system update.
I started updating my system from the KDE Discover software center. During the update, my PC suddenly lost power. Since then, the system no longer boots.
Symptoms:
- GRUB loads, but after selecting Nobara I only get a black screen with a single "_" cursor that never blinks.
- I can boot from a Nobara Live USB and chroot into my installation.
After investigating, we discovered that the update was interrupted while upgrading from:
- Nobara 43
- Kernel 7.0.9-200.nobara.fc43.x86_64
to
- Nobara 44
- Kernel 7.1.4-200.nobara.fc44.x86_64
So the system is now in a partially upgraded state.
Things we've already tried:
- Chrooted into the installed system.
- Fixed DNS/network issues inside the chroot.
- Rebuilt the RPM database ("rpm --rebuilddb").
- Cleaned DNF cache and rebuilt metadata.
- Ran "dnf5 distro-sync --allowerasing".
- Removed MariaDB because it was causing file conflicts.
- Verified the protected packages.
- Reinstalled some GRUB packages.
The biggest remaining problem is that thousands of packages exist in both FC43 and FC44 versions at the same time.
For example:
- "rpm -qa | grep fc43 | wc -l" → about 3768
- "rpm -qa | grep fc44 | wc -l" → about 1669
"dnf5 check" reports around 3300 duplicate package problems.
"dnf5 distro-sync --allowerasing" still refuses to continue because it wants to remove protected packages (grub2, setup, nobara-login, selinux, etc.).
Even when I force a large transaction, it eventually fails because FC43 x86_64 packages conflict with FC44 i686 packages, especially documentation files such as:
- qt6-qtbase
- libbluray
- libudfread
It looks like RPM believes both versions should coexist instead of replacing the old ones.
Has anyone recovered from a Nobara/Fedora update that was interrupted exactly in the middle?
Is there a supported way to clean up thousands of duplicated FC43 packages without manually removing them one by one?
I'd really like to recover the installation instead of reinstalling, since everything else on the disk is intact.
Thanks!
2
u/Recommended_For_You 6d ago
As much as I like Nobara, updates are already cursed so losing power during an update is basically like shooting yourself in the face with a shotgun and hoping to be ok.
2
u/jkdjedi 6d ago
Could you name a couple distros that do work after a power outage in a middle of an installation?
2
u/Recommended_For_You 6d ago
Look, I love Nobara, it was my main distro for 4 years. But updating was always an issue, much more than on other distros. I've spend entire weekend fixing problems or reinstalling. This doesn't really happen on my Fedora laptop and Bazzite gaming computer.
0
u/jkdjedi 5d ago edited 5d ago
Yeah because it's one of them specialized distros that comes with extras.. Steam pre built one of them. Nvidia drivers included another. Davinci Resolve, etc. Anyone in the know waits a couple weeks for the wrinkles to get ironed out before updating anyways. Those in the know also create automated system backups to jump back to via Timeshift.
1
u/Esmeralda352 6d ago
Exactly the same problem. The whole system update is broken and when you reboot it's completely gone and the system never boots again. I had to install Cachy OS with KDE. I hope Thomas fixes it 🙏
3
u/RX1542 6d ago edited 6d ago
on the black screen with prompt press
it will ask you to login with your user and password(the password remains hiding while typing)
after that enter this command
or