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.
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
- 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)
Installation issues
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 always correctly compute the minimal required partition size
link to this item - Bugzilla: #1224048
The installer uses a set of heuristics to determine the minimal partition size to fit your installation in. Sometimes if you get very unlucky or you intentionally try to get the install partitions as small as possible, the installer might approve the partition size, but the installation fails at the beginning of the installation transaction (after your partitions have been created and formatted) due to insufficient disk size.
To be safe from this issue, please don't try to set an extremely small root partition (or any other system-critical partition, like /usr partition, if you decide to define one). Always plan for at least 500+MB of free disk space on such partitions (of course, in majority of cases you want much much more free space to have your system usable and useful).
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.
Upgrade issues
FreeIPA fails to upgrade properly
link to this item - Bugzilla: #1274905
If you upgrade a system running FreeIPA to Fedora 23, FreeIPA will not start on the upgraded system. The logs will instruct you to run FreeIPA's upgrade process: Upgrade required: please run ipa-server-upgrade command. However, if you run the upgrade script, it will fail, and FreeIPA will still not work.
We strongly advise you do NOT upgrade FreeIPA servers to Fedora 23 until updates are available to fix several known issues in the upgrade process. If you have already updated the system but not yet run the ipa-server-upgrade script, we strongly recommend you do NOT run it yet: it is better to wait for the updates to be released first. If you have already run the upgrade script, you may be able to recover and get FreeIPA working by doing the following:
- Edit
/etc/dirsrv/slapd-(DOMAIN)/schema/99user.ldif - Find the entry (split across three lines) that starts attributeTypes: ( 2.16.840.1.113730.3.8.18.2.3 NAME 'ipaVaultPublicKey'
- Replace it with:
attributeTypes: ( 2.16.840.1.113730.3.8.18.2.3 NAME 'ipaVaultPublicKey' DESC ' IPA vault public key' EQUALITY octetStringMatch SYNTAX 1.3.6.1.4.1.1466.115.1 21.1.40 X-ORIGIN ( 'IPA v4.2' 'user defined' ) )
- Run
pki-server migrate --tomcat 8 - Run
systemctl start pki-tomcatd@pki-tomcat.service - Re-run the upgrade script:
ipa-server-upgrade
However, results may vary, and we strongly recommend waiting for the updated packages to be built, tested and made available.
Certain plymouth themes are problematic during system upgrade
link to this item - Bugzilla: #1267949
Certain plymouth (boot screen) themes are buggy when being inside the system upgrade environment. The known issues are with script and spinner themes - for the first one, the progress information scrolls off the screen soon, for the second one the screen stays black during the whole upgrade. The upgrade itself will execute just fine, but you won't see the progress properly (if this happened to you, do not force-reboot the computer in the middle of the operation, wait for it to finish, it will automatically reboot once the upgrade is done).
There is a fixed version of plymouth to resolve this issue. Even if you have it installed, you still need to execute sudo dracut -f manually to regenerate the ramdisk for your current kernel (or install a new kernel, which will do that automatically for you).
Alternatively, you can revert to the default theme before performing the upgrade:
sudo plymouth-set-default-theme charge sudo dracut -f
Upgrade path for Vagrant broken (rubygem-celluloid retired)
link to this item - Bugzilla: #1275030
The package 
rubygem-celluloid
Core software issues
SELinux denial appears on application crash
link to this item - Bugzilla: #1276305
There is a known issue in Fedora 23's SELinux policy which causes a denial to occur often when an application crashes. It seems SELinux is forbidding the ABRT crash reporting tool from doing something it wants to do to analyze the crash. The denial will be SELinux is preventing abrt-hook-ccpp from using the 'sigchld' accesses on a process. The SELinux maintainers are working on a fix for this problem and it should be available soon.
Initial setup sometimes starts in text mode instead of in graphics mode
link to this item - Bugzilla: #1185447
Sometimes, the initial setup utility that runs on first boot when a user account is not created in the installer starts in text mode instead of graphical mode. This looks a little surprising, but the text mode utility will work correctly and allow you to create a user account if desired, and the login screen should be shown correctly after it is complete.
GNOME issues
Logging out does not work when autologin enabled
link to this item - Bugzilla: #1245953
If you enable autologin in GNOME in Fedora 23, trying to log out will fail to work correctly; instead of returning to the login screen, you will get stuck at a black screen. We are working to fix this issue and an update should be available soon. Until then, we advise not using the autologin function of GNOME.
Initial user creation hands off to login screen (not desktop) and first attempt to log out fails
link to this item - Bugzilla: #1273112 - Bugzilla: #1272706
GNOME includes its own 'first boot' utility,
It appears that there is a timing problem, where gnome-initial-setup creates the logged in desktop session but does not successfully hand off to it, and when you then log in normally and log out, you are sent to the session created by gnome-initial-session.
This problem is a one-time issue and has no further effects. Once you log out a second time, everything will work normally from then on.
Plasma (KDE) issues
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.
Three monitors with an Intel GPU results in instability and display issues
link to this item - Bugzilla: #1275770
Since kernel 4.2, some people with Intel graphics cards have reported issues when they have three (or possibly more) monitors attached. The issues can range from desktop environment crashing, to monitor layout being reset from time to time, or certain monitors not waking up from sleep/locked desktop mode.
If you're affected, you can install and boot an older kernel 4.1 to work around this, or please wait until the issues are fixed in some future kernel update.
ARM issues
Fedora Server issues
Fedora Cloud issues
Atomic images have incorrect permissions on the /tmp directory
link to this item - Bugzilla: #1276775
The permissions of the /tmp dir on Fedora 23 Atomic host images are 755 when they should be 777. This breaks things that want to write to tmp but don't have permissions to. To get around this: chmod 1777 /sysroot/tmp. Updated Atomic host images are expected to be provided regularly for Fedora 23, and this issue should be resolved in those.