Common F32 bugs: Difference between revisions

Latest revision as of 08:06, 25 June 2020

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
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)

Core system issues

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 has been tweaked in Fedora 32 so that it can no longer be installed. If you currently have it installed, on upgrade to Fedora 32, it will be removed: the packaging system will show it being removed as a "dependent package", which is not really accurate but a limitation of how package removals are calculated. The removal is normal and expected and nothing to worry about.

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

Fedora 32 Workstation (ppc64le) Live image failed to boot

link to this item

Fedora 32 Workstation media for PowerPC 64 LE is known to have an issue with booting up because default kernel and initram are 32-bit instead of 64-bit. The workaround is to edit the grub boot config at Petitboot prompt and replace the ppc with ppc64 for vmlinuz and initrd.img

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.

Fedora Media Writer does not work on macOS 10.15 (Catalina)

link to this item

Fedora Media Writer, the official tool for writing Fedora images to USB stick, is reported to not work with macOS 10.15 (Catalina). It appears to work, but does not actually write anything to the USB stick. There is no known workaround to make FMW work in this scenario at present. Alternative options include running FMW on a Linux or Windows system if you have access to one, using the command-line dd utility instead, or using a third-party tool. One user in the issue thread recommends a tool called Etcher: Fedora has not currently officially reviewed this tool and so cannot officially recommend it, but a cursory review of the tool description suggests it at least ought to write Fedora images correctly.

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

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

Resolved issues

Colored output in DNF is hard to read

link to this item - Bugzilla: #1814563

Fix released
An update has been released to address this problem. After you update your system in your usual way, and possibly reboot, you should no longer be affected by it.

DNF 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. The update tweaked the colors to improve the readability considerably.

@@ Line 1: / Line 1: @@
 <!--
-This header (down to the first "Issues" section below) is generated by '''SUBSTITUTING''' [[Template:Common_bugs_header_prerelease]] at the time of page creation: <nowiki>{{subst:Common_bugs_header_prerelease}}</nowiki>. Please do this rather than copy/pasting. At the time a release goes stable, replace this entire header with a '''SUBSTITUTION''' of [[Template:Common_bugs_header_stable_release]]: <nowiki>{{subst:Common_bugs_header_stable_release}}</nowiki>.If you are making improvements to the header text, please make them also in the [[Template:Common_bugs_header_stable_release]], [[Template:Common_bugs_header_prerelease]] and [[Template:Common_bugs_header_shared]] templates as appropriate, so future pages will contain the same improvements.
+This header (down to the first "Issues" section below) is generated by '''SUBSTITUTING''' [[Template:Common_bugs_header_stable_release]] at the time the release goes stable: <nowiki>{{subst:Common_bugs_header_stable_release<|release=XX>}}</nowiki>. This should replace the entire pre-release header text. Please do this rather than copy/pasting. If you are making improvements to the header text, please make them also in the [[Template:Common_bugs_header_stable_release]], [[Template:Common_bugs_header_prerelease]] and [[Template:Common_bugs_header_shared]] templates as appropriate, so future pages will contain the same improvements.
 -->
 {{autolang|base=yes}}
