Common F34 bugs

Click here to set up this language box

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.

Pre-release version
Fedora 34 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 34 pre-releases. Issues that are fixed will be removed from the page once a fix is available (for instance, an issue that affects the Beta but is fixed in the final release will be removed at the time of that release).

Release Notes

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
  1. a summary of the problem
  2. any known workarounds
  3. 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)

Upgrade issues

Upgrade to Fedora 34 may fail if i686 rdma-core package installed

link to this item - Bugzilla: #1919864

If you try to upgrade to Fedora 34 with the rdma-core 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 --allowerasing 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.

ARM and AArch64 issues

Console output not shown on monitor during boot on AArch64

link to this item - Bugzilla: #1940163

During system boot on AArch64, console output is not shown on the monitor even if one is connected unless plymouth is installed. plymouth 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 plymouth - if necessary via a kickstart or before rebooting from the installer - or use the serial console.

IoT Edition

Boot failure after installing grub2-2.06~rc1-1.fc34

link to this item - Bugzilla: #1940524

After installing the latest grub2, 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 line:

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.