Announcing Fedora Linux 38 Beta

The text "Fedora Linux 38 Beta" on the default Fedora Linux 38 background image: cumuloform clouds with a green field in the background

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

Download this prerelease from our Get Fedora site:

Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices like the Raspberry Pi:

Beta Release Highlights

Fedora Workstation

Fedora 38 Workstation Beta includes GNOME 44. It’s currently in beta, with a final release expected at the end of March. GNOME 44 includes a lot of great improvements, including a new lock screen, a “background apps” section on the quick menu, and improvements to accessibility settings . In addition, enabling third-party repositories now enables an unfiltered view of applications on Flathub. 

Other updates

We always strive to bring new security features to users quickly. Packages are now built with stricter compiler flags that protect against buffer overflows. The rpm package manager uses a Sequoia-based OpenPGP parser instead of its own implementation.

If you’re profiling applications, you’ll appreciate the frame pointers now built into official packages. This makes Fedora Linux a great platform for developers looking to improve Linux application performance.

Of course, there’s the usual update of programming languages and libraries: Ruby 3.2, gcc 13, LLVM 16, Golang 1.20, PHP 8.2, and much more!

Testing needed

Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA 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.

More information

For more detailed information about what’s new on Fedora Linux 38 Beta release, you can consult the Fedora Linux 38 Change set. It contains more technical information about the new packages and improvements shipped with this release.

