Announcing Fedora Linux 40 Beta

The Fedora Project is pleased to announce the immediate availability of Fedora Linux 40 Beta, the next step towards our planned Fedora Linux 40 release at the end of April.

Get the the prerelease of any of our editions from our project website:

Or, try one of our many different desktop variants (like KDE Plasma, Xfce, or Cinnamon) from Fedora Linux Spins.

You can also update an existing system to the beta using DNF system-upgrade.

Beta release highlights

Some key things to try in this release!

PyTorch is a popular open-source machine learning framework. We want to make using this tool in Fedora Linux as easy as possible, and it’s now available for you to install with one easy command: sudo dnf install python3-torch

Note that for this release, we’ve only included CPU support, but this lays the groundwork for future updates with support for accelerators like GPUs and NPUs. For now, this is suitable for playing around with the technology, and possibly for some light inference loads.

Fedora IoT now uses ostree native containers, or “bootable containers”. This showcases the next generation of the ostree technology for operating system composition. Read more in the documentation from ostree and bootc.

Also on the immutable OS front, we’ve revived the “Atomic Desktop” brand for the growing collection of desktop spins based on ostree. An ever-expanding collection of obscure mineral names was fun, but hard to keep straight. We’re keeping well-known Silverblue and Kinoite, and other desktop environments will be, for example, Fedora Sway Atomic and Fedora Budgie Atomic.

Other notable updates

Fedora KDE Desktop now ships with Plasma 6, thanks to a lot of hard work from the Fedora KDE Special Interest Group and the upstream KDE project, is Wayland-only. (Don’t worry — X11-native apps will still run under Wayland.)

Fedora Workstation 40 Beta brings us GNOME 46. We’re bringing you Podman 5 for container management. The AMD ROCm accelerator framework is updated to version 6. And, we’ve got the updated language stacks you expect from a new release: LLVM 18 (that’s clang and friends), as well as GCC 14 (with newer glibc, binutils, and gdb).

There are many other changes big and small across the release. See the official Fedora Linux 40 Change Set for more, and check your favorite software for improvements — and, since this is a beta… possibly bugs!

Testing needed

As with any beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora Quality team via the test mailing list or in the #quality channel on Fedora Chat. As testing progresses, common issues are tracked in the “Common Issues” category on Ask Fedora.

For tips on reporting a bug effectively, read how to file a bug.

What is the beta release?

A beta release is code-complete and bears a very strong resemblance to the final release. If you take the time to download and try out the beta, you can check and make sure the things that are important to you are working. Every bug you find and report doesn’t just help you, it improves the experience of millions of Fedora Linux users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can. Your feedback improves not only Fedora Linux, but the Linux ecosystem and free software as a whole.

