Common F23 bugs

In other languages: English (en) español (es) русский (ru) [edit]

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

USB sticks written from Fedora 23 with liveusb-creator (dd mode) and livecd-iso-to-disk do not work

link to this item - Bugzilla: #1264012 - Bugzilla: #1263988

When run from Fedora 23 (or Rawhide), liveusb-creator (in dd mode) and livecd-iso-to-disk fail to create bootable USB sticks (they may boot in UEFI mode). Run from Fedora 22 or earlier (and Windows, for liveusb-creator) they work correctly.

If you need to write a USB stick from Fedora 23 or Rawhide for now, we recommend using the dd method or "Linux (GNOME) quick start (direct write)" documented at How_to_create_and_use_Live_USB.

Media consistency check fails with an error on DVD/netinst

link to this item - Bugzilla: #1250414

If you choose to verify media consistency using appropriate boot menu item when using the DVD or netinst media, you'll shortly see an error and then the boot will continue. You'll not be able to verify whether the image was burned/created correctly.

We recommend at least verifying the downloaded ISO image sha256 checksum to avoid download errors, or using the Live media if you need to be sure that the image was burned correctly.

Media consistency check times out when using optical media

link to this item - Bugzilla: #1250440

If you choose to verify media consistency using appropriate boot menu item when booting from a optical medium (CD/DVD instead of USB stick), the check is very likely to take more than 90 seconds, after which the boot process times out and you're put into an emergency shell. The consistency check still continues and can you wait for it to finish to make sure the medium is burned correctly. But then you'll need to reboot the machine and boot the installer again, this time avoiding "Test this media" boot options.

Installer deletes EFI System Partition even in dual boot scenarios

link to this item - Bugzilla: #1183880

If you have several operating systems installed using UEFI boot (booting from EFI System Partition - ESP) and then go into the manual partitioning screen in the installer and select one of the operating systems to be deleted, the ESP will be deleted as well, even though it is required by the other operating systems.

If you need to perform such installation, don't delete the full partition tree under the to-be-deleted operating system, but delete all of its non-ESP partitions individually and leave ESP intact.

Installer does not correctly compute the minimal required partition size when using network installation

link to this item - Bugzilla: #1224048

If you use the network install image (netinst), the installer will not always correctly warn you when your root partition is too small to contain the installed system. If the disk space runs out during package installation, anaconda reboots the machine without a warning, and the partial Fedora installation is broken and unusable. If this happens, please repeat the installation, but assign more space to the root partiton. For example, the absolute minimum for a Workstation package set is 6 GiB.

In the vast majority of cases, this issue does not affect Live or DVD (offline) installations. There is a very slight chance that if you set the partition to be almost exactly the same size as is the installed package set, the filesystem metadata will occupy enough space so that the installed system does not fit into the free space.

To be safe from this issue, please don't try to set an extremely small root partition.

Filesystems encrypted with passphrases using Cyrillic, Arabic or other switched keyboard layout characters cannot be decrypted at boot time

link to this item - Bugzilla: #681250

If the console keyboard layout for your language is 'switched' (you use a key combination to switch between typing Latin characters, and characters from your language), you will not be able to switch when entering encryption passphrases. Therefore, you will only be able to enter passphrases using whichever layout is the default. Usually, the Latin layout is the default. Therefore, if you are doing an encrypted installation using a language with a switched keyboard layout, we recommend you use only Latin characters in the passphrase.

Plasma (KDE) issues

Initial setup sometimes starts in text mode instead of in graphics mode

link to this item - Bugzilla: #1185447

Sometimes happens that initial setup starts in text mode instead of graphical mode. Furthermode, it seems that text mode does not display properly. You can either reboot a few times, or log into a console and disable initial-setup-text.service by running command sudo systemctl disable initial-setup-text.service and restart. The graphical initial setup should be provided then.

Network issues

No network connection in VM when both host and guest installed from a live image

link to this item - Bugzilla: #1146232

If you install Fedora from a live image, and then create a virtual machine on it and install another Fedora from a live image as a guest, your networking in guest will probably not work. The reason is that libvirt virtual network address ranges are the same both in the host and the guest and clash. This does not happen if you install the libvirt packages in the guest manually at some point later (it is detected during package installation), only when you install from a live image.

If you don't need libvirt to work in the VM, you can remove libvirt networking there by running sudo virsh net-destroy default && sudo virsh net-undefine default, and then renewing the network connection in NetworkManager. If you need libvirt to work in VM, you need to edit its configuration files and assign a different IP range to it.

Hardware issues

The system reboots instead of shutting down

link to this item - Bugzilla: #1257131

On some specific Intel boards the system reboots after a few seconds instead of shutting down. This is related to the XHCI controller and will likely be fixed with newer kernel releases, but for now there is a workaround listed in the bug report to fix this issue.

1263762

link to this item

Fedora 23 Beta testing identified an issue where some 64-bit AMD processors cannot boot 32-bit Fedora 23 Beta kernels. 32-bit AMD CPUs do boot these kernels successfully. This may also affect you if you upgrade a 32-bit install on a 64-bit AMD system to Fedora 23 Beta.

If you are affected by this issue, you can work around it by passing the kernel parameter {{{1}}} or {{{1}}}. If you upgraded from Fedora 22, the Fedora 22 kernel should also still be bootable.

A kernel update should soon be available to fix this, and later Fedora 23 nightly images will include the fix.