New in Fedora


  1. David

    Is the mobility spin still in the plan for F38? I recall it was approved, but didnt see beta images (yet).

  2. Greg

    Of course, there’s the usual update of programming languages and libraries: Ruby 3.2, gcc 13, LLVM 16, Golang 1.20, PHP 8.2, and much more!

    LLVM16 isnt even in the Beta. might wanna fix that

    • Zbigniew Jędrzejewski-Szmek

      LLVM16 final hasn’t been released yet, and the pre-release versions may contain breaking changes, so we don’t want to include them. The final version will be included in F38 if it is released in time.

    • Leo

      When you change dnf4 to dnf5. It’s really slowly.

  3. Thomas

    Installed the upgrade 37 – 38b via dnf on my Lenovo yoda 9 – everything smooth 🙂

  4. I’m a big fan of Fedora, if I want something for a more static setup I’ll use Debian but for everything else, Fedora or Arch. I need to try it again, dnf has never won any races and the repos aren’t as straight cut as the more unified Arch approach or the popular Ubuntu support, only things holding me back from hopping back and forth between it and Arch as the undecided guy I am.

  5. Patrick O'Callaghan

    Rather than simply pointing to the various downloads, it would be useful to include a link to the proposed changes in each version. This can be surprisingly laborious to find if you don’t already know where to look.

  6. Amal Barman

    I am testing server version on VirtualBox environment. It has been installed perfectly and working without any error.

    • Amal Barman

      First installation has been crashed. Now trying to install it second time. Some version mismatch is present in case on “MATE Desktop” environment.

  7. Dave Hugh

    Upgraded from Fedora Workstation 37 to 38 Beta using DNF on my ASUS AMD Ryzen™ 7 4800H Laptop. Python3-Pillow reported a missing dependency. Since I didn’t need, uninstalled that module, and the upgrade proceeded without issue. Otherwise uneventful. I’m always impressed with the stability of Fedora’s forward looking distributions.

  8. Rodd

    Having troubles running dnf system-upgrade –releasever 38 download


    Problem: package gstreamer1-plugin-libav-1.22.0-2.fc38.i686 requires, but none of the providers can be installed
    – package gstreamer1-plugin-libav-1.22.0-2.fc38.i686 requires, but none of the providers can be installed
    – conflicting requests
    – libavcodec-free-6.0-1.fc38.i686 has inferior architecture
    – package gstreamer1-plugin-libav-1.22.0-2.fc38.x86_64 requires, but none of the providers can be installed
    – package gstreamer1-plugin-libav-1.22.0-2.fc38.x86_64 requires, but none of the providers can be installed
    – package libavcodec-freeworld-5.1.2-9.fc38.x86_64 requires, but none of the providers can be installed
    – package libavcodec-freeworld-5.1.2-9.fc38.x86_64 requires, but none of the providers can be installed
    – package ffmpeg-libs-5.1.2-9.fc38.x86_64 conflicts with libavcodec-free provided by libavcodec-free-6.0-1.fc38.x86_64

    I don’t have gstreamer1-plugin-libav installed so I’m not sure what the issue is.

    • It looks like you may need to remove ffmpeg-libs before doing the upgrade. But this isn’t meant to be a support forum. Use for user support. Thanks.

      • Rodd

        I’m not asking for support.

        Apparently it’s okay for people to say it worked, but not feedback it didn’t work?

        I’m letting people know there’s issues.

        • Feedback that something doesn’t work is fine. I just took your last statement “… so I’m not sure what the issue is” to be a request for support.

          It’s not necessarily surprising that third-party packages haven’t caught up with the versions of the software that Fedora has just released in its beta though. You may need to disable and uninstall all third-party software to upgrade to the beta.

    • Might try adding “–allowerasing” to the dnf command and see if that gets you past the issue. I’m guessing it would.

  9. Bill Davidsen

    I did my regular test, using qemu I installed WorkStation, i3, KDE, and Cinnamon, then updated to usual. I did wait 2 days after the initial and updated. I’m using a Xeon w/ 8 cores & 32G RAM in 2T solid disk.
    I note that on the WorkStation the initial user name did not have the ability to change the user name from 1000 or the dir out of /home. Why?
    I also see something else is needed to chaange between NVIDIA and what ever default is used for Dell.
    Otherwise it’s staple enough for a large test, pretty fast updated.

  10. crd

    Does anyone know if the hibernation situation will be improved in F38 Workstation? See, for example,

  11. Chuck

    You need to correct your ‘Testing Needed’ section to point to the correct channel – #quality does not exist on Libera, maybe #fedora-qa?

    • It’s not referring to Libera. It’s referring to our Matrix server. I’ve updated the post with a link.

  12. Darvond

    So from what I understand, this is initializing the steps to allow users to drop GRUB in favor of SystemD-Boot? Because I’d like any reason to boot it out of my boot order. (Currently using ReFind. Not bad, but could be so much simpler.)

    • Zbigniew Jędrzejewski-Szmek

      Where did you get this impression? This article doesn’t even mention the bootloader.

      • Darvond

        Right around the item “Unified Kernel Support” and the fact that I recently noticed a few new bootloaders had been added to SystemD-boot.

        I’d really like literally any excuse for Grub to be gone.

        • Zbigniew Jędrzejewski-Szmek

          There are no plans for significant changes as of now. UKIs will most likely start being supported by grub2; patches are under review. Systemd-boot will continue to be provided as an option. We’re currently working on getting it signed by a unique key, to make self-enrollment easier. (I’m not sure what you mean by bootloaders being added to systemd-boot: it is a bootloader.) Boot paths without grub2 will likely be used in some installations like virtual machines or edge devices, but “normal” machines will not change much.

          • Jesse

            I would prefer a more reliable shutdown. Right now it takes so long to shutdown I end up pressing the reset button just to get done.

  13. redouane

    I got XFCE Beta 38 and hang after loging the session.
    the keyboard is unresponsiveness (no led from shift of any combinaison keys.
    after trying two times XFCE , I ‘ll go with KDE hoping is working;

    • Zbigniew Jędrzejewski-Szmek

      Please report a bug, with details about hardware and logs if possible.

  14. gnudna

    Has anybody tested the latest arm version with new Mac M1/M2 cpu’s? does it work out of the box?

  15. Pete

    the article could also describe the dnf way on how to update to F38 beta…

  16. Fedorauser

    There since version 33 and always extremely impressed by the performance implemented by the developers. My respect for this great distribution.
    Only the backgrounds of the desktop make me more depressed over the years and that of version 38 crowns it. I’m going to see my therapist.

    Best regards

      • Claude

        This article should be updated.

        I wonder if we type f* instead of the number of the release if we would get all the supplemental wallpapers?

        • You can use this command to get a list of all the backgrounds available via the repository

          dnf list –all *background*

          • There should be a backslash in front of each * in that command. They were filtered out.

            • Claude

              The -all is not recognized as an argument.

              • $ dnf list –all \*background\* | head -20
                Last metadata expiration check: 0:02:31 ago on Mon Apr 3 13:39:59 2023.
                Installed Packages
                desktop-backgrounds-compat.noarch 37.0.0-4.fc37 @updates
                f36-backgrounds-base.noarch 36.1.1-2.fc37 @fedora
                f36-backgrounds-extras-base.noarch 36.1.1-2.fc37 @fedora
                f36-backgrounds-extras-mate.noarch 36.1.1-2.fc37 @fedora
                f36-backgrounds-mate.noarch 36.1.1-2.fc37 @fedora
                f37-backgrounds-base.noarch 37.0.5-1.fc37 @updates
                f37-backgrounds-mate.noarch 37.0.5-1.fc37 @updates
                mate-backgrounds.noarch 1.26.0-3.fc37 @fedora
                Available Packages
                adapta-backgrounds.noarch fedora
                beefy-miracle-backgrounds.noarch 16.91.0-21.fc37 fedora
                beefy-miracle-backgrounds-gnome.noarch 16.91.0-21.fc37 fedora
                beefy-miracle-backgrounds-kde.noarch 16.91.0-21.fc37 fedora
                beefy-miracle-backgrounds-single.noarch 16.91.0-21.fc37 fedora
                beefy-miracle-backgrounds-xfce.noarch 16.91.0-21.fc37 fedora
                budgie-backgrounds.noarch 1.0-1.fc37 updates
                constantine-backgrounds.noarch 12.1.1-23.fc37 fedora
                constantine-backgrounds-extras.noarch 12.1.1-23.fc37 fedora

          • Claude

            That said, typing f* instead of the version number work.

            It goes back to fedora 21

  17. tsyang

    Does F38 Beta resolve the EFI boot problem?
    F37 cannot be booted on some old EFI firmware which requires 32 bit shim.
    Fedora versions before F37 have no such problem.

  18. Saravanan

    How to upgrade to this Beta using Software app in Fedora 37?

    • Lex

      You need to enable the prerelease setting using this command ‘gsettings set show-upgrade-prerelease true’

  19. lars martin

    Can anybody confirm:

    AME=”Fedora Linux”
    VERSION=”38 (Workstation Edition Prerelease)”
    PRETTY_NAME=”Fedora Linux 38 (Workstation Edition Prerelease)”
    VARIANT=”Workstation Edition”

    Copr repo for PyCharm owned by phracek 6.5 kB/s | 3.6 kB 00:00
    Fedora 37 – x86_64 26 kB/s | 18 kB 00:00
    Fedora 37 openh264 (From Cisco) – x86_64 1.9 kB/s | 989 B 00:00
    Fedora Modular 37 – x86_64 27 kB/s | 18 kB 00:00
    Fedora 37 – x86_64 – Updates 11 kB/s | 14 kB 00:01
    Fedora 37 – x86_64 – Updates 819 kB/s | 2.9 MB 00:03
    Fedora Modular 37 – x86_64 – Updates 27 kB/s | 17 kB 00:00
    Fedora 37 – x86_64 – Test Updates 32 kB/s | 12 kB 00:00
    Fedora 37 – x86_64 – Test Updates 3.3 MB/s | 7.4 MB 00:02
    Fedora Modular 37 – x86_64 – Test Updates 24 kB/s | 15 kB 00:00
    Fedora Modular 37 – x86_64 – Test Updates 11 kB/s | 39 kB 00:03
    google-chrome 2.8 kB/s | 1.3 kB 00:00
    Opera packages 15 kB/s | 3.0 kB 00:00
    RPM Fusion for Fedora 37 – Nonfree – NVIDIA Dri 20 kB/s | 6.4 kB 00:00
    RPM Fusion for Fedora 37 – Nonfree – Steam 18 kB/s | 6.5 kB 00:00
    skype (stable) 9.8 kB/s | 2.9 kB 00:00
    Fedora 37 – x86_64 – VirtualBox 2.6 kB/s | 6.9 kB 00:02
    Errors during downloading metadata for repository ‘virtualbox’: broked upgrade or normaly issue?

  20. Aiden


    ” In the graphical software manager app, Flathub packages will only be selected by default when no Fedora package is available. ”

    I’m not a fan of this increasing encroachment of Flathub/Flatpak.

    Try working out from the Flathub site who maintains the builds there and why we should trust them. It’s insane.

  21. Ricardo

    The kernel 6.2.X Not boot on Thinkpad (T14 Gen2 for example) so sad.

    • tsyang

      Hi Ricardo,

      I don’t have a Thinkpad, but I have a Thinkserver TS140.
      I cannot have F38 booted at first. But after I changed/tried some of the BIOS settings, F38 can be booted now.

      Here are what I did to the BIOS settings:
      Under Security menu, change Secure Boot to Disabled.
      Under Startup menu, change CSM to Enabled, then change Boot Priority to UEFI First.

      If your Thinkpad has the similar BIOS settings, you might want to try it.

  22. Cedrick Ansorge

    My graphpical interface goes completely wild after upgrading to ver 6.2.8 (windows are flickering, the symbols in the task bar are intermittently becoming transparent, etc.). I cannot use this version and have reverted back to 6.2.7 where the problem does not occur.

    Device: HP ZBook Power 15.6 inch G9 Mobile Workstation PC
    Firmware: U97 Ver. 01.03.00
    Processor: 2th Gen Intel® Core™ i7-12700H × 20
    Intel® Graphics (ADL GT2)
    Gnome ver 44.
    Windowing System: Wayland

  23. Turkhan

    Clicking on “64-bit image” download buttons does not work for Lab prereleases.

    For instance,


    You don’t have permission to access this resource.

  24. samson

    Anyone notice the cache build up on The 38 is fast? started my computer and left it on idle for an hour, no app running at all, upon coming back, i have 8GB of cache, dropped the cache but still the build up is crazy. anyone with a similar problem. Crazy thing is I can’t play Video without scratches like the ones on CDs because of the same

Comments are Closed

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