From Fedora Project Wiki

Revision as of 00:06, 25 September 2021 by Adamwill (talk | contribs) (Issues updated with commonbugs-update)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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, please do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.

Release Notes

Read the F34 release announcement and the Fedora Linux 34 release notes for specific information about changes in Fedora Linux 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)

Installation issues

Compression not enabled for btrfs subvolumes renamed during install

link to this item - Bugzilla: #1952764

If you use the "custom" partitioning UI during installation of Fedora 34 and change the name of any btrfs subvolume, its line in /etc/fstab will lack the intended compress=zstd:1 mount option. This is benign, affecting only fstab entries, unless the subvolume is mounted as root (/); in this case, the entire installation will lack compression.

If you need to change the root subvolume name, e.g. to "@root", there are two possible workarounds:

Workaround A: change the subvolume name during installation, and then fix /etc/fstab after installation

  1. Change the subvolume name during installation.
  2. (optionally, to enable compression during installation) Immediately after beginning the installation process proper, switch to a shell (ctrl-alt-f2) and run mount -o remount,compress=zstd:1 /mnt/sysimage. If you get an error, you were too fast, the installer hasn't yet mounted the filesystem - simply reissue the command until it returns without error. You can confirm it's enabled with mount | grep btrfs.
  3. Modify /etc/fstab post-install, either before or after rebooting from the install environment.

Workaround B: change the subvolume name change after installation

  1. Proceed with installation without changing the subvolume name.
  2. After installation, change the name of the root subvolume, and update the subvol=(NAME) setting on the appropriate line of /etc/fstab.

NOTE: It is safe to rename actively mounted subvolumes.

Some default keyboard layouts (Russian, Finnish...) not installed when they should be

link to this item - Bugzilla: #1955162 - Bugzilla: #1955793

We have identified a problem with Fedora 34 media which can mean that the expected default console keyboard layout for some languages is not installed. This affects several languages and layouts, including Russian (ru layout) and Finnish (fi layout); it affects any case where the default layout we want to use is in the kbd-legacy package.

When installing from a live image, or from the Server DVD image without the additional remote Fedora repository enabled, the installer will configure the system to use the intended layout, but will not be able to install the kbd-legacy package, because due to an oversight it was left off the install media. This will result in the system using the 'us' console keyboard layout, though it may indicate that the 'ru' or 'fi' (etc.) layout is configured.

If you are able to complete boot and log in using the 'us' layout, please do so, and then install the kbd-legacy package with a graphical package manager or by running sudo dnf install kbd-legacy. If you have encrypted system partitions, you should also run sudo dracut -f to regenerate the initramfs environment, as that is the environment used for partition decryption during boot. This should resolve the issue. If you would like to avoid it at install time, please install from a network install image, or from the Server DVD image but with remote repositories enabled; note that this will still not work for Finnish specifically, as that case suffers from a further bug in the installer.

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.

Audio may not work after upgrade to Fedora 34 if pipewire was previously installed

link to this item - Bugzilla: #1931384

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 pipewire-pulseaudio. You will then need to re-apply any customizations you had made to the configuration files.

Upgrade does not install latest version of iptables, or fails on iptables if --best is used

link to this item - Bugzilla: #1953178

A complex issue involving an attempt to split the iptables package combined with Fedora's package group definitions means that you may encounter problems related to the iptables package when upgrading to Fedora 34, if it is installed and the "Common NetworkManager Submodules" package group is installed.

If you use the --best argument when upgrading - which is usually not necessary, and not recommended in the Upgrading page - the upgrade may fail, complaining it cannot install the "best update candidate". If you do not use --best, the upgrade should not fail, but you may notice it warns about the same thing, and installs an older version of iptables and related packages (1.8.7-3.fc34) rather than the newer versions available from the updates repository.

We are currently considering ways to resolve this issue, but it's actually quite difficult. To work around it, we recommend simply not using --best, allowing the upgrade to proceed and install the 1.8.7-3.fc34 package versions, and then updating again, which should install later versions (and remove the iptables package - it is no longer needed, its functionality is retained in other subpackages).

