From Fedora Project Wiki

(3rd-party-apps-missing|Some 3rd party apps might be missing in GNOME Software initially|2016510)
(gis-wireless-keyboard|Wireless keyboards might not work in GNOME Initial Setup on aarch64|2017043)
Line 82: Line 82:
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 '{{code|1=echo "blacklist vc4" >> /etc/modprobe.d/blacklist-vc4.conf}}'.
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 '{{code|1=echo "blacklist vc4" >> /etc/modprobe.d/blacklist-vc4.conf}}'.


{{Common bugs issue|gis-wireless-keyboard|Wireless keyboards might not work in GNOME Initial Setup on aarch64|2017043}}
If you install Workstation on aarch64, there's an Initial Setup presented to you during the first boot, where you configure system basics and create a user. However, this dialog seems to not accept input from (certain?) wireless keyboards. The only known workaround currently is to connect a wired keyboard.


== Virtualization issues ==
== Virtualization issues ==

Revision as of 15:12, 1 November 2021

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.

Note.png
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.


Upgrade 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                                                                                   


Workstation issues

"Fedora Flathub Selection" third-party repository can't be easily enabled, if you don't enable it initially

link to this item - Bugzilla: #2011274

When you install Fedora 35 or upgrade to Fedora 35, if you don't opt-in to Fedora Third-party repositories initially (during the first boot after the installation, or from an info bar in GNOME Software after an upgrade), you are supposed to be able to opt-in through the GNOME Software repositories dialog later. However, the "Fedora Flathub Selection" third-party repository will not be visible there, so cannot be enabled. As a workaround, from the command line, run:

sudo fedora-third-party disable
sudo fedora-third-party enable

This will result in all third-party repositories being created and enabled. You can disable any repositories you don't want through the GNOME Software repositories dialog.

Some 3rd party apps might be missing in GNOME Software initially

link to this item - Bugzilla: #2016510

If you enabled 3rd party repositories during a fresh system install, some 3rd party applications from those repositories might be missing in GNOME Software initially (this is a race condition, happens only sometimes). The best way to force GNOME Software to refresh all repositories and repopulate the search results is to go to its Updates tab and click the refresh arrow in the top left corner. After this is complete, all available applications should show up in the search results.

Disabling camera/microphone access in GNOME Settings doesn't disable either

link to this item - Bugzilla: #2018158

If you use GNOME Settings to disable camera and/or microphone access in the Privacy tab, the setting doesn't have the desired effect and applications can still use your camera and microphone. This has been broken for a long time. There is currently no known workaround for this.

Hyperlinks are truncated in GNOME Calendar

link to this item - Bugzilla: #2009451

If you use GNOME Calendar to view your events, and there's a hyperlink in that calendar event, it might be truncated, depending on its length. Such links then obviously lead to invalid URLs. There's no known workaround for this issue.


KDE issues

In Discover, packages can't be installed&removed, or removed&installed, without Discover restart

link to this item - Bugzilla: #2011774

Idea.png
Update available for testing
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-2021-35e9884fd8

If you install a package in Discover, and then try to remove it, the latter operation will fail with a "Package not found" error. The same problem occurs if you remove a package and then try to install it again. The workaround here is to close and reopen Discover after the first operation, and then the second operation will work as expected.

Configured repositories in Discover jump around in the list

link to this item - Bugzilla: #2011774

Idea.png
Update available for testing
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-2021-35e9884fd8

If you configure your repositories using Discover, the enabled/disabled repos (and some other related ones) will immediately jump to the bottom of the list, which can be quite confusing. So if you perform multiple operations, read carefully what you click on, because the list keeps re-organizing itself after each action.


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'.

Wireless keyboards might not work in GNOME Initial Setup on aarch64

link to this item - Bugzilla: #2017043

If you install Workstation on aarch64, there's an Initial Setup presented to you during the first boot, where you configure system basics and create a user. However, this dialog seems to not accept input from (certain?) wireless keyboards. The only known workaround currently is to connect a wired keyboard.

Virtualization issues

Mouse cursor position is incorrect if you change display resolution in a virtual machine

link to this item - Bugzilla: #2006746

If you run a virtual machine (VM) and change the internal display resolution of the VM, the mouse cursor position might no longer reflect where you actually see the cursor, and instead get some horizontal and vertical offset (meaning your clicks will be passed to a completely different point of the screen). This only seems to happen after the resolution change is performed during a live session, so if you reboot the machine, the issue should disappear (until you decide to change the VM resolution again). Another workaround is to remove the spice-vdagent package, however that will also mean you'll lose some features, like seamless mouse integration into the VM, or clipboard sharing.

Clipboard is not shared with KDE virtual machines

link to this item - Bugzilla: #2016563

If you run a virtual machine (VM) with the KDE desktop, your host clipboard will not be shared with VM guest. That means text you copy inside your host can't be pasted into the VM, and text you copy inside the VM can't be pasted into the host. One possible workaround is to log out from the current KDE session, select "Desktop Session: Plasma (X11)" at the very bottom of the login screen, and then login again. With an X11 session, this bug will not occur.