This page documents common bugs in Fedora 34 and, if available, fixes or workarounds for these problems. If you find your problem in this page, do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.
- 1 Release Notes
- 2 My bug is not listed
- 3 KDE issues
- 4 Upgrade issues
- 5 ARM and AArch64 issues
- 6 IoT Edition
Read the F34 Beta release announcement for specific information about changes in Fedora 34 and other general information.
My bug is not listed
Not every bug is listed in this page, but Bugzilla should be a comprehensive database of known bugs. This page is a sampling of the bugs most commonly discussed on our mailing lists and forums.
To see if your bug has already been reported, you can search Bugzilla. If it has not yet been reported, we encourage you to do so to help improve Fedora for yourself and others. A guide to Bugs and feature requests has been prepared to assist you.
If you believe an already-reported bug report should be added to this page because it is commonly encountered, you can:
- Add it yourself, if you have wiki access. Common bugs instructions provides guidance on how to add an entry to the page correctly, but the most important thing is to make sure that the bug is listed - don't worry if you don't get the format quite right, we can clean it up later.
- Or, add the CommonBugs keyword to the bug report. Someone from the QA team will then inspect the issue to determine whether the bug should be listed as a common bug. To expedite your request, please add a comment to the bug that includes
- a summary of the problem
- any known workarounds
- an assessment on the impact to Fedora users
For reference, you can query Bugzilla for bugs tagged CommonBugs:
- CommonBugs? (bugs with CommonBugs keyword, but do not yet have a link to this page)
- CommonBugs+(bugs with CommonBugs keyword and contain a link to this page)
KDE live image shows update notifications
The Fedora 34 Beta KDE live image will notify you of available updates while running in live mode. Please do not respond to these notifications and install the updates, it is generally not a good idea to try and update the live system and may cause your session to crash or hang. Please only update installed systems.
Upgrade to Fedora 34 may fail if i686 rdma-core package installed
If you try to upgrade to Fedora 34 with the
i686 package installed, the upgrade may fail with errors relating to that package. The i686 version of the package needs to be removed on upgrade to Fedora 34, but due to limitations in RPM we cannot make this happen automatically in all cases. If you encounter this issue, you can try using the argument for the upgrade; it should cause the upgrade to remove the package. Please do check it does not result in any other desired package being selected for removal.
Audio may not work after upgrade to Fedora 34 if pipewire was previously installed
Some users have reported that pipewire (the default audio framework in Fedora 34) may not work properly on update from older versions due to a configuration file format incompatibility. If you had pipewire installed in Fedora 32 or 33, it may stop working on upgrade to Fedora 34. If this happens to you, we recommend moving all
*.conf files out of
/etc/pipewire and reinstalling pipewire with
sudo dnf reinstall pipewire. You will then need to re-apply any customizations you had made to the configuration files.
ARM and AArch64 issues
Console output not shown on monitor during boot on AArch64
During system boot on AArch64, console output is not shown on the monitor even if one is connected unless
is installed by default with graphical desktop package sets, but not with non-graphical package sets like minimal or Fedora Server. Notably, if you have an encrypted system partition, the prompt to decrypt it will be sent to the serial console, not shown on the monitor. To work around this, you can install
- if necessary via a kickstart or before rebooting from the installer - or use the serial console.
Raspberry Pi 3 series systems boot very slowly
Due to a bug in uboot, Raspberry Pi 3 series devices may boot Fedora 34 Beta very slowly and report several "failed to come online" errors; the bug is indeed that uboot fails to bring CPU cores beyond the first online, and this causes the slowness as a single core has to handle the entire boot process.
An update has been issued that resolves this problem, but it did not quite make the Beta release. To resolve the problem after initial deployment, ensure you have the updated uboot-tools installed, then run
Raspberry Pi 4 will not start without being connected to a monitor
An HDMI monitor must be connected to the Raspberry Pi 4 to boot successfully. To boot headless after completing initial-setup, add
Boot failure after installing grub2-2.06~rc1-1.fc34
After installing the latest
, upgrades and package installations may fail to list any IoT ostree deployments in the grub menu, and only list a system firmware option. This is due to a small typo in the grub.cfg. To work around the issue look for the following line in
search --no-floppy --fs-uuid --set=root 5EB5-588D
And change to:
search --no-floppy --fs-uuid --set=boot 5EB5-588D
Note, change "--set=root" to "--set=boot". The UUID (5EB5-588D) may differ on your local system.