Common F31 bugs

Click here to set up this language box

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, 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 31 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 31 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 F31 Beta release announcement 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

Custom network configuration passed to the installer via kernel arguments not passed to installed system

link to this item - Bugzilla: #1727904

When installing Fedora, it is possible to specify custom network configuration via kernel arguments. Indeed, if you need to retrieve a kickstart, updates image or the installer environment itself via a network connection, but that network connection requires manual configuration, this is the only way to do it. Normally, when you do this, the network connection is automatically translated into a NetworkManager configuration file and included with the installed system. However, in Fedora 31 Beta that mechanism is broken, so if you only pass the custom configuration via kernel arguments, the installed system will not have it. It will instead attempt to use DHCP to bring up any physically connected network interfaces, as a typical Fedora installation does.

If you must ensure that the custom network configuration is immediately present on the installed system, then as well as passing it via kernel arguments, you should also specify it either in the kickstart (if installing via kickstart) or interactively in the installer (if performing an interactive installation). This should ensure that the configuration is also written to the installed system.

Workstation (GNOME) issues

GNOME Printers settings app can crash if you enter a typo when searching for a printer

link to this item - Bugzilla: #1750394

It has been reported that the GNOME Printers settings applet (accessible directly or via the Control Center) may crash if you enter a typo when searching for a printer, e.g. socket> instead of socket:. If you observe this applet crash unexpectedly, this may be the cause, so you may be able to avoid the problem by retrying and typing correctly.

Copy and paste and other agent features do not work with a SPICE-based virtual machine running Workstation

link to this item - Bugzilla: #1750120

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.

A tool called spice-vdagent is run automatically in SPICE-based virtual machines (e.g. those run by virt-manager or GNOME Boxes, usually) to enable features like copying and pasting from the host system into the virtual machine, and vice versa. In Fedora 31 Beta, this tool does not run correctly in GNOME, so all features enabled by the agent will not work. The update referenced above fixes this bug, but it was not included in the Beta release, so you will still encounter this bug when booting the Beta Workstation live image in a virtual machine. The bug will be resolved in future nightly live images, and in the Final live images.

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

Fedora 31 desktop background not used in KDE

link to this item - Bugzilla: #1749086

Update available for testing
A candidate fix for this issue has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, run this command: sudo dnf --enablerepo=updates-testing update --advisory=FEDORA-2019-d7fbbec3ae

Fedora 31 Beta contains a bug which results in the wrong desktop background being used by default in KDE. It is not a Fedora background at all, in fact, but an upstream background called "Next". The update listed above will fix this bug, but only for users created after the update is installed. If you install using the Fedora 31 Beta KDE live image (or another KDE image from before the bug is resolved) and create a user before updating, the user's background will be set to the 'wrong' one and this will not be changed automatically when updating. You can easily switch to the correct background for affected user accounts in the KDE settings (or, of course, any other background you might prefer). This issue will be resolved for future nightly images and for the Final release.

Upgrade issues

Podman fails to run containers on upgraded systems (due to use of runc runtime with cgroups v2)

link to this item - Bugzilla: #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 runc runtime should be used to launch containers, but at present, 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 rm ~/.config/containers/libpod.conf. If you have modified the file in some other way, you can edit it and change the runtime setting from runc to crun.

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 https://github.com/ostreedev/ostree/pull/1929 and https://discussion.fedoraproject.org/t/boot-entries-gone-after-upgrade/8026.

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 arguments (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 arguments 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=XXX" to "CMA=256M@2G".

Systems with less than 512M RAM

link to this item

Systems with less than 512M RAM 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 with Device Tree

link to this item - Bugzilla: #1724276

Some Enterprise AArch64 systems may boot with iommu/arm-smmu errors when booting with device tree (the fedora default). It is recommended to boot these systems using ACPI by adding "acpi=force" to the kernel arguments. 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 firmware by the system vendor.