Common F35 bugs

Click here to set up this language box

This page documents common bugs in Fedora Linux 35 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 Linux 35 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 35 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 F35 Beta release announcement for specific information about changes in Fedora Linux 35 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)

Installation issues

When using a secondary keyboard layout in the installer, it frequently switches to the primary one

link to this item - Bugzilla: #2016613

This only affects desktop environments running on Wayland session by default (Workstation, KDE). If you boot such a Live image, run the installer, configure multiple keyboard layouts, and then switch to a secondary layout using the integrated layout switcher, the keyboard layout will switch to the primary one immediately after pressing a keyboard modifier such as Shift/Alt/Ctrl. This isn't usually a problem on Workstation, because there's hardly a place where you'd like to use the secondary layout for typing characters. However, for KDE, this is more common, because you need to create a user in KDE's installer, and you might want to use your national alphabet (if configured as a secondary layout) to name it. In this case, you can either name the user differently and rename it after you boot into the installed system, or you can log out from the KDE live session, select "Desktop Session: Plasma (X11)" at the very bottom of the login screen, and then login again as the "Live System User" (no password). With X11 session, this bug will not occur.

Workstation issues

No sound after upgrade

link to this item - Bugzilla: #2016253

In some cases, the new WirePlumber service may not be properly configured to start automatically after an upgrade. WirePlumber is a session manager for PipeWire, the modern audio subsystem we made the default starting with Fedora 34. You can read those links for details, but the short version is "this needs to be running for sound to work". The upgrade process should take care of this, and we expect this to be true for almost everyone. However, if your system is one of the unfortunate exceptions, run the following command from a terminal (not as root or with sudo), and everything should start working:

$ systemctl --user enable --now wireplumber                                                                                   

Server issues

Resolving dnssec-enabled domains may fail after FreeIPA server upgrade to Fedora 35

link to this item - Bugzilla: #1999321

In automated testing of FreeIPA on Fedora 35, we found that upgrading a FreeIPA server with dnssec validation enabled to Fedora 35 may possibly break DNS resolution of hosts in dnssec-enabled domains. This problem occurs in our automated testing environment, but has not yet been successfully replicated outside it, so it may be specific somehow to that environment. However, if after upgrading a FreeIPA server configured to act as a DNS server to Fedora 35 you find that you have problems when resolving hosts in dnssec-enabled domains, you can try disabling dnssec validation on the server:

# ipa-dns-install --disable-dnssec-master

ARM and Aarch64 issues

Raspberry Pi Boards will not start without being connected to a monitor

link to this item - Bugzilla: #1894241

An HDMI monitor must be connected to Raspberry Pi boards to boot successfully. To boot headless after completing initial-setup, add hdmi_force_hotplug=1 to /boot/efi/config.txt. This is due to an upstream regression and will be fixed in a kernel update.

Raspberry Pi 4 GUI frequently locks up with the Workstation Edition

link to this item - Bugzilla: #2008557

While not officially supported in Fedora, the Raspberry Pi 4 works well for most use cases. Unfortunately the upstream vc4 driver frequently locks up when using Wayland on the Workstation image. This is considerably better when using Xorg, but can still be affected by the bug. To workaround this issue you can blacklist the vc4 driver by running the following command 'echo "blacklist vc4" >> /etc/modprobe.d/blacklist-vc4.conf'.