This page documents common bugs in Fedora 24 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 F24 general release announcement for specific information about changes in Fedora 24 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
Dual booting Windows fails with 'relocation failed' error on some UEFI systems
link to this item - Bugzilla: #1347291
On some hardware, it's not possible to start Windows (possibly even some other OSes) from GRUB boot menu when booting over UEFI (it does not happen in BIOS mode). The message says error: relocation failed. The problem is still being investigated.
As a workaround, you can use your UEFI boot menu (the one-time boot menu is usually reachable via some hotkey like Esc, F8, F11, F12, etc) to boot Windows, which should work fine.
Advanced users can download and install grub2-2.02-0.25.fc23 (grub2 from Fedora 23), which should immediately fix the problem. However, when using this solution, the broken version of grub2 from Fedora 24 will be offered to you with every new system update, and you'll need to manually exclude it every time.
Windows entry is missing in grub when systems are installed on firmware RAID on UEFI system
link to this item - Bugzilla: #1347273
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 happens only with UEFI. User can use UEFI boot menu as a workaround (the one-time boot menu is usually reachable via some hotkey like Esc, F8, F11, F12, etc).
This bug appears just when UEFI and firmware RAID is used. So BIOS installations and normal disks (or with FW RAID turned off) shouldn't be affected.
Fedora fails to install on some RAID setups
link to this item - Bugzilla: #1333131 - Bugzilla: #1259953
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.
OS X volumes using Apple Core Storage are not recognized by the installer and shrinking them destroys all data
link to this item - Bugzilla: #1033778
The installer appears to support volume shrink for OS X volumes (Apple Core Storage) by offering a Shrink button and sizing slider in Automatic partitioning; and likewise allow numeric resizing in Manual partitioning. However, setting the installer to resize these volumes and proceeding with installation will result in complete data loss of the volume. Resize the volume in OS X's Disk Utility to create free space before proceeding with the installation of Fedora.
Fedora Media Writer shows no writing progress on Fedora 22
link to this item - Bugzilla: #1328462
If you use Fedora Media Writer (formerly liveusb-creator) on Fedora 22 to create a new bootable USB drive, no progress is displayed during the writing process. You need to wait until the dialog says "Finished".
LVM setup on encrypted PVs unrecognized after decryption
link to this item - Bugzilla: #1348688
Due to the issues with the new LVM DBus API, the installation fails to analyze an existing LVM setup on top of encrypted (LUKS) PVs after unlocking the LUKS device(s).
An installer update image has been made available which resolves this issue. To use it, hit e or Tab ⇆ on the installer boot menu to edit the boot options, and add the following: inst.updates=http://vpodzime.fedorapeople.org/1348688_updates.img
This bug doesn't seem to occur with Live images (at least with Workstation Live), only netinst/Server images.
Software RAID (mdraid) from existing Fedora installations not recognized by Workstation/Live edition
link to this item - Bugzilla: #1225184
Installation from Workstation/Live image does not properly recognize existing Software RAID (mdraid) devices (e.g. from an existing Fedora installation). Those devices are listed as "Unknown" (0 bytes size) and cannot be used in the device selection dialogue which makes it effectively impossible to install Fedora 24 or keep existing data.
This bug exists since Fedora 22 (several Bugzilla reports have been filed for this issue but none has been processed yet).
The Server image does not have this problem and it can be used as a workaround to setup a minimal Server, and then install the "Workstation" package group from network remotely (using dnf). The result is not exactly the same and requires some minor additional manual work afterwards. (If anybody knows easier workarounds, please add to this section.)
Non-live install with KDE, or installing KDE post-install, also installs Cinnamon
link to this item - Bugzilla: #1349743
Due to some unfortunate interactions between the Fedora package group definitions and the 
libsolvsudo dnf groupinstall kde-desktop-environment or something similar, you will get KDE...and also Cinnamon.
There is no way to work around this at system install time, besides installing from the KDE live image instead. You would just have to remove the unwanted packages manually. If you are trying to install KDE after initial system install and wish to avoid the unnecessary Cinnamon packages, running sudo dnf install @kde-desktop-environment imsettings-qt should avoid the problem.
Upgrade issues
Rpmfusion packages block Fedora upgrade
At the time of release, rpmfusion packages were blocking Fedora upgrades with a message similar to:
Error: Package a52dec-0.7.4-19.fc24.x86_64.rpm is not signed
This is a third-party repository issue outside of Fedora control. You can read more about possible solutions in this blog post. The repository maintainers are supposedly working on signing their repo, so that the issue disappears in the future. As of recently (mid-July) this has been fixed and RPMFusion packages are signed.
Upgrade from Fedora 24 fails if 
dnf-plugin-system-upgrade
dnf-plugin-system-upgradelink to this item - Bugzilla: #1395686
When upgrading from Fedora 24, it is possible to be in a situation where upgrade preparation - the dnf system-upgrade download step - works, but the actual upgrade - the dnf system-upgrade reboot step - does not. This occurs if you have the
If you encounter this issue, when you try the upgrade step, the system will start booting, but then appear to stall. If you hit Esc, you may see a message Reached target System Update. No progress information on the upgrade will appear.
To be absolutely sure this is the issue you are encountering, please leave the system for a long time - say, two or three hours - to ensure it is not just upgrading silently, as rebooting in the middle of an upgrade can cause the system to be entirely unusable.
But if there definitely appears to be no activity after several hours, shut the system down. Now either boot up and add rd.break to the boot parameters, boot the 'Rescue mode' from a Fedora install image, or boot from a live image. From the installed system root, remove the file /system-update. Now you should be able to boot the system normally again. Now install the package
Core system issues
DNF might remove essential system packages if you used PackageKit (GNOME Software, KDE Apper) in the past
link to this item - Bugzilla: #1259865
There was an unfortunate situation in the past few Fedora releases where PackageKit and DNF didn't work well together. If you installed something via PackageKit (used by GNOME Software or KDE Apper), it didn't mark such packages as "user installed" in the DNF database (which is used to differentiate user-requested packages from other packages installed purely as a dependency, but not explicitly requested by the user). Similarly, if you updated your system using PackageKit (GNOME offline updates, Apper), it erased such "user installed" flags from all updated packages. DNF then tries to remove any unnecessary packages during its next transaction (or when specifically asked using sudo dnf autoremove). This might lead to removing core system packages because DNF no longer sees them as "user installed" and considers them a no-longer-needed dependency. It is also possible that this might happen to you when performing a system upgrade to Fedora 24.
This is now fixed in Fedora 24 (since libhif-0.2.2-3.fc24) and Fedora 23 (since libhif-0.2.2-3.fc23). Future use of PackageKit (GNOME Software, Apper) should be safe. However, if you have ever used these tools in the past, you're strongly advised to fix your "user installed" database before you start using DNF:
- First, make sure your libhif package version is the same as described above or newer:
rpm -q libhif
If not, update it, and check again:
sudo dnf --refresh update libhif
Reboot after update. - Then, mark all your current packages as "user installed" using this command:
rpm -qa --qf '%{NAME}\n' | xargs sudo dnf mark install
Please note that this solution is slightly excessive, because you're going to end up with all your packages considered either system essential or user requested, and none of them is ever going to be removed as a no-longer-needed dependency. However, this is the only way to be absolutely sure that you're not going to be affected by this issue, at a relatively small cost (some packages might stay on your disk unnecessarily). Power users can tweak this solution according to their needs.
X crashes when systemd-udev package updated on systems with multiple graphics adapters (hybrid graphics)
link to this item - Bugzilla: #1341327 - Bugzilla: #1378974
If your system has multiple graphics adapters - the most common case being laptop 'hybrid graphics' (NVIDIA Optimus or AMD 'Dynamic Switchable Graphics') - and you update the systemd-udev package while X is running, it is highly likely that X will crash.
This may be a severe problem if you were running the update process inside of X (e.g. from a terminal app within your desktop). The X crash will kill the update process before the update has properly completed. This may leave you with inconsistencies in the package database, which can be difficult to recover from, and cause various other consequences (these will vary depending on which parts of the update process were not completed before the crash).
The crash is triggered when the systemd-udev-trigger.service service is restarted, so any other action which results in that happening may also cause X to crash on affected systems.
We strongly advise against running updates from a terminal window inside a graphical desktop. We advise against this in any case, but obviously there is a specific and severe reason to avoid it in this case. The safest way to apply updates on Fedora is using the 'offline updates' system, which applies updates by rebooting to a minimal environment, installing the updates, then rebooting to the usual environment.
If you update from the GNOME Software application on Fedora Workstation (GNOME), or by clicking on the 'reboot to install updates' notifications which are shown automatically from time to time on Workstation, you are using the 'offline updates' system and will not be affected by this bug.
On other desktops or non-graphical installs, you can use the offline updates system as follows:
sudo pkcon refresh force && \ sudo pkcon update --only-download && \ sudo pkcon offline-trigger && \ sudo systemctl reboot
If you do not want to use the offline update system, we strongly advise you at least update from a VT, instead of from a terminal app in a graphical desktop. That is, press ctrl-alt-f3 to get a console login prompt, log in, and run the update from the console. If you leave X running while the update runs on an affected system, it will still crash when the systemd-udev package is updated, but the update process will not crash (as it is not running in X) and will complete properly.
An update to resolve this particular issue will be available soon, but due to the technical details of exactly how the bug is triggered, the update process that applies the fix will still be vulnerable to the bug. The fix can only prevent subsequent updates involving the systemd-udev package from triggering the bug.
GNOME issues
Offline updates in GNOME stop working after Google Chrome is installed
link to this item - Bugzilla: #1344643
If you install Google Chrome, it tries but fails to install a GPG key for its repository. This will break "offline update" functionality in GNOME Software (in this mode the updates are installed during a system reboot). Once a new google-chrome update is released, all future updates using GNOME Software will fail (including system updates unrelated to google-chrome, it's enough that the new google-chrome package is in the update set). This is not a problem for DNF, which will ask you to confirm the GPG key during the next google-chrome update.
In order to work around this, you need to confirm the GPG key for the google-chrome repo. You can do it using DNF, once a new google-chrome update is available. Simply update chrome using DNF and confirm the gpg key question:
$ sudo dnf update 'google-chrome*'
Alternatively, you can download the key and import it into RPM database (in this case you don't need to wait until new google-chrome update is available):
$ curl -O 'https://dl.google.com/linux/linux_signing_key.pub' $ sudo rpmkeys --import ./linux_signing_key.pub
After this, offline updates using GNOME Software should start working again.
Network configuration changes not always applies in GNOME control center
link to this item - Bugzilla: #1344788
In GNOME settings (control-center), network changes may not take effect for a connection using the Apply button - the configuration is not reloaded. Turn the connection off then back on again to reload the settings.
One of the affected options is "Use this connection only for resources on its network". This can be used for example when someone wants to make wireless connection default and still connect via wired connection for local resources.
Plasma (KDE) issues
Plasma crashes when switching users in VMs using QXL driver
link to this item - Bugzilla: #1293167
If you try to switch between different user accounts in Plasma while running in a virtual machine using the QXL driver, Plasma is likely to crash. This doesn't seem to happen when using a different video driver. It also doesn't affect bare metal machines (because those don't use QXL). The workaround is to use a different video driver in your VM.
Network issues
Hardware issues
Application issues
Firefox no longer plays H264 content using gstreamer, uses ffmpeg now
link to this item - Bugzilla: #1331496
Since Firefox 46, it no longer uses gstreamer to play non-free multimedia content (most often represented by H264 video codec), but uses ffmpeg instead. Instead of having gstreamer1-libav, now you need to have ffmpeg-libs installed if you want to be able to play such content in Firefox. Please note that ffmpeg is not distributed by Fedora and you need to obtain it yourself, if you wish to use it.
Docker fails to run anything if docker-1.10.3-3 was ever used
link to this item - Bugzilla: #1322909
There has been reported an issue with docker-1.10.3-3, which results in unusable docker. This issue persists even if docker is updated. Sufficient workaround should be to stop docker, remove directory /var/lib/docker and install newer docker. Users with lvm thin pool must recreate the pool since the removal of /var/lib/docker breaks it. For more, see RHBZ 1322909#c21.
ARM issues
bananapi: unable to pxe boot
link to this item - Bugzilla: #1329613
Some people are experiencing a problem with graphical PXE installation on Banana Pi. They are probably running into memory issues when 1G of RAM is not enough. The workaround is to append inst.text to kernel cmdline and proceed with text installation or install the system via VNC.
Fedora Server issues
FreeIPA fails to start after upgrade if initially installed with Fedora 21 or earlier
link to this item - Bugzilla: #1323400
Between Fedora 21 and Fedora 22, FreeIPA was changed from using a file-based store for certificate profiles to a database store. Any FreeIPA server initially deployed under Fedora 21 or earlier would have had the file store, and would need to be migrated to the database store on upgrade to Fedora 22 or later.
Testing indicates that this migration was often not correctly performed on upgrade. With versions of
An update that fixes the upgrade migration process is available. If you have a server which was initially deployed with Fedora 21 or earlier and you have not yet upgraded to Fedora 22 or later, please either wait for the update to be released, or ensure it is included in the upgrade by enabling the updates-testing repository during upgrade or in some other way, to ensure the migration works correctly.
If you already hit this bug during upgrade, updating the package will not fix it. The symptom of this bug is that the pki-tomcatd@pki-tomcat.service service fails to start during FreeIPA initialization. If you run ipactl -d, you will see it repeatedly attempt to connection to https://(serverhostname):8443/ca/admin/ca/getStatus for some time, failing each time, then eventually time out.
If you are affected by the bug, first apply the update: run sudo dnf install yum, then sudo yum-deprecated --enablerepo=updates-testing update --advisory=FEDORA-2016-4d226a5f7e. Then, edit the file /etc/pki/pki-tomcat/ca/CS.cfg and replace the text subsystem.1.class=com.netscape.cmscore.profile.LDAPProfileSubsystem with subsystem.1.class=com.netscape.cmscore.profile.ProfileSubsystem. Finally, run sudo ipa-server-upgrade. This should correctly perform the migration, and FreeIPA should subsequently start correctly.
Fedora Cloud issues
Other issues
Hibernation doesn't work from a standard install
link to this item - Bugzilla: #1206936
The systemd-hibernate generator used to handle resume from hibernate functionality expects a resume=/path/to/swap in the kernel args. Anaconda does not add this into /etc/default/grub and the dracut cmdline generator doesn't act in a way the systemd hibernate generator can locate the swap with the resume image.
To work around this, check the devmapper path to the swap via swapon -s command and add it to the GRUB_CMDLINE_LINUX entry in /etc/default/grub, then regenerate the grub.cfg file used:
- Via grub2-mkconfig:
- For BIOS systems:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
- For EFI systems:
sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
- For BIOS systems:
- Via grubby:
sudo grubby --args=resume=/path/to/swap --update-kernel=$(grubby --default-kernel)