This page documents common bugs in Fedora 33 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.
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)
Secure Boot fails to boot F33 Beta image
Booting Fedora 33 with Secure Boot switched on ends with the "Secure Boot Image failed to verify with *ACCESS DENIED* error on computers with updated DBX database (mostly dualboots with Ubuntu). The Ubuntu update prevents Fedora's shim from booting. Ubuntu has already proposed to revert the update, so this issue should not emerge in nearest future, but some computers might have already be affected.
If your computer is affected by this problem, do not switch off Secure Boot but try to clear the Secure Boot keys using your computer's Setup tool. On some computers, a factory reset might be necessary to do it.
Switching off Secure Boot should be the very last option to workaround this issue.
Commands run with sudo use vi as the default editor, not nano
With the Changes/UseNanoByDefault feature in Fedora 33,
nano should be the default editor everywhere. However, if you run
sudo command, and that command launches a text editor, it uses
vi instead of
nano. The reason is that
sudo resets the environment, which includes the
EDITOR environment variable (where
nano is configured). If you want to run such a command using
sudo, but keep using
nano as the default editor, the recommended way to execute it is
sudo -i command.
Switching keyboard layout by Anaconda does not work in mutter (Wayland)
The graphical version of Anaconda runs on Wayland in Fedora Workstation Live image, which causes a situation that the keyboard layouts cannot be switched using a key combo (usually alt+shift). This will happen on system where more keyboard layouts have been added to the system.
The layouts can be switched by using the layout indicator in the upper right corner of the screen.
Default partitioning on Macs creates an extra 600M FAT32 volume that goes unused
On Apple Macs, Automatic and Custom (Manual) partitioning's "Click here to create them automatically" option, will create a spare 600M FAT formatted partitioning that won't be used for anything. You don't need to do anything, the spare partition is harmless. A work around is to perform a completely manual installation (you can find more instructions in the bug report).
Certain systems like Microsoft Surface Go 2 can't boot
Systems like Microsoft Surface Go 2 can't boot the installer or the installed system. The kernel prints
clocksource: Switched to clocksource tsc and freezes. The problem is resolved in
kernel-5.8.16-200. However, if you need to install Fedora 33 on such a system, you either need to wait for unofficial respin of installation media, or install an older version and upgrade.
Login stuck when changing users repeatedly in KDE (log out, log in a different one)
On Fedora 33 KDE, the login screen can freeze when users log in and out repetitively in a sequence.
The reasons why this happens are complex and multi-faceted, and were impossible to resolve entirely for the Fedora 33 release. The situation should be improved in later Fedora releases. To reduce the likelihood of this happening, try to avoid logging out and logging in too quickly. When logging out from a user account, wait at least 10 seconds before you try to log in again (using the same or a different user).
Google account: Credentials have expired
The Google account credentials are reported to have expired, although they have been correctly added and should be working.
This problem is caused by improper unlocking the keyring which might occur with some of the authentication methods, such as autologin or using the CLI passwd to change your user password.
If you experience this bug, do not use autologin and use the GUI method to change your password.
ARM and AArch64 issues
Raspberry Pi 4 will not start without being connected to a monitor
An HDMI monitor must be connected to the Raspberry Pi 4 to boot successfully. To boot headless after completing initial-setup, add
Failed upgrade from Fedora 32 IoT Edition on AArch64
When upgrading from Fedora 32 IoT Edition on AArch64 you may hit an assertion failure with device tree. The upgrade will appear to be successful but on reboot you will still be at the old deployment. To work around this issue run:
rpm-ostree usroverlay && rpm -Uvh https://dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/aarch64/Packages/o/ostree-2020.8-1.fc32.aarch64.rpm https://dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/aarch64/Packages/o/ostree-libs-2020.8-1.fc32.aarch64.rpm systemctl restart rpm-ostreed
dnssec-trigger keys rejected after upgrade from Fedora 32 or earlier
If you run dnssec-trigger on a system that has been upgraded through several Fedora releases, and you upgrade it to Fedora 33 or later, it may fail to start due to keys generated at the time you initially deployed it now being too weak. The system logs will show a "key too small" error for the files
/etc/dnssec-trigger/dnssec_trigger_server.key. To resolve this issue, delete or rename those files, and restart the service:
sudo systemctl restart dnssec-triggerd-keygen.service
Pantheon session does not work at all
At Fedora 33 release time, the Pantheon session did not work at all. There was no known workaround, besides temporarily switching to a different desktop environment, but the update should now have resolved this.
Certain Bluetooth mice don't reconnect on system resume
Some Bluetooth mice didn't reconnect automatically when the system was resumed from sleep. The workaround in GNOME was to open the Bluetooth control panel (search for Bluetooth in GNOME overview, or open Settings -> Bluetooth) and wait a few seconds. This issue didn't affect cleanly booted computers, only computers resumed from sleep.
Reporters of the bug report that it seems to be resolved with updates after November 2020, though it is not clear exactly which update solved the problem.
XFS filesystem on armhfp crashes when running dnf-makecache
The XFS filesystem on armhfp will periodically crash when dnf-makecache runs (it is usually enabled by default as a background service). This usually happens in the background and results in the root filesystem being unmounted. After a new deployment of Fedora 33, before you update to kernel 5.9.11 or higher, we recommend that you stop and disable the service and timer, and delete the contents of
systemctl --now disable dnf-makecache.service systemctl --now disable dnf-makecache.timer rm -rf /var/cache/dnf
Degraded or broken networking on Allwinner SBCs
Some Allwinner SBCs may have degraded or unavailable network due to a bug in the GA kernel (5.8.15-301.fc33). This issue is fixed with the kernel-5.8.17-300.fc33 kernel. There are a number of ways to work around the lack of networking until the update is installed. You can install Fedora 32 or Fedora 33 Beta and then upgrade to Fedora 33 Final (which will install a current kernel from the update repositories), use a USB ethernet dongle just to update the kernel, or use a USB stick to copy the kernel update to the device.