For existing installations only:
You cannot skip versions. For example you cannot go from Nobara 39 to Nobara 41.
Nobara 39 is no longer supported and is not receiving any more updates.
First and foremost, update your system using one of the recommended methods. You will need to resolve any conflicts reported before going further.
Next, update the repos:
sudo dnf update fedora-repos fedora-gpg-keys nobara-repos nobara-gpg-keys --releasever=41 --nogpgcheck --refresh
NOTE:
Errors during downloading metadata for repository 'nobara-baseos-41':
- Status code: 404 for https://apac-nobara-baseos.nobaraproject.org/41/repodata/repomd.xml (IP: 2606:4700:20::681a:46a)
- Status code: 404 for https://eue-nobara-baseos.nobaraproject.org/41/repodata/repomd.xml (IP: 2606:4700:20::ac43:443f)
- Status code: 404 for https://euw-nobara-baseos.nobaraproject.org/41/repodata/repomd.xml (IP: 2606:4700:20::681a:56a)
- Status code: 404 for https://usw-nobara-baseos.nobaraproject.org/41/repodata/repomd.xml (IP: 2606:4700:20::681a:56a)
- Status code: 404 for https://nobara-baseos.nobaraproject.org/41/repodata/repomd.xml (IP: 2606:4700:20::681a:46a)
Error: Failed to download metadata for repo 'nobara-baseos-41': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
This can be safely ignored. The repository paths are changed in 41, and 40 still has the old repo paths. It will still allow you to install the new repo packages, just confirm (press y). Once the new repo packages are installed the 404 errors will no longer occur.
NOTE:
Example:
If you have nobara.repo
and nobara.repo.rpmnew
— you should do this:
sudo cp /etc/yum.repos.d/nobara.repo.rpmnew /etc/yum.repos.d/nobara.repo
NOTE:
sudo dnf remove rocm* obs-cef obs-studio-plugin-webkitgtk
Then:
sudo dnf update kernel -y --refresh
sudo dnf distro-sync --refresh
Once this is finished you can reboot and your system should be upgraded to N41.
If you removed obs-cef, it auto-removes obs-browser. You will want to reinstall it:
sudo dnf install obs-studio-plugin-browser
Once rebooted into N41 run the ‘Update System’ app once more to cleanup any lingering packages that may have been deprecated and to apply Nobara 41 quirks/fixups.
ADDITIONAL NOTE, NOT PART OF UPGRADE STEPS, DO NOT USE:
If you are familiar with upgrading Nobara or Fedora, you may have noticed this time we are NOT using the traditional upgrade steps:
DON'T USE THESE. sudo dnf install dnf-plugin-system-upgrade -y sudo dnf system-upgrade download --releasever=41 -y sudo dnf system-upgrade reboot
The reasoning behind this is because we found this method would often fail on non-standard hardware such as macbooks or surface devices, because they would not boot into the install environment. By doing it the new way we provided it avoids relying on the install environment in order to upgrade.
First and foremost, update your system using one of the recommended methods. You will need to resolve any conflicts reported before going further.
Next, update the repos:
sudo dnf update fedora-repos fedora-gpg-keys nobara-repos nobara-gpg-keys --releasever=40 --nogpgcheck --refresh
If you have any *.rpmnew files in /etc/yum.repos.d/ you should replace the originals with them.
Example:
If you have nobara.repo
and nobara.repo.rpmnew
— you should do this:
sudo cp /etc/yum.repos.d/nobara.repo.rpmnew /etc/yum.repos.d/nobara.repo
If you have this file you must remove it:
/etc/yum.repos.d/nobara-nvidia-new-feature.repo
it is no longer used in N40.
Next, it’s time to sync all of your packages to N41 versions:
If you are on the Gnome version, now is the time to disable your extensions temporarily via the extension manager global switch until you're fully upgraded and booted into Nobara 41 to avoid a potential freeze during package upgrading.
sudo dnf update kernel -y --refresh
sudo dnf distro-sync --refresh
Once this is finished you can reboot and your system should be upgraded to N40.
ADDITIONAL NOTE, NOT PART OF UPGRADE STEPS, DO NOT USE:
If you are familiar with upgrading Nobara or Fedora, you may have noticed this time we are NOT using the traditional upgrade steps:
DON'T USE THESE. sudo dnf install dnf-plugin-system-upgrade -y sudo dnf system-upgrade download --releasever=40 -y sudo dnf system-upgrade reboot
The reasoning behind this is because we found this method would often fail on non-standard hardware such as macbooks or surface devices, because they would not boot into the install environment. By doing it the new way we provided it avoids relying on the install environment in order to upgrade.