This page documents common bugs in Fedora 32 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 32 release announcement and the Fedora 32 release notes for specific information about changes in Fedora 32 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)
Core system issues
Colored output in DNF is hard to read
link to this item - Bugzilla: #1814563
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-2020-68aa5586edDNF terminal output is now colored in certain cases (e.g. colored search results, package names to be installed, package names to be removed, etc). Depending on your terminal color scheme, some output might be harder to read. There is an update available which should improve the readability considerably.
Package fedora-obsolete-packages is no longer installable, and is removed when upgrading to Fedora 32
link to this item - Bugzilla: #1827398
The behaviour of the special package called 
fedora-obsolete-packages
The package's only purpose is to obsolete packages that were retired and which would otherwise cause dependency resolution problems on upgrades. The package accomplishes this purpose simply by being available in the repositories; it never needs to actually be installed. Any attempt to install this package will end with "Nothing to do" message, but don't worry: this is not an error.
Installation issues
Memtest present on installation media often reboots/freezes
link to this item - Bugzilla: #1811353
Fedora installation media contain a "Run memory test" boot option that runs Memtest tool to check your memory for errors. Due to a bug, this tool often either freezes or reboots almost immediately. It might be particular to just certain hardware, but we have numerous reports of this happening. If you need to check your memory for errors, it's recommended to use a different source to create a Memtest bootable medium, and avoid using Fedora installation media for this.
Workstation (GNOME) issues
Changing default keyboard layout gets reflected during disk decryption only after next kernel update
link to this item - Bugzilla: #1405539
If you change your default keyboard layout in GNOME Settings, it will be changed immediately in your system, but it will not be changed immediately in the disk decryption dialog that is shown during boot (if you use disk encryption). The old keyboard layout will still be used for that disk decryption dialog until a new kernel is installed, only then it will be switched to the newly selected keyboard layout.
KDE issues
User switching/re-logging in KDE might often lead to a black/frozen screen
link to this item - Bugzilla: #1817708
We've identified several issues with user switching in KDE, which might lead to a black/frozen login screen:
- Log out and immediately try to log back in using the same user.
- Switch users (i.e. keep the current session running), and immediately try to log back in using the same user.
- Switch users, log in as a second user, and then log out the second user.
The issue might occur just on certain systems and might depend on timing of your actions.
KDE login screen cannot handle expired passwords
link to this item - Bugzilla: #1819749
If your user password is configured to expire, you will not be able to log in using KDE login screen when it does. The login screen doesn't allow expired password to be changed (renewed). This is not a bug but a missing feature, it's not a regression from the past.
Upgrade issues
mDNS (multicast DNS) breaks on upgrade to Fedora 32
link to this item - Bugzilla: #1811935
The 'multicast DNS' feature enabled by default on Fedora, which allows you to reach another machine on the local network under the name <hostname>.local, breaks when upgrading to Fedora 32 beta. This happens because the /etc/nsswitch.conf file is modified incorrectly during the upgrade process. The problem can be resolved by editing the file manually and changing this line:
hosts: files dns myhostname
back to this:
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
This is resolved in the Fedora 32 final release.
Other software issues
Trying to scroll with mouse wheel in inactive Firefox window results in back/forward instead
link to this item - Bugzilla: #1650051
When using the Wayland backend for Firefox, a known issue in GTK+ means that the Alt modifier key is still considered active in Firefox after you switch away from the window using the Alt+Tab ⇆ shortcut. So if you then move the mouse over the inactive Firefox window (but do not click to activate it) and scroll the wheel, Firefox will treat this as holding down the Alt key and scrolling the wheel. By default, in Firefox, this is mapped to going 'back' and 'forward' in the page history, so instead of the page scrolling, you will rapidly move backwards or forwards through your page history.
If you find yourself frequently triggering this unwanted behaviour, you can work around it by navigating to about:config in Firefox and setting the value mousewheel.with_alt.action to 1 (the integer value one). This sets the action when holding Alt and scrolling the wheel to be the same as when scrolling the wheel normally (it will scroll the page).