I’ve read here and on Reddit that someone is using fedora 39, how can I update to it?
I’m using fedora 38 with gnome
(Pretty sure that I’m missing something but I’d prefer ask here)
Found this in my history:
sudo dnf upgrade --refresh
sudo dnf install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --releasever=39
sudo dnf system-upgrade reboot
I think that’s all to it!
People are testing F39, but the proposed release date is available in F39 Key Tasks and may change if testing reveals problems.
As @pilang posted that will do it but you might also check this out as well.
DNF system upgrade - Fedora Project Wiki
I upgraded from 38 to 39 about a month ago without issue’s but Fedora39 is still in beta.
Fedora Asahi will launch as F39, so we do encourage upgrades if you’re happy to test things (and deal with the potential for minor brokenness) 
Please do report successful upgrades! It should work but it’s always nice to get confirmation from users that it all goes smoothly.
I just upgraded from F38 to F39 successfully.
dnf system-upgrade download --releasever=39 barked about pipewire, so I just appended --allowerasing to the command, performed the upgrade, and installed pipewire manually after the upgrade to get sound, but other than that, the upgrade was smooth sailing.
Update to 39 successful, still no sound.
OS: Fedora Linux Asahi Remix 39 (Thirty Nine) aarch64
.:cccccccccccccccccccccccccc:. Host: Apple MacBook Air (M1, 2020)
.;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: 6.5.6-403.asahi.fc39.aarch64+16k
Did you dnf install pipewire and reboot?
Speakers aren’t supported yet. This is just about the existing headphone jack support.
Updated now to fedora 39 successful, except for two GNOME related stuff:
- Tray icon extension seems not working correctly
- Pop-shell extension disabled due to not compatible with GNOME 45
So not any Asahi related problem
I didnt have to remove pipewire, it stayed there through my upgrade. I see below that Hector says the speakers still arent supported yet so thats my issue, I thought 39 enabled them. Bluetooth for me until then. Stangely, now I have to type boot at the boot loader screen, it stopped booting automatically, leaves me at a black screen with =>
Ah - you’ll want to stick with Bluetooth or audio jack then, which will always provide a better quality than the small low-quality speakers they add to a laptop. And while Apple uses slightly nicer speakers in their laptops, they won’t be enabled until they can sound nice as outlined here.
An upgrade from F38 to F39 using the steps outlined by Joakim Pilang works seamlessly.
However, sound will not work if running as root.
Two files need to be edited -
/usr/lib/systemd/user/pipewire-pulse.service
and
/usr/lib/systemd/user/pipewire-pulse.socket
The statement “ConditionUser=!root” needs to be commented out.
I originally ran with KDE Plasma, but reverted to XFCE as KDE is too top-heavy/bloated for me.
I am running an M1 Mini with 16GB.
Yesterday, I upgraded my F38 Asahi Gnome install to F39. I’ve had installed telegram-desktop from RPMFusion repos, and I also had a package installed manually which required python 3.11 (and was not in any repos). Since telegram-desktop in RPMFusion wasn’t built with latest qt6 packages, I needed to use --best --allow-erasing options when upgrading, and also I removed my custom package before upgrade. With these two, I upgraded successfully to F39.
After updated, I installed telegram-desktop from RPMFusion repos, which downgraded Qt6 packages to be compatible.
There was also something, which was not problematic: for whatever reason (I didn’t spend time trying to figure out why), when upgrading my kernel-devel package was downgraded to some old version (IIRC, to kernel-devel-6.3.8), but after upgrading to F39 I ran dnf update and this package was updated to latest version without any problems. Don’t know why it happened, but it was harmless.
On my side, I performed upgrade sucessfully through CLI but I had to remove yt-dlp python3-proton-client prior to that.
Before that I was getting following errors :
sudo dnf system-upgrade download --releasever=39
Problème 1: package protonvpn-gui-1.12.0-1.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
- python3-3.11.6-1.fc38.x86_64 from @System does not belong to a distupgrade repository
- problème avec le paquet installé protonvpn-gui-1.12.0-1.noarch
Problème 2: package python3-3.11.6-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.6-1.fc38, but none of the providers can be installed
- package python3-proton-client-0.7.1-3.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
- python3-libs-3.11.6-1.fc38.x86_64 from @System does not belong to a distupgrade repository
- problème avec le paquet installé python3-proton-client-0.7.1-3.noarch
Problème 3: problème avec le paquet installé yt-dlp-2023.10.07-1.fc38.noarch
- package yt-dlp-2023.07.06-2.fc39.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed
- package yt-dlp-2023.07.06-2.fc39.noarch from fedora-modular requires python(abi) = 3.12, but none of the providers can be installed
- package yt-dlp-2023.07.06-2.fc39.noarch from updates-modular requires python(abi) = 3.12, but none of the providers can be installed
- python3-3.12.0-1.fc39.i686 from updates-modular does not belong to a distupgrade repository
- python3-3.12.0-1.fc39.i686 from fedora-modular does not belong to a distupgrade repository
- python3-3.12.0-1.fc39.i686 from fedora does not belong to a distupgrade repository
- cannot install both python3-3.12.0-1.fc39.x86_64 from fedora and python3-3.11.6-1.fc38.x86_64 from @System
- cannot install both python3-3.12.0-1.fc39.x86_64 from fedora-modular and python3-3.11.6-1.fc38.x86_64 from @System
- cannot install both python3-3.12.0-1.fc39.x86_64 from updates-modular and python3-3.11.6-1.fc38.x86_64 from @System
- package python3-protonvpn-nm-lib-3.14.0-1.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
- yt-dlp-2023.10.07-1.fc38.noarch from @System does not belong to a distupgrade repository
- problème avec le paquet installé python3-protonvpn-nm-lib-3.14.0-1.fc38.noarch
After upgrade I reinstalled yt-dlp through dnf, and installed Proton VPN through Gnome Software.
Fedora 39 is worth the upgrade. Of course as often we’ve some Gnome Extensions not compatible (asusctl-gex, Dash to Dock for COSMIC, GSConnect).
I also did upgrade my SilverBlue workstation. Also success in the end, after a small issue encountered :
rpm-ostree rebase fedora:fedora/39/x86_64/silverblue got stuck at a time (I had some network connectivity issues) and I had to reboot as rpm-ostree cancel does not work :
rpm-ostree cancel
Cancelling transaction: rebase fedora:fedora/39/x86_64/silverblue
CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
^CAwaiting transaction cancellation...
Well done Fedora Team for this new version! 
Upgraded without issue a GNOME Desktop-based system using dnf5. Happily, the GNOME extension dash-to-dock now works.
Upgraders all: Don’t forget to run rpmconf -a after rebooting!
Upgraded ok to fedora 39 here, got into a few issues though :
- Some trouble related to rpmfusion packages, simply removed these
rpm -qa --qf "%{NAME} %{PACKAGER}\n" | grep "RPM Fusion" | cut -d\ -f1 | sort gets you the list of installed packages from this repo
- Then the upgrade refused to go through due to some asahi packages ‘conflicting’
$ sudo dnf system-upgrade download --releasever=39 --best --allowerasing
Transaction check succeeded.
Running transaction test
Error: Transaction test error:
file /usr/lib/os-release from install of fedora-asahi-remix-release-identity-basic-39-3.noarch conflicts with file from package asahi-fedora-remix-release-identity-basic-38-0.1.noarch
Without best / allowerasing dnf was reporting two problems :
Error:
Problem 1: package asahi-fedora-remix-release-common-38-0.1.noarch from @System requires fedora-repos(38), but none of the providers can be installed
- fedora-repos-38-1.noarch from @System does not belong to a distupgrade repository
- problem with installed package asahi-fedora-remix-release-common-38-0.1.noarch
Problem 2: problem with installed package fedora-repos-modular-38-1.noarch
- cannot install both fedora-repos-39-1.noarch from fedora and fedora-repos-38-1.noarch from @System
- cannot install both fedora-repos-39-1.noarch from fedora-modular and fedora-repos-38-1.noarch from @System
- cannot install both fedora-repos-39-1.noarch from updates-modular and fedora-repos-38-1.noarch from @System
- package asahi-fedora-remix-release-common-38-0.1.noarch from @System requires fedora-repos(38), but none of the providers can be installed
- package asahi-fedora-remix-release-38-0.1.noarch from @System requires asahi-fedora-remix-release-common = 38-0.1, but none of the providers can be installed
- fedora-repos-modular-38-1.noarch from @System does not belong to a distupgrade repository
- problem with installed package asahi-fedora-remix-release-38-0.1.noarch
Turns out I missed a package name change at some point which required :
$ sudo dnf swap asahi-fedora-remix-release* fedora-asahi-remix-release-workstation
$ sudo dnf swap asahi-fedora-remix-logos fedora-logos
After the two swaps above, upgrade went through.
The upgrade went well here with the --alloerasing argument