Another option is to remove the iptables package before upgrade, and yet a third option is to mark the problematic group as not being installed before upgrading, with dnf group mark remove networkmanager-submodules. If you do either of those, the upgrade should manage to upgrade directly to the latest packages.

Workstation issues

GNOME Terminal, large selection can cause a crash

link to this item - Bugzilla: #1929282

When making very large selections in GNOME Terminal, it can crash resulting in the loss of all Terminal instances. Upstream's current workaround is to limit select-all to visible text. Fedora is reverting that workaround, so it's possible very large selections will result in a crash.

KDE issues

Akonadi fails to start after upgrade to Fedora 34, preventing KMail etc. from working correctly

link to this item - Bugzilla: #1953675

It has been reported that after upgrading a KDE system to Fedora 34, the akonadi PIM server may fail to start correctly. This can prevent KMail and other apps that use Akonadi from working.

We are currently investigating this issue, but in the meantime, it has been reported that renaming ~/.config/share/akonadi will allow Akonadi to start up correctly. Of course, this will remove any local configuration that might be set there; you may be able to reapply it from the backup location after Akonadi has started successfully.

ARM and AArch64 issues

Desktop images may require CMA allocation for graphical display

link to this item - Bugzilla: #1934576

Some ARM and AArch64 SBC's (single board computers) may require CMA (Contiguous Memory Allocator) allocation added to the kernel parameters. This can be added with the arm-image-installer by using the --args option or in the grub menu during boot. If required, cma=192M is sufficient for most desktops. Workstation uses a little more with cma=256M recommended.

Application issues

Resolved issues

Constant SELinux alerts if /etc/NetworkManager/VPN exists

link to this item - Bugzilla: #1934725

Fix released
An update has been released to address this problem. After you update your system in your usual way, and possibly reboot, you should no longer be affected by it.

If the directory /etc/NetworkManager/VPN exists on a Fedora 34 system and NetworkManager is enabled, SELinux denials will happen constantly as NetworkManager tries to watch that directory, and SELinux blocks it. The directory is likely to exist if your system began life as Fedora 25 or earlier. In most cases this directory is empty; if so, you can safely remove it, and the denials will stop.

GDM login might fail with the error "fingerprint authentication didn't work"

link to this item - Bugzilla: #1942443

Fix released
An update has been released to address this problem. After you update your system in your usual way, and possibly reboot, you should no longer be affected by it.

After upgrading to Fedora 34, especially on a system that started life as a much older Fedora release (before Fedora 29), or a system where authentication configuration has been locally modified, Workstation users may see a login error message:

Sorry, fingerprint authentication didn't work. Please try again.

The error will appear even if you don't use fingerprint authentication and want to use a regular password instead.

If you upgraded before the fix for this (see above) was released and are stuck, you can switch to a virtual console (e.g. Ctrl+Alt+F3), log in there, and update the system with sudo dnf --refresh update. After this, restart the system, and the bug should be resolved.

With the updated gnome-shell package, you still might see the warnings, but they will not prevent logging in from working. In order to fully resolve the issue and make the warnings go away, it is a good idea to reset your authconfig files to the default state, with sudo authselect select --force sssd with-fingerprint with-silent-lastlog.

Copy/paste between host and Fedora 34 KDE guest using SPICE does not work

link to this item - Bugzilla: #1951580

Fix released
An update has been released to address this problem. After you update your system in your usual way, and possibly reboot, you should no longer be affected by it.

It was reported that when running Fedora 34 KDE in a VM using the SPICE protocol (default for libvirt, virt-manager and Boxes virtualization), copy/paste between the host and the guest - and possibly other features relying on spice-vdagent - did not work.

USB devices forwarded from the host to a guest aren't recognized in a libvirt virtual machine

link to this item - Bugzilla: #1950258

Fix released
An update has been released to address this problem. After you update your system in your usual way, and possibly reboot, you should no longer be affected by it.

If you used a libvirt machine through virt-manager and tried to forward a USB device from the host to a guest (most likely a USB flash drive), the device might not be recognized correctly.