From Fedora Project Wiki

(clear 1749086 (resolved for Final))
(remove 1752040 (fixed in Final))
Line 29: Line 29:
== Upgrade issues ==
== Upgrade issues ==
{{Common bugs issue|podman-cgroups2-runc|Podman fails to run containers on upgraded systems (due to use of runc runtime with cgroups v2)|1752040}}
If you upgrade a Fedora system where you have already installed and used podman to Fedora 31, after the upgrade it is likely podman will fail to launch containers any more. This is because on first use of podman in earlier Fedora releases a configuration file is written to the user's home directory which specifies that the {{command|runc}} runtime should be used to launch containers, but at present, {{command|runc}} does not work with version 2 of the kernel ''cgroups'' feature, as included in Fedora 31.
To resolve this issue, if you have not modified it in any other way, you can simply remove the affected file, with {{command|rm ~/.config/containers/libpod.conf}}. If you ''have'' modified the file in some other way, you can edit it and change the {{code|runtime}} setting from {{code|runc}} to {{code|crun}}.
{{Common bugs issue|silverblue-iot-double-entries|On Fedora Silverblue/IoT, the GRUB menu shows duplicate entries}}
{{Common bugs issue|silverblue-iot-double-entries|On Fedora Silverblue/IoT, the GRUB menu shows duplicate entries}}

Revision as of 00:40, 29 October 2019

This page documents common bugs in Fedora 31 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 Fedora 31 release announcement and the Fedora 31 release notes for specific information about changes in Fedora 31 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)

Core system issues

Encrypted system does not resume from hibernation correctly if you wait more than 90 seconds to input encryption password

link to this item - Bugzilla: #1705522

If you install Fedora 31 with the system partitions encrypted, and then use the hibernate (suspend-to-disk) feature, you will be prompted to input the encryption password during system resume. If you wait longer than 90 seconds before inputting the password, the system will not resume from hibernation correctly - instead a fresh boot will be performed and your previous state will be lost.

There is currently no known workaround for this problem besides simply making sure you input the password soon enough to avoid it happening.

Installation issues

Workstation (GNOME) issues

Custom keyboard layout switch key combinations do not work in X11

link to this item - Bugzilla: #1743005

It has been reported that in Fedora 31, if you run GNOME on X11 (not on Wayland) and configure a custom key combination for switching the keyboard layout via GNOME Tweak Tool or direct configuration editing, the custom combination will not work. Custom switcher combos do work in Wayland, and the several pre-defined combos available via the GNOME Control Center do work in both X11 and Wayland. Switching layout via the graphical menu in the top panel also works.

KDE issues

Upgrade issues

On Fedora Silverblue/IoT, the GRUB menu shows duplicate entries

link to this item

Upgrading Fedora Silverblue or Fedora IoT from an older Fedora release to Fedora 31 might result in duplicate GRUB entries at boot time. However, the default boot entry is still the correct one. Hence, updating and rebooting should still work as usual. This is due to both GRUB2 (via blscfg) and ostree-grub2 (via /etc/grub.d/15_ostree) emitting menu entries. However, we cannot yet turn off the latter in favour of pure BLS booting due to a combination of: (1) older systems may have a GRUB2 too old to understand BLS, (2) OSTree systems do not yet have a mechanism for updating bootloader software, and (3) there is no easy way to detect the currently installed GRUB2 version.

We're working on ways to address this. In the meantime, one way to remove the duplicate menu entries is to disable blscfg support by setting GRUB_ENABLE_BLSCFG=false in /etc/default/grub. This will take effect on the next update and reboot.

For more information, see and

Docker package no longer available and will not run by default (due to switch to cgroups v2)

link to this item - Bugzilla: #1757078

Docker package has been removed from the Fedora distribution for Fedora 31. Docker package has been replaced by the upstream package moby-engine, which includes the Docker CLI as well as the Docker Engine. Another alternative is to use the Podman package. Podman is compatible with the Docker CLI. We have also switched the default cgroup for Fedora 31 to V2. The moby-engine package does not support cgroup V2 yet, although Podman does. If you need to run the moby-engine or run the Docker CE package, then you need to switch the system to using cgroup V1, by changing the kernel boot line.

You can use the kernel parameter systemd.unified_cgroup_hierarchy=0,

Edit the kernel args by opening /boot/grub2/grubenv and add systemd.unified_cgroup_hierarchy=0 to the kernelopts line.

ARM issues

Nvidia Jetson TK1 requires nouveau driver to be blacklisted for graphical output

link to this item

Due to an issue with Nouveau on the Nvidia Jetson TK1 you will need to blacklist the driver. To do this before booting the system, mount the installation media and edit the "/etc/extlinux.conf" file adding 'rd.driver.blacklist=nouveau' to the kernel parameters (line that begins with append).

Etnaviv on imx.6 requires CMA adjustment for graphical output

link to this item

To use the Etnaviv driver on imx.6 based boards you will need to make a small adjustment to the kernel parameters to fix CMA memory allocation issues. To do this before booting the system, mount the installation media and edit the "/etc/extlinux.conf" changing "cma=256MB" to "cma=256M@2G". Fixed in a recent upstream kernel commit.

Low memory systems

link to this item

Systems with low memory (less than 512MB) may run out of memory when running some applications- most notably dnf. To workaround this, stop and disable the zram service "systemctl stop zram; systemctl disable zram; swapoff /dev/zram0". It is then recommended you create a swap file to use in its place.

AArch64 issues

Some AArch64 systems may boot with iommu/arm-smmu errors using Device Tree

link to this item - Bugzilla: #1724276

Some Enterprise AArch64 systems may boot with iommu/arm-smmu errors when booting using device tree (the fedora default). It is recommended to boot these systems using ACPI by adding "acpi=force" to the kernel parameters. If you would like to use device tree you can work around this issue by adding "arm-smmu.disable_bypass=n". This should be fixed in a system firmware update.

Other software issues