Fedora Project community New in Fedora


  1. Alex

    Headless remote desktop does not work in beta release, all fields are gray and disabled for input. journalctl show error when enabling this from UI

    • Trung LE

      I second that. It’s seems to me some components might be missing in order for that feature to run

      • Romek

        Yep, gnome-remote-desktop is 45.1-4. Rawhide has 46.0-1 so i suppose it would be OK soon 🙂

    • Looking into this, but I already found at least one obvious error in the package, fixing that:

      It doesn’t seem like the package depends on gnome-shell or gdm, which is…interesting. I guess it’s sort of intended to be installed on a system which already has GNOME, not on a minimal install, but possibly this can be tweaked, I’ll ask the team about it.

      Will try and get this working locally and see how it goes…

    • Hmm, I can’t really find any clear documentation of how gnome-remote-desktop is supposed to be used, so I’m not sure about this one. Can you explain in more detail exactly how you tried to use it, so I can try and reproduce that? i.e. what type of of Fedora install did you start from, then what packages did you install and what exactly did you do to try and configure the server end and connect from the client end…thanks!

      • sim

        Joan Torres Remote headless Wayland sessions on GNOME

        you can search this on youtube, good explanation how it works

    • dtunma

      I’ve been using Gnome 46’s headless remote logins (via GDM and RDP) for two days. To make it work:
      1. Update to latest (this will install gnome-remote-desktop-46.0-1.fc40)(*1)
      2. Apply a workaround: disable selinux
      3. This is optional. A workaround for polkit blocking some access: A script is available at post made by “matt335672 commented on Jun 5, 2023”. WARNING: After applying this script, whether it’s enabled or enabled-then-disabled, the system may fail to boot if selinux is revert back to enforcing.

      (*1) I also tried gnome-remote-desktop-46.0-2.fc41, but step 2 workaround is still required.

      • tima

        Yes, it’s working with your steps. It seams that gnome connections does not support headless login (tried on F39), xfreerdp works fine with selinux disabled.
        Tried also with microsoft remote desktop from macos, does not work. This feature will work only with Linux, not other platforms?
        I did not turn off firewall, just open port 3389 and 3390 (if you have classic rdp and remote login enabled, it changes port)

        • jamo

          Sound is not working in regular RDP session, and in headless RDP session? both client and server are fedora
          On Windows RDP client, sound works

    • Somdutt Patnaik

      Plasma 6?

  2. menur

    gnome disk utility still does not show size of nvme disks, please test it on real devices not only on vm’s, as this is bug from gnome 45, but still not resolved
    You are selling slimbook laptops with nvme, where it show Unknown for disk size

    • Lucious

      I found your comment interesting so I checked my setup. On my desktop, the samsung nvme disk size shows just fine in disk utility. However, on my laptop the Intel nvme disk size is not shown. Weird. Besides the different manufacturers and the laptop being encrypted, they’re both on fedora 39.

      • Chris

        Had a problem with an intel M.2 660p 500GB, if you go on the Solidigm website they have a fixit bootable (I.T guys) for a usb key and it automatically fixed the firmware problem with my device, guess was running a firmware that was 4 versions out of date.
        For the last 8 years using in a 5th gen intel nuc there were multiple io errors using with opensource. Sometimes the drive would kill the boot record, no boot, no OS, just a big error on screen. Never had much luck with dealing with Intel, since Solidigm took over, you might want to go get that file cause they said they are only going to support those fancy intel devices for one year. Solidigm seems intent on selling their new devices in their fancy white and purple boxes.
        Basically boot from usb key, it scans your box and you go through the prompts and it’s fixed, software is useful for multiple ssd devices. Like I said, get that file quick. Not sure that company is going to last long,

    • I also cannot reproduce the issue you’ve stated. Best to file a bug report with all details, or else no-one will know about it, and it’ll never be fixed.

    • I can also confirm that my Samsung NVME disk is reporting its size correctly in F39 Gnome 45.

    • This should be reported as a bug at , as that’s the storage library that GNOME Disks uses. I’m not sure exactly what info they need to debug it, and it doesn’t seem to be very ‘chatty’ by default, so…I’d just file an issue and see if they ask for some specific debugging steps.

  3. Leslie Satenstein

    with Files command, the title “Size” should really be “Items”.

    Listed are the number of entries in the directories. Second level within directory title is correct (shows size in m/k/g bytes)

    • The most common case is that a directory will contain both files and subdirectories. So the title has to cover both cases as best as possible.

  4. iumun

    I always delete Firefox browser and install Brave. Deleting Firefox from Software wasn’t working for me, icon is still present in menu. sudo dnf remove firefox worked, not sure why.
    Also I always delete multiple apps from Software, which I don’t need, in some cases iI needed to click Uninstall multiple times.
    This was clean install on bare metal.

  5. Darvond

    Can’t quite leap on this one, but thankfully I’m not a Gnome user; learned helplessness is not my game. (Looking forward to COSMIC though.)

    It looks like I’d lose out on some Trinity utilities, and have enough packages downgraded that I wouldn’t feel safe/sane to take the leap.

  6. estamos em festa pois está lançamento tanto Beta como Plasma ,ai fica a escolha do internauta ,como amo todo sistema Linux ,e melhor ainda sem restrições de uso ,venham participar deste novo lançamento ,obrigado

  7. Keeping the Silverblue and Kinoite names is a mistake as it will confuse new users. Should have followed the naming convention all the way through and called them Fedora Gnome Atomic and Fedora KDE Atomic. Simple and straightforward.

    • They probably wanted to avoid the discussion whether Silverblue should become “GNOME Atomic” or “Workstation Atomic”.

  8. Artsiom


    amdgpu: Secure display, Generic: Failure

    AMD Ryzen™ 3 5300U

  9. Petar

    Kodi can’t start the movie, but if you fast forward a bit, it works without problems.

  10. I don’t think the PyTorch instructions are correct, as there is no package named


    . There is instead


    , and it does not provide



  11. temurin

    AMD GPU for some strange reason disables it self, like it’s going in sleep. SSH works on machine, just turning on monitor does not work. I see that LED logo on GPU is not turned on.
    Disabling Screen lock fixes this issue.

  12. Grandpa Leslie Satenstein

    Went to the website that is promoted by Magazine and by Distrowatch.
    Clicked on what I think is the KDE 6.x AMD type download.
    Link points to nowhere.

  13. adm

    NFS share is not able to start rpdbind because there is missing directory sm in /var/lib/nfs/statd/sm
    statd and sm folders are missing, after creating them, everything works, service starts

    • Those directories are part of the


      package, which also contains the


      service and the


      server binary. If I install that package, I get all three, and running an NFS server works. How exactly did you try to set this up? Thanks.

  14. Hey everyone! Thank you for the feedback. Please remember that these comments aren’t regularly tracked by Fedora developers. (Most people have too many inboxes already!) If you find a problem, please report on the test list or in the Fedora Chat #quality channel. (Or, if you’d like to start with a more informal conversation, perhaps

  15. Peter Braet

    Do gparted and dnfdragora start and work in GUI under Wayland?

  16. hammerhead corvette

    I know it’s well intentioned but having CPU only Pytorch is going to confuse the hell out of people and the forums will be full of questions about it. I’ll be looking to head it off at the pass, I might do a write up for it. . .

  17. Dan

    Does Plasma Wayland work with Nvidia in Fedora 40?
    It doesn’t work well in Fedora 39. The performance is absolutely dreadful on my Nvidia laptop.
    And there’s no way to make Nvidia the “primary GPU” on Wayland which is a huge problem if you use an external display.

  18. Irritated Skeptic

    “Don’t worry — X11-native apps will still run under Wayland.”

    Not necessarily. X4 Foundations won’t work with Xwayland if both have adaptive frame rate active. It stutters making the game unplayable. It functions fine with Xwayland isn’t 100% drop in compatible, and I get tired of people saying it is despite even Wayland’s own developers saying it only implements the most commonly used parts of X11.

    • FYI, a secret that the KDE SIG does not want you to know, but you can still (technically “again”, after I reintroduced the package in time for this Beta release) get a “Plasma (X11)” session option back with “sudo dnf install plasma-workspace-x11”. (This will also install kwin-x11 as a dependency.)

  19. Paul Rockwell

    Where’s the ISO for aarch64? Can’t test this on virtual machines that are ARM SystemReady like VMware Fusion without it.

  20. dnf install python3-torch
    Poslední kontrola metadat: před 0:19:34, St 3. dubna 2024, 14:32:07.
    Problém: protichůdné požadavky
    – nothing provides needed by python3-torch-2.1.2-3.fc40.x86_64 from fedora
    – nothing provides needed by python3-torch-2.1.2-3.fc40.x86_64 from fedora
    (zkuste přidat ‘–skip-broken’ pro přeskočení odinstalovatelných balíčků)

    dnf install xorg-x11-drv-nvidia-470xx akmod-nvidia-470xx
    Žádná shoda pro argument: xorg-x11-drv-nvidia-470xx
    Žádná shoda pro argument: akmod-nvidia-470xx

    Repo rpmfusion povoleno.

    Testováno na dvou rozdílných počítačích 6.8.2-300.fc40.x86_64

  21. realmente sensacional ,estamos indo direto para a grande vantagens da tecnologia de ponta ,pós nosso Fedora tem uma nova copilação neste grande sistema Linux ,livre sem restrições e sem tantos erros ,obrigado

  22. Parm Lehal

    dnf distrosync did upgrade for KDE spin install but no display worked. No LXDE, No LXQt, not even gnome. Had to reinstall from scratch as distrosync failed to downgrade to 39. It is not even at alpha quality.

    • distro sync is not a recommended upgrade method, especially when upgrading to a new release. It does not install new dependencies. It only updates existing packages. It is mainly intended for use as a (possible) recovery method when the normal dependency resolution fails.

  23. Max

    Dear all, I have been using Fedora 39 on a Lenovo L380 notebook for about a month now. In general the user experience is very good. I only report 2 problems: I can’t update two drivers that are constantly reported in the software center, I have Telegram Desktop installed that goes into crush often

  24. Alex M.

    Fedora 40 beta Gnome y Plasma, en mis portátiles Acer y Dell el wifi funciona, pero no reconoce la clave de acceso a mis dos cuentas en 2.4 GHz y 5 GHz.

  25. Alex M.

    Fedora 40 beta Gnome and Plasma, on Acer and Dell laptops the wifi works, but it does not recognize the access key to my two accounts on 2.4 GHz and 5 GHz.

  26. Abegunde Omolayo

    The OS looks great with the introduction of KDE, but Fedora stinks with Flet programming in both distros 39 & 40. Error: error while loading shared libraries: Manage to get, another error will comes up. Pls try and fix it

    • Abegunde Omolayo

      I solve the problem using the followin steps:

      Run the command to install the packages:
      sudo dnf install mpv-libs
      sudo dnf install mpv-devel

      Searching the packages in directory
      cd /usr/lib64
      Searching the mpv

      The answer must be:

      Creating a symbolic link
      sudo ln -s /usr/lib64/ /usr/lib64/

Leave a Reply

The interval between posting a comment and its appearance will be irregular so please DO NOT resend the same post repeatedly. All comments are moderated but this site is not monitored continuously so comments will not appear as soon as posted.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. Fedora Magazine aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. The Fedora logo is a trademark of Red Hat, Inc. Terms and Conditions