This page documents common bugs in Fedora 26 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.
- 1 My bug is not listed
- 2 Installation issues
- 2.1 Switching keyboard layout with key combo does not work in Wayland
- 2.2 Disk initialization in installer can take a very long time if large ext filesystems are present
- 2.3 Windows entry is missing in grub when systems are installed on firmware RAID on UEFI system
- 2.4 Fedora fails to install on some RAID setups
- 2.5 Installer on several live images does not offer iSCSI support
- 2.6 32-bit installer incorrectly calculates space that will be freed when removing devices
- 3 Upgrade issues
- 4 Core system issues
- 5 GNOME issues
- 6 Plasma (KDE) issues
- 7 Network issues
- 8 Hardware issues
- 9 Application issues
- 10 ARM issues
- 11 Fedora Server issues
- 12 Fedora Cloud issues
- 13 Fedora Atomic issues
- 14 Other issues
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)
Switching keyboard layout with key combo does not work in Wayland
If you're running Workstation Live install media and configure multiple languages in the installer, you won't be able to switch between them using the standard system shortcut (typically+ or + ). However, you can still click on the language indicator in the installer with the mouse and that will switch the languages.
This does not affect other install media (KDE Live, DVD and netinst images).
Disk initialization in installer can take a very long time if large ext filesystems are present
When checking existing disks prior to installation, the installer runs an(filesystem consistency check) on all ext2/3/4 filesystems. For large (1TB+) filesystems, this can take hours to finish. There is no obvious indicator that this is occurring, but if you know your system has large ext filesystems and the installer pauses for a long time when starting up, this is likely the cause.
Windows entry is missing in grub when systems are installed on firmware RAID on UEFI system
When Fedora is installed beside Windows on the firmware RAID and on UEFI it could happen that there will be Windows entry missing in grub menu.
This bug occurs only when UEFI and firmware RAID are used, so BIOS installations and normal disks (or with FW RAID turned off) shouldn't be affected. In most cases, you can use the UEFI boot menu as a workaround. Different systems (different firmwares, in fact) offer access to the UEFI boot menu in different ways, so we cannot provide exact instructions, but often a one-time boot menu is reachable via some hotkey like, , , at boot time. The UEFI boot menu should offer an option to boot Windows or Fedora.
Fedora fails to install on some RAID setups
On some setups, installing Fedora over existing firmware or software RAID can cause anaconda to crash.
- If you try to create a RAID array during setup on a system that has an existing RAID configuration using the drives from that previous RAID array, the newly-created one gets produced incorrectly and is unusable (and of course, the one you deleted is no longer there). User can restart and try again on the same selected drives (this time using free space) as workaround.
- The installer might crash on startup with certain non-intel firmware RAIDs. No further details are known at the moment.
Installer on several live images does not offer iSCSI support
On many or all of the Fedora 26 Alpha live images, the installer will not offer iSCSI functionality (the "Add iSCSI target" button will not appear in the 'Specialized & Network Disks' screen). You can avoid the problem by running
sudo dnf install storaged-iscsi from a console before starting the install process, or by installing from a dedicated installer image rather than a live image.
32-bit installer incorrectly calculates space that will be freed when removing devices
If you use a 32-bit Fedora 26 image and attempt to free up space for an installation by deleting filesystems or other storage devices, you may find that the installer incorrectly calculates the space that will be freed and refuses to proceed as it does not believe sufficient space will be available.
To work around this, you can remove the devices with some other tool (e.g.
parted) from a live or rescue environment before running the installer.
Please remember that i686 is no longer a release-blocking architecture for Fedora (since Fedora 24). We recommend the use of x86_64 wherever possible.