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.
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
- 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)
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
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.
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.
Other software issues
Dnfdragora shows spurious "DNF is locked by another process" error after successful update
link to this item - Bugzilla: #1750575
It has been reported that the Dnfdragora package manager used on several desktops in Fedora 31 shows a spurious error message "DNF is locked by another process. dnfdragora will exit." after successfully updating the system. Please rest assured that there are no further consequences and this message can simply be safely ignored.