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, do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.
Read the F32 Beta release announcement 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)
Workstation (GNOME) issues
In Fedora Workstation, the shutdown/reboot menu is intended to alert you if system updates are prepared for installation and offer you the option of installing them before shutting down. This worked as intended in Fedora 28 and earlier. However, in Fedora 29 and later, a change to suspend PackageKit when it is not needed broke this feature: the notification almost never appears in the shutdown/reboot menu (it will only pop up if you happen to try and shut down very shortly after actively using PackageKit somehow).
There is no known practical workaround for this issue at present.
KDE has wrong desktop background
KDE live boots and installs of Fedora 32 Beta do not have the correct desktop background. Instead, the upstream 'Next' background is used. The correct background is used on the login screen and lock screen, and the desktop background can be changed by right-clicking, selecting 'Desktop settings', and selecting the 'Fedora 32' theme.
We worked out the cause of this problem shortly before the Beta release, but there was a complication with implementing the fix and this meant we did not have sufficient time to include it in the Beta. It will be fixed soon after Beta release, and hence in the Final release. However, the update will not fix the problem for any user account created before it is installed; for any such accounts, the correct background must be chosen manually (as explained above).
mDNS (multicast DNS) breaks on upgrade to Fedora 32
The 'multicast DNS' feature enabled by default on Fedora, which allows you to reach another machine on the local network under the name
/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
We are investigating the cause of this problem and aim to resolve it before the Fedora 32 final release.
Other software issues
Trying to scroll with mouse wheel in inactive Firefox window results in back/forward instead
When using the Wayland backend for Firefox, a known issue in GTK+ means that the modifier key is still considered active in Firefox after you switch away from the window using the + 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 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 toin Firefox and setting the value to 1 instead of 2. 1 sets the action when holding and scrolling the wheel to be the same as when scrolling the wheel normally (it will scroll the page).