-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.
+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.
-{{admon/note|Pre-release version|Fedora 32 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 32 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 [https://fedoramagazine.org/announcing-fedora-32/ Fedora 32 release announcement] and the [https://docs.fedoraproject.org/en-US/fedora/f32/release-notes/ Fedora 32 release notes] for specific information about changes in Fedora 32 and other general information.
-== Release Notes ==
+{{Common_bugs_header_shared}}
-Read the [https://fedoramagazine.org/announcing-the-release-of-fedora-32-beta/ F32 Beta release announcement] <!--and the [http://fedorapeople.org/groups/docs/release-notes/en-US/ Fedora {{<includeonly>safesubst:</includeonly>#expr: {{<includeonly>safesubst:</includeonly>CurrentFedoraVersion}} + 1}} Beta Release Notes] <!--[http://docs.fedoraproject.org/en-US/Fedora/{{<includeonly>safesubst:</includeonly>#expr: {{<includeonly>safesubst:</includeonly>CurrentFedoraVersion}} + 1}}/html/Release_Notes/ Fedora {{<includeonly>safesubst:</includeonly>#expr: {{<includeonly>safesubst:</includeonly>CurrentFedoraVersion}} + 1}} release notes]--> for specific information about changes in Fedora 32 and other general information.
+== Core system issues ==
+{{Common bugs issue|fedora-obsolete-packages|Package fedora-obsolete-packages is no longer installable, and is removed when upgrading to Fedora 32|1827398}} <!--#SCRIPTIGNORE# this comment marks issue to be ignored by scripts -->
+The behaviour of the special package called {{package|fedora-obsolete-packages}} has been tweaked in Fedora 32 so that it can no longer be installed. If you currently have it installed, on upgrade to Fedora 32, it will be removed: the packaging system will show it being removed as a "dependent package", which is not really accurate but a limitation of how package removals are calculated. The removal is normal and expected and nothing to worry about.
-{{Common bugs header shared}}
+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 ==
+{{Common bugs issue|f32-workstation-ppc64le-grub-boot|Fedora 32 Workstation (ppc64le) Live image failed to boot}}
+Fedora 32 Workstation media for PowerPC 64 LE is known to have an issue with booting up because default kernel and initram are 32-bit instead of 64-bit. The workaround is to edit the grub boot config at Petitboot prompt and replace the `ppc` with `ppc64` for `vmlinuz` and `initrd.img`
+{{Common bugs issue|memtest-reboots-freezes|Memtest present on installation media often reboots/freezes|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.
+{{Common bugs issue|fmw-macos-catalina|Fedora Media Writer does not work on macOS 10.15 (Catalina)}}
+Fedora Media Writer, the official tool for writing Fedora images to USB stick, is reported to [https://github.com/FedoraQt/MediaWriter/issues/217 not work with macOS 10.15 (Catalina)]. It appears to work, but does not actually write anything to the USB stick. There is no known workaround to make FMW work in this scenario at present. Alternative options include running FMW on a Linux or Windows system if you have access to one, [https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/#_using_a_direct_write_method using the command-line {{command|dd}} utility instead], or using a third-party tool. One user in the issue thread recommends [https://www.balena.io/etcher/ a tool called Etcher]: Fedora has not currently officially reviewed this tool and so cannot officially recommend it, but a cursory review of the tool description suggests it at least ought to write Fedora images correctly.
 == Workstation (GNOME) issues ==
+{{Common bugs issue|keyboard-layout-update-plymouth|Changing default keyboard layout gets reflected during disk decryption only after next kernel update|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 ==
+{{Common bugs issue|kde-user-switching-issues|User switching/re-logging in KDE might often lead to a black/frozen screen|1817708}}
-== Upgrade issues ==
+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.
-{{Common bugs issue|mdns-upgrade-broken|mDNS (multicast DNS) breaks on upgrade to Fedora 32|1811935}}
+The issue might occur just on certain systems and might depend on timing of your actions.
-The 'multicast DNS' feature enabled by default on Fedora, which allows you to reach another machine on the local network under the name {{code|<hostname>.local}}, breaks when upgrading to Fedora 32 beta. This happens because the {{filename|/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:
+{{Common bugs issue|kde-login-expired-passwords|KDE login screen cannot handle expired passwords|1819749}}
- hosts:      files dns myhostname
+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.
-back to this:
+== Upgrade issues ==
- hosts:      files mdns4_minimal [NOTFOUND=return] dns myhostname
-This is resolved in the Fedora 32 final release.
 == Other software issues ==
@@ Line 42: / Line 62: @@
 When using the Wayland backend for Firefox, a [https://gitlab.gnome.org/GNOME/gtk/issues/2112 known issue in GTK+] means that the {{key|Alt}} modifier key is still considered active in Firefox after you switch away from the window using the {{key|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 {{key|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 {{code|about:config}} in Firefox and setting the value {{code|mousewheel.with_alt.action}} to 1 instead of 2. 1 sets the action when holding {{key|Alt}} and scrolling the wheel to be the same as when scrolling the wheel normally (it will scroll the page).
+If you find yourself frequently triggering this unwanted behaviour, you can work around it by navigating to {{code|about:config}} in Firefox and setting the value '''{{code|mousewheel.with_alt.action}}''' to '''{{code|1}}''' (the integer value ''one''). This sets the action when holding {{key|Alt}} and scrolling the wheel to be the same as when scrolling the wheel normally (it will scroll the page).
+== Resolved issues ==
+{{Common bugs issue|dnf-colors-hard-to-read|Colored output in DNF is hard to read|1814563}}
+{{Common bugs update released|FEDORA-2020-68aa5586ed}}
+DNF 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. The update tweaked the colors to improve the readability considerably.
 [[Category:Common bugs]]

Search