This page documents common bugs in Fedora 20 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.
- 1 Release Notes
- 2 My bug is not listed
- 3 Major issues
- 3.1 RPM scriptlets fail during updates
- 3.2 System fails to boot after install using LVM Thin Provisioning
- 3.3 Crash when switching from a complete mirror repository to a DVD-based repository: NoSuchGroup: 3d-printing
- 3.4 389 Directory Server crashes during search operation
- 3.5 /root permissions incorrect on pre-release installations
- 4 Installation issues
- 4.1 Installer crashes with No such file or directory: '/dev/md' if MD-RAID set is referred to by device node name in /etc/fstab
- 4.2 Problem with Installation Source spoke when installing from a partially complete kickstart
- 4.3 Booting previously installed OS (including Windows) from the Fedora bootloader menu may fail after UEFI installation
- 4.4 Network configuration changes made after clicking Configure in installer (nm-connection-editor) are not applied unless interface is turned off and on again
- 4.5 In custom partitioning, cannot change size of a pre-existing LV after setting a mount point for it and scheduling it to be reformatted
- 4.6 In custom partitioning, cannot change size of a pre-existing partition then reset it to initial value
- 4.7 In custom partitioning, cannot change size of a pre-existing LV multiple times then reset it to initial value
- 4.8 Installation crashes during partitioning if disk was scanned after an encrypted volume has already been unlocked
- 4.9 Exiting shell from rescue mode does not return to menu or reboot, but sticks at Pane is dead
- 4.10 Network installation with Authoring and Publishing group selected fails
- 4.11 Installer performs a UEFI native installation even if noefi parameter is specified
- 4.12 UEFI install to ms-dos ('MBR') labelled disk fails with unclear errors
- 4.13 USB stick from which install is running appears as a possible install target
- 4.14 'Selected' state for disks is indicated with a small and easily missed check mark
- 4.15 Bootloader password is required on each boot
- 4.16 Non-GNOME initial setup utility does not warn of failure to create a user account
- 4.17 Kickstart: if no password is specified for a user account, it will be unlocked
- 5 Upgrade issues
- 5.1 Upgrade fails if /var is a separate partition
- 5.2 Upgrade fails with dependency issues if perl-Language-Expr is installed
- 5.3 Fedup: upgrade can't start without rd.luks.uuid/rd.lvm.lv/rd.md.uuid boot args
- 5.4 Upgrading to Tmux 1.9a-2 results in not being able to connect to sessions created previously
- 6 Hardware issues
- 7 Software issues
- 7.1 DVD not available as a package repository after installation
- 7.2 libvirt guests are killed on host shutdown
- 7.3 KVM guests using the qxl graphics driver may display sluggish graphics performance on Fedora 20 hosts
- 7.4 Error messages about swap activation if swap is on a plain partition on a GPT disk
- 7.6 Desktop elements appear too large in GNOME ("high DPI" mode incorrectly enabled)
- 7.7 Crash in speech-dispatcher process when launching GNOME or KDE screen readers
- 7.8 Repeated dbus error messages logged with ModemManager.service disabled
- 7.9 Eclipse crashes with Google Talk plugin installed
- 7.10 ZIP support in PHP
- 7.11 yum reports duplicate packages installed, older version cannot be easily removed
- 7.12 Bluetooth HSP/HFP Profile stops working with upgrade from F19
- 7.13 Text renders fuzzy with Cantarell font (default Gnome font)
- 7.14 rsyslogd consumes 100% CPU time
- 8 Resolved issues
- 8.1 Panorama Stitcher application crashes when launched from system menus in KDE
- 8.2 Multiple cases of "group (groupname) does not exist" errors when running yum
- 8.3 yum groups mark convert command recommended by yum results in many additional packages being installed on yum update
- 8.4 Missing attributes in objectclasses in 389 Directory Server (and hence FreeIPA)
- 8.5 389 Directory Server referential integrity plugin fails to work
- 8.6 389 Directory Server crashes after enabling FreeIPA Active Directory trust support
- 8.7 Upgrade to Fedora 20 with fedup 0.7 fails, reboots shortly after booting the System Upgrade option
- 8.8 Upgrade to Fedora 20 with fedup 0.8 fails due to GPG key problems
- 8.9 Alternative on-screen keyboards do not work correctly in GNOME
- 8.10 Cannot browse / discover SMB/CIFS (Windows, Samba) shares with firewalld enabled
- 8.11 MyPasswordSafe crashes
- 8.12 Disabling SELinux via configuration file failed with libselinux-2.2.1-4.fc20
- 8.13 CUPS hangs on shutdown (causing a long wait on system shutdown) if printer sharing is enabled
- 8.14 ARM: HDMI output and USB peripherals not working on Beagle Bone Black
- 8.15 GNOME Shell crashes after creating a keyring without a password
- 8.16 Sudden inability to unlock screen, or log in to running system (caused by creation of /var/run/nologin)
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. Please follow the style and guidelines explained in the comments in the page source.
- 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 one or more Common Bugs pages)
- CommonBugs+(bugs with CommonBugs keyword and contain a link to one or more Common Bugs pages)
RPM scriptlets fail during updates
A bug in SELinux policy introduced via an update causes RPM scriptlets to fail to execute in Fedora 20 if SELinux is enabled and is in enforcing mode which is the default in Fedora 20.
warning: %post(libkcompactdisc-4.12.1-1.fc20.x86_64) scriptlet failed, exit status 127 Non-fatal POSTIN scriptlet failure in rpm package libkcompactdisc-4.12.1-1.fc20.x86_64
To resolve such problems, run the following commands as root user or using sudo. The first command disables SELinux enforcement for the current session and the subsequent commands expire the yum caching and gets the SELinux policy update which fixes this issue and the last command enables SELinux enforcement back.
# setenforce 0 # yum clean expire-cache # yum update selinux-policy\* # setenforce 1
If you install any packages which failed with scriptlet errors before doing the above procedure, reinstall them using yum reinstall <package name>. If you are unsure of the package names, you can use yum history list to find out the number of the transaction and use yum history undo <transaction number> and then use yum history redo <transaction number> to reinstall the packages.
Fedora SELinux maintainers have a policy of only loosening the policy and typically never tightening it on updates precisely to avoid such kind of problems, however a policy inclusion meant for Rawhide, the development version of Fedora was accidentally included in this release. Fedora SELinux maintainers will be setting up a much higher karma requirement for new updates to avoid similar problems in the future.
System fails to boot after install using LVM Thin Provisioning
Fedora 20 introduces install-time support for LVM Thin Provisioning as a feature. Unfortunately, a late change to fix another serious bug inadvertently introduced a serious bug in this support. If you install Fedora 20 using the release packages (a live install, DVD install, or network install using a repository that contains the frozen release-time package set rather than including updates) and place any system partition (/home and other data partitions are not affected) on a thin-provisioned LV, the installed system will fail to boot. After a delay of 2-3 minutes, it will drop you an emergency mode. The cause of the bug is that tools needed for accessing thin provisioned LVs are erroneously left out of both system-specific and generic initramfs builds due to the broken change in Dracut, the tool that generates the initramfs.
There is no simple workaround for this issue if you are affected by it. Obviously, you can avoid it by not installing to thin-provisioned LVM. Network installs which include the update repository should not be affected by the issue, as the fixed dracut package is now in the stable updates repository.
If you do find yourself affected by the issue and wish to rescue the installation rather than re-install, you can use the installer's rescue mode.
Boot to rescue mode and choose Continue to mount your installed system and go to a shell. Now run the following:
chroot /mnt/sysimage /bin/bash yum update dracut dracut -f exit reboot
Crash when switching from a complete mirror repository to a DVD-based repository: NoSuchGroup: 3d-printing
This issue does not affect the simple cases of booting from the DVD and using it as the package source, or booting from the network install image and using a normal public Fedora mirror as the package source. Each of those cases works fine. You do not need to worry about this issue if this is how you plan to install Fedora 20.
However, if you set the Installation Source for a Fedora 20 installation to be a source with a complete set of packages - such as the default remote repository configuration, or any full Fedora 20 mirror - then switch to a source which contains only the restricted set of packages on the DVD image - such as a repository which simply is the DVD image, accessed via any protocol, or any other repository somehow generated solely from the DVD package set - the installer will likely crash with a NoSuchGroup: 3d-printing error.
In practice what this means is if you boot the network install image normally - so that the default remote repository is automatically configured - and then attempt to switch to, say, an NFS or HTTP repository which just contains the DVD ISO image (or has the contents of the DVD ISO image mounted or copied to it), the installer will likely crash.
There are several possible workarounds for this. You can simply set things up so your install repository contains the full package set, not the subset from the DVD image. You can pass in your desired repository configuration with the inst.repo boot parameter or using a kickstart with the repo command - this will cause your chosen repository to be configured straight away, and so avoid the bug. Or you can boot with the askmethod parameter, which has the effect of telling the installer not to try and configure the default remote repository automatically, but to wait for you to enter the Installation Source hub and choose a repository configuration yourself, which again should avoid the bug. You could even boot from the DVD image itself, though that does not seem likely to be a very useful workaround for the majority of cases where you would actually want to install from a separate repository containing only the DVD image file or contents.
389 Directory Server crashes during search operation
A tester has reported repeated crashes in Fedora 20's 389 Directory Server during search operations. This crash is currently being investigated and will be fixed as soon as possible.
Due to this and other 389 and FreeIPA issues discussed later in this page, we strongly recommend not deploying any kind of production 389 Directory Server or FreeIPA server using the Fedora 20 release at this point. Updates will be issued to resolve this and the other bugs listed on this page, and it should be safe to deploy a Fedora 20-based 389 / FreeIPA server with those updates installed. This entry will be updated when updates are available, or you can follow the relevant tickets.
/root permissions incorrect on pre-release installations
This issue does not affect systems installed with or upgraded after the release of the final release version of Fedora 20, but we are documenting it as it may be of significant interest to those who used Fedora 20 prior to release.
If you used any Fedora 20 pre-release (or test compose or release candidate build), the permissions on the /root directory are likely to be incorrect: an older version of the
package set the permissions to 0755 (users other than root can read files in the /root directory). We felt it not a good idea to try and fix this with an update, as sysadmins who manually change their /root permissions would not want us to override those changes, but we would like to make those who installed from pre-releases aware of the issue. The usual default Fedora permissions (and those set by the final release version of Fedora 20) are 0550. You can run
su -c 'chmod 0550 /root' to set those permissions, which will prevent users other than root from reading files in /root.
Installer crashes with No such file or directory: '/dev/md' if MD-RAID set is referred to by device node name in
If you attempt to install Fedora 20 on a system containing an existing Linux system whose
/etc/fstab contains one or more entries referring to a partition on an MD-RAID set by its device node name (e.g.
/dev/md127p2), the installer will likely crash, with the error No such file or directory: '/dev/md'.
Identifying any storage device by its device node name is fragile and it is usually a better idea to use something more robust such as a filesystem label or UUID, but it is of course a bug that the Fedora installer crashes when it encounters such a situation; it should handle it more gracefully.
To work around this issue, either adjust the
/etc/fstab entry to refer to the device(s) by a more robust identifier, or temporarily comment them out while running the Fedora installation. The latter approach will have the minor drawback that Fedora will not be able to identify the device(s) as being part of any existing installation, and will instead display them in the 'Unknown' group of the Custom Partitioning screen, if you visit it during your installation.
Problem with Installation Source spoke when installing from a partially complete kickstart
If you attempt to install Fedora 20 using a partially-complete kickstart - in particular, a kickstart which specifies a package set but no installation source - you will find that the interactive process for setting that option behaves strangely. On the Installation Source spoke, you may not be able to use the default Closest mirror option. If you are affected by this problem, you can manually enter the URL of the Fedora 20 mirror list, and check the This URL refers to a mirror list. box. The URLs for the 64-bit and 32-bit mirror lists are
If you have an existing UEFI-native operating system and do a UEFI-native install of Fedora alongside it, attempting to boot the previously existing OS from Fedora's bootloader may fail consistently. The reason for this failure is that os-prober currently fails to set the correct boot options for the previously existing OS in the GRUB menu.
You may be able to use your system firmware's interface to the UEFI boot manager to boot the previously existing OS directly. This boot menu is often accessible at reboot time by interrupting the boot process and choosing to boot from a different device, but implementations vary between firmwares. The Windows boot option is often named Windows Boot Manager.
Alternatively, you can use the
efibootmgr command from Fedora to direct the system to boot a particular UEFI boot manager entry on the next reboot.
efibootmgr should list all the UEFI boot manager entries. Identify the one for Windows, and run
su -c 'efibootmgr -n XXXX', where XXXX is the (hexadecimal) number that follows the word Boot in the
efibootmgr output for that entry. For instance, if
[user@host ~]# efibootmgr BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0002 Boot0000* Fedora Boot0002* Windows Boot Manager
then you could run
su -c 'efibootmgr -n 0002' to instruct the system to boot Windows on the next startup.
You may also be able to manually edit the Fedora bootloader (GRUB) configuration to supply the parameters required to boot the previously existing OS from the Fedora boot menu.
Network configuration changes made after clicking Configure in installer (nm-connection-editor) are not applied unless interface is turned off and on again
The Fedora installer's network configuration screen has a button labelled 'Configure', which launches the nm-connection-editor utility to allow configuration of the network connection. Due to issues in the interaction between the installer and the separate nm-connection-editor process, configuration set in the nm-connection-editor process will not take effect unless and until you turn the connection off and then on again. We will attempt to remedy this for future Fedora releases, but it now cannot be resolved in Fedora 20, as the installer cannot be updated after release.
In custom partitioning, cannot change size of a pre-existing LV after setting a mount point for it and scheduling it to be reformatted
If you use custom partitioning while installing Fedora 20 to a system with a pre-existing LVM LV, assign a mount point to that LV, and set it to be re-formatted, you will no longer be able to request that its size be changed. Any attempts to change the 'Desired Capacity' field and hit 'Update Settings' will result in the size returning to the previous value.
This issue is easy to work around; as long as the volume is not both assigned a mount point and scheduled to be reformatted, you can successfully adjust its size (as long as that adjustment is achievable within the container, of course). So if you run into this problem, simply temporarily undo the mount point assignment and/or 'reformat' check box, make the size change, and then re-apply the mount point and 'reformat'.
In custom partitioning, cannot change size of a pre-existing partition then reset it to initial value
If you use custom partitioning while installing Fedora 20 to a system with one or more pre-existing partitions, then change the target size of any partition and subsequently change your mind and decide you did not want to resize it after all, you will not be able to set it back to precisely its original size (and cancel the resize request). Any attempt to do so will cause the value to change to a previous setting, which can look quite strange.
If you do run into this problem, you can work around it by hitting the 'Reset All' button, which will let you start over from scratch with the storage configuration as it actually exists on the disk(s) prior to Fedora 20 installation beginning.
In custom partitioning, cannot change size of a pre-existing LV multiple times then reset it to initial value
If you use custom partitioning while installing Fedora 20 to a system with one or more pre-existing LVM LVs, and change the target size of an LV more than once during one custom partitioning 'run', you will no longer be able to set it back to precisely its original size (and cancel the resize request). Any attempt to do so will cause the value to change to a previous setting, which can look quite strange.
If you're a bit indecisive about what size you want your LVs to be and run into this problem, you can work around it by hitting the 'Reset All' button, which will let you start over from scratch with the storage configuration as it actually exists on the disk(s) prior to Fedora 20 installation beginning.
Installation crashes during partitioning if disk was scanned after an encrypted volume has already been unlocked
This is a complex issue. Broadly speaking, if you somehow trigger the installer to do a disk scan after having already accessed a previously-existing encrypted storage volume, then the installation may crash during the partitioning stage with the error LUKSError: luks device not configured. The bug report contains several different possible reproduction scenarios; all are fairly involved, but it is something you may be most likely to run into when installing to a system with an existing encrypted storage volume and then running through partitioning multiple times or using the Refresh Disks function in the custom partitioning screen.
As there are various ways to encounter this issue and they are all quite involved it's difficult to suggest a precise workaround, but broadly speaking, the workaround is to reboot and try the install again, without using the Refresh Disks button (which actually rescans the disks on the system, as opposed to Reset all which just resets the custom partitioning screen to the state it was in when you first entered - it is safe to use that button) or running the installer or the partitioning phase multiple times.
If you use the Fedora 20 installer's rescue mode, and enter the interactive shell to try and rescue your installed system, then on exiting the shell it would be expected that you would return to the top-level rescue mode menu, or perhaps that the system would reboot. Instead, you wind up stuck on a screen that says Pane is dead. At this point, your partitions are still mounted, and a hard reset could possibly cause data loss. Do not do a hard shut down or reboot. You can hit ctrl-alt-f2 (or ctrl-b 2) to get a second shell and run 'reboot', or just hit ctrl-alt-del to trigger a clean reboot.
Network installation with Authoring and Publishing group selected fails
Due to an unmarked conflict between two texlive-related packages (
), Fedora 20 installations with the Authoring and Publishing package group selected (and possibly with the Font design group selected) will fail.
The offending packages (and groups) are not present on the Fedora 20 DVD, so the bug is not present there. The issue affects only network installs. It will be resolved once the conflict between the two packages is fixed with an update, so long as you enable the updates repository in your installation.
Installer performs a UEFI native installation even if noefi parameter is specified
Due to a change in the kernel's behaviour when the noefi parameter is passed, if you boot a Fedora 20 image in native UEFI mode but pass the noefi parameter to try and force a BIOS-native installation, Fedora 20's installer still believes the system is booted in native UEFI mode and performs a UEFI-native installation. If you are relying on this workaround for some reason, use the updates image to avoid this bug.
UEFI install to ms-dos ('MBR') labelled disk fails with unclear errors
As veterans of the Fedora 16 release may remember, there are two commonly-used 'disk label' or 'partition table' formats known as 'gpt' and 'ms-dos' or 'mbr'.
Fedora 20's installer effectively requires that native UEFI installations be performed to a disk with the 'gpt' format (in fact, it requires that the EFI system partition be on such a disk). In fact, this is not a requirement of the official UEFI specification: it leaves open the possibility of an EFI system partition residing on an ms-dos labelled disk, though it is possible that some firmwares may not support such a configuration.
In any case, if you attempt to do a native UEFI install of Fedora 20 such that the EFI system partition will reside on an ms-dos labelled disk, this will fail. You are likely get an error of the form you have not created a bootloader stage1 target device, possibly with the note that the volume backing the EFI system partition must have one of the following disklabel types: gpt. You may also observe unusual behaviour on the Reclaim space screen, if you use it in your installation attempt. Note that you can encounter this error message even when installing to a gpt-labelled disk if you use custom partitioning and fail to correctly configure an EFI system partition: when doing a UEFI install you must include a partition of the 'EFI system partition' type, and mount it at the path /boot/efi.
We have found that there appear to be some systems 'in the wild' with existing native UEFI operating system installations to an ms-dos labelled drive. Unfortunately, this bug means you cannot install Fedora 20 in a dual-boot configuration to the same drive as such an operating system. You would need to install to a second drive in order to dual boot.
If you wish to do a native UEFI installation of Fedora 20, it must be to a gpt-labelled disk, or you must configure your installation such that all existing partitions on the disk on which the EFI system partition will reside will be deleted (doing this will cause the installer to reformat it with a gpt disk label). Note that it is not possible to change the label format of a disk in a non-destructive way with the installer: it requires a complete re-format.
You can, however, convert it using the
gdisk utility from a live image prior to running the installer. Simply invoke
gdisk as root using your hard disk device as the first argument (e.g.
su -c 'gdisk /dev/sda') and it will offer to convert the partition table for you. After answering "yes", type
w and press Enter to commit the changes to disk, then type
q and press Enter to exit
gdisk. Please note that conversion is a potentially risky operation; make sure you have backups before proceeding! Also, existing operating system installations may fail to boot after converting your partition table, so you may have to reinstall them (or just their bootloader if possible) in order for them to function again.
If you do not actually wish to perform a native UEFI installation, you should boot your installation medium in BIOS compatibility mode if your system firmware allows you to do so. Different firmwares present this capability in different ways, so we cannot provide definitive instructions. If you cannot see how to achieve this in your firmware, you can use an installation medium which is not compatible with UEFI-native booting: for instance, write a USB stick using the
livecd-iso-to-disk tool without passing the
If all else fails, you can boot your installation medium in UEFI native mode, but pass the kernel parameters
inst.updates=https://www.happyassassin.net/updates/updates-1047904.img noefi when booting the installer: this should cause the installer to perform a BIOS-native installation instead of a UEFI-native installation. The updates image is necessary to avoid a bug that causes the installer to still believe it is in UEFI native mode even if the
noefi parameter is passed: see this entry for details.
For Fedora 21, we intend to revise the installer to handle this situation in a better way. We apologize for any inconvenience it causes.
USB stick from which install is running appears as a possible install target
In some circumstances, when you are installing Fedora 20 from a USB stick, the stick itself will show up as a possible 'target disk' on the Installation Destination screen where you choose which disk(s) to install onto. This is not intended to happen. It is not possible to install to the USB stick from which the installation is running: if you attempt to do this, the installation will fail. Naturally, therefore, we recommend you simply avoid selecting the stick on this screen.
'Selected' state for disks is indicated with a small and easily missed check mark
On the installer screen where you choose which disks will be used for Fedora 20 installation, disks that are selected as installation targets are marked with a fairly small black check mark in the lower right hand corner; disks that are not selected do not have the check mark.
This has been changed since Fedora 18, when disks that were selected were highlighted in blue, and now the blue highlight simply means the UI element is selected. So if you click on a disk that was previously selected as an install target, then you have just de-selected it - so the check mark goes away - but the UI element is active, so it is highlighted in blue.
Add to this that if you only have a single hard disk it will be pre-selected as an install target when you enter the page, and it has become clear that this design is confusing people. Many users have entered the screen and clicked to 'select' their single disk - in fact de-selecting it, because it was already selected, but not noticing the mistake.
Bootloader password is required on each boot
If you set a bootloader password during installation of Fedora 19 (which is only possible when doing a kickstart-based install), the password will be required at each boot of the system. This is a change in behaviour from Fedora 15 and earlier, where the password was required only to change settings from within the bootloader.
Lawrence Lowe suggests that the --unrestricted parameter can be added to menuentry lines in the grub config file to make them available without the password being entered.
Non-GNOME initial setup utility does not warn of failure to create a user account
In Fedora 20, the initial-setup utility (shown after a graphical install with any desktop other than GNOME if you do not create a user account during installation) does not present any kind of warning if you leave it without having created a user account. Thus it is relatively easy to arrive at a graphical login screen without any user accounts available.
The old utility would allow you to skip user account creation, but required you to click through a warning in order to do so, to ensure no-one did it inadvertently. This is also how initial-setup should behave.
We have tested that the desktops for which the new tool is used - KDE, Xfce, LXDE, MATE, and Sugar - all allow login as root, so this bug should not present any major roadblocks to accessing the installed system. However, if you do install without creating a user account, we strongly advise that you log in as root only in order to create a user account, and then immediately log out and in future always log in as the user account. Using a graphical desktop with root privileges can increase your vulnerability to remote attack, to simple mistakes having severe consequences, and to bugs caused by software not expecting to be run with root privileges.
This issue does not affect the GNOME initial setup utility: in fact, that utility will not allow you to skip user account creation at all.
Kickstart: if no password is specified for a user account, it will be unlocked
In Fedora 20 (and 19), if you do a kickstart installation and your kickstart contains a user directive with no password, the user will be created as an unlocked account: it will be possible to log in to it with no password. This differs from previous releases and from the behaviour previously described on the wiki page (which has now been updated), where such an account would be created locked: impossible to log into.
To create a locked user account, explicitly specify the --lock parameter to the user directive in your kickstart file. It would be best practice to do this in any case, and not rely on the default behaviour being correct, as this case shows!
This issue will be resolved for future releases.
Upgrade fails if /var is a separate partition
/var, or more specifically the
/var/tmp directory on your system is a separate partition from the root filesystem (whether using regular partitions or LVM), a fedup-based upgrade may fail to work correctly. After the first stage is complete and you reboot, the upgrade environment may fail to find the /var device. Testers report that the system will in fact boot to your normal graphical environment instead of to the upgrade process, in this case.
This is fixed in fedup-0.8.0-4. You don't need to re-run
fedup - just update and reboot.
If you attempt to upgrade a system with the
package installed to Fedora 20, it will likely fail, as the package has broken dependencies in the Fedora 20 repositories. In Fedora 20, nothing else requires the package, but in Fedora 19 and earlier, some things did.
Until we resolve this problem, the workaround is to remove
and all its dependencies before upgrading, perform the upgrade, and then reinstall any of the dependencies you still wish to use. They should all install without a problem after the upgrade.
Fedup: upgrade can't start without rd.luks.uuid/rd.lvm.lv/rd.md.uuid boot args
The system may hang during the reboot after running the command
fedup --network 20 if these parameters are not specified.
Under normal circumstances, the installer would set up those arguments for you, but some people who migrated from GRUB to GRUB2 by hand have dropped those arguments - which works fine for F17 and F18, but fails for F19 and later.
The recommended fix is to restore the rd.luks.uuid/rd.lvm.lv/etc. arguments from your old grub.cfg. In a pinch, you can add "rd.auto=1" to your boot arguments to make dracut try to automatically set up every disk it finds; this isn't recommended for general use though.
Upgrading to Tmux 1.9a-2 results in not being able to connect to sessions created previously
If you've recently updated tmux - you might not be able to connect to sessions created with your earlier version of tmux. There are two workarounds for this. Run
pgrep tmux/exe at
to connect to your older session so you can migrate it - or downgrade.
DVD not available as a package repository after installation
In older releases of Fedora - at least older than Fedora 18 - after you installed from the DVD, it was automatically used as a repository for installing packages after system installation. Since Fedora 18, due to changes to the underlying tools, this function has no longer worked. We hope to be able to restore it soon, but cannot commit to a specific time frame.
A comment on the bug provides a partial workaround which will allow you to install packages from the DVD using the
libvirt guests are killed on host shutdown
When hosting virtual guests via libvirt in recent Fedora releases it is intended that, if you shut the host down with the guests still running, they will be suspended and then resumed when you boot the host up again. This does not currently work in Fedora 20. If you shut the host down with guests running, they will simply be uncleanly shut down (the processes are killed).
We are currently investigating to try and find a fix for this issue. In the mean time, if your virtual guests are of any value to you, please shut them down cleanly before shutting down the host. We apologize for any inconvenience this may cause.
KVM guests using the qxl graphics driver may display sluggish graphics performance on Fedora 20 hosts
With a sufficiently recent version of Fedora's virtualization stack, such as that in Fedora 20, a feature is available for guests that use the qxl virtual graphics adapter and driver which is intended to provide smooth playback of video in the guest guests. However, it seems this 'streaming' mode can erroneously be invoked when certain non-video operations happen in guest machines, and this causes very sluggish graphics performance and artifacting. In particular, the way GNOME 3 handles screen redraws means this problem affects guests running GNOME 3 very badly, but it can also be seen on other desktops in certain circumstances, such as when scrolling through a web page that contains many large images.
We have implemented a workaround for the qxl driver in Fedora 20 which means that Fedora 20 guests are not affected by this bug, and we will likely provide the workaround for Fedora 19 as an update. However, the bug may still be observed on other guest operating systems that include a qxl driver which is new enough to take advantage of the streaming feature, but does not contain this workaround. If you are unfortunate enough to be affected, you can edit the configuration of the virtual machine (e.g. via
virsh), and change the line that looks like this:
<graphics type='spice' autoport='yes'/>
to look like this instead:
<graphics type='spice' autoport='yes'> <streaming mode='off'/> </graphics>
This disables the 'streaming' feature for the virtual machine, which should completely avoid the problem occurring on any guest operating system.
Error messages about swap activation if swap is on a plain partition on a GPT disk
If your swap device is a plain partition (not LVM-backed) on a GPT-labelled disk, it appears that systemd has some trouble activating this, and you will notice errors in your system log at each boot, related to swap activation. However, testing indicates that the swap device is ultimately activated successfully. This issue is unlikely to cause any real problems, we note it purely to explain why you may see these errors in the system log. You can run the command
swapon without any parameters if you wish to check that the partition has been successfully activated.
If you are familiar with debugging this kind of issue using valgrind, you may be able to help us in fixing it. Details on the debugging information that would be useful can be found in bug #1034467 (the corresponding Rawhide bug) and Mozilla bug #972725.
Desktop elements appear too large in GNOME ("high DPI" mode incorrectly enabled)
GNOME / GTK+ 3.10, included in Fedora 20, includes initial support for "high DPI" mode - essentially, rendering text and other display elements using more pixels on very high resolution displays, so that they appear at a 'normal' size.
Detecting when this mode should be engaged depends on being able to reliably determine the display resolution and physical size, and there are some known cases - particularly Samsung displays, particularly televisions - where this does not work correctly, resulting in the "high DPI" mode being enabled on displays where it should not be used. The symptom of this bug is that the GNOME interface, text and icons and so on look too large.
If you are affected by this issue, running the command
gsettings set org.gnome.desktop.interface scaling-factor 1 - as your regular user account, not as root! - should resolve it. A graphical preference for the scaling factor should be added to the GNOME Tweak Tool at some point in the future, to make it easier to override the auto-detected setting.
Crash in speech-dispatcher process when launching GNOME or KDE screen readers
Both GNOME and KDE desktops in Fedora 20 include a screen reader application, a tool for visually-impaired users which reads the contents of the screen aloud. GNOME's is
, KDE's is
. Commonly, when launching either of these, you will be notified of a crash in the
This may be disconcerting, but testing indicates it does not actually prevent the screen reader applications from working correctly; you can safely proceed to use them. It is not necessary to report the crash, as the issue is already known and we are attempting to find a solution, but it will not harm anything if you do.
Repeated dbus error messages logged with ModemManager.service disabled
If you have NetworkManager installed and active, but you disable ModemManager.service - which you might well choose to do if you have no cellular modem - this will result in error messages being printed to the system logs every two minutes:
Dec 14 09:27:02 localhost dbus-daemon: dbus: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Dec 14 09:27:02 localhost dbus: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Dec 14 09:27:02 localhost dbus: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. Dec 14 09:27:02 localhost dbus-daemon: dbus: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
There is no more serious consequence of this problem, but you may find the log spam annoying. You can avoid it by re-enabling ModemManager.service, or by removing ModemManager entirely with
su -c 'yum remove ModemManager'.
Eclipse crashes with Google Talk plugin installed
Multiple users have reported an unusual bug in the Eclipse IDE: it commonly crashes if the Google Talk plugin is installed.
Unfortunately, as the Google Talk plugin is proprietary and no debugging symbols are available, Fedora developers cannot resolve this issue. A Google employee has stated that he has reported the issue internally, but we have received no progress reports since then.
Users have reported that the Eclipse IDE no longer crashes when the latest version of the Google Talk plugin is installed. Therefore updating the plugin would be strongly recommended. If this still fails, a workaround has been suggested at https://bugzilla.redhat.com/show_bug.cgi?id=1043438#c3. Alternatively you may choose to remove the Google Talk plugin.
ZIP support in PHP
In Fedora 20, support from ZIP has been dropped from main php package and is now provided in a separate php-pecl-zip package.
If you need zip support, as for any other extension, run
su -c 'yum install php-zip'.
yum reports duplicate packages installed, older version cannot be easily removed
This note covers a category of issues, rather than a specific bug.
The RPM packaging system used by Fedora allows the execution of scripts, often known in context as 'scriptlets', at various points during the process of installing, removing and updating packages. In this context, RPM considers 'updating' a package to consist of installing the new package and then removing the old package, as two separate operations (in fact, all installation operations are run, and then all removal operations are run). A package can specify scriptlets to run:
- Before the entire transaction of which its installation and/or removal will be a part (%pretrans)
- Before it is installed (%pre)
- After it is installed (%post)
- Before it is removed (%preun)
- After it is removed (%postun)
- After the entire transaction of which its installation and/or removal will be a part (%posttrans)
An idiosyncracy of this system is that it can lead to bugs that are almost impossible to fix entirely. In particular, the %preun stage is vulnerable to this. If a package is ever built with a broken %preun scriptlet, then the game is almost entirely lost: you cannot really 'fix' a broken %preun scriptlet with an update, because of when the scriptlet is executed. 'Updating' to the new package consists of installing the new package and removing the old one, and the broken %preun scriptlet will be executed on removal of the old package. Ironically, in fact, if a packager notices a broken %preun scriptlet and ships an update to fix it, the very act of installing the update that fixes the broken scriptlet will trigger the broken scriptlet. When scriptlet execution fails, RPM will abort immediately and still consider the affected package to be installed, although all its files have already been removed (or updated to the newer version if the package was being updated rather than removed).
Sometimes we are able to work around this with clever tricks like inserting a hack in a scriptlet that we know will be executed before the broken %preun scriptlet which somehow works around the error, but this is not always practical. In general, if you are unfortunate enough to install a package with a broken %preun scriptlet (or, in certain circumstances, another broken scriptlet), it is likely you will wind up with a duplicate package database entry whenever you come to update or remove that package.
If you have been affected by this class of bug and now have a 'duplicate' package installed that you are having difficulty removing, it can usually be resolved by running:
rpm -e --noscripts (packagename-version)
Package versions known to have been affected by this type of issue within the last three releases include the following, though this cannot be known to be an exhaustive list:
- usbmuxd-1.0.8-10.fc19 and usbmuxd-1.0.8-10.fc20
Bluetooth HSP/HFP Profile stops working with upgrade from F19
Fedora 19 used Bluez 4 and supported switching between A2DP Sink profile (sink only) and the HSP/HFP Telephony profile (mono sink + mic source). Fedora 20 migrated to Bluez5 which has a regression causing HSP/HFP Telephone profile to not be available. This regression is documented in the draft release notes for Pulseaudio 5.0, which say (in "Notes for packagers"): "PulseAudio now supports BlueZ 5, but only the A2DP profile. BlueZ 4 is still the only way to make HSP/HFP work."
Text renders fuzzy with Cantarell font (default Gnome font)
Fedora 20 includes a new freetype package, which now uses a new font rendering engine (CFF) compared to previous Fedora releases (autohinter). This engine causes the Cantarell font to appear "fuzzy" due to the font darkening. Several workarounds include using "slight" hinting or to temporarily use the autohinter engine (freetype 2.4.11).
rsyslogd consumes 100% CPU time
Several users have reported seeing the rsyslogd logging daemon consuming 100% of CPU time (this may manifest as sluggish performance and/or high power consumption and heat production). This appears to be triggered by specific contents of the systemd journal.
Deleting the contents of the journal - in either
/run/log/journal - will resolve the issue, though of course result in you losing the copy of the system logs accessible via
journalctl and other journal-related tools.
Attempting to launch the application Panorama Stitcher from the KDE menus in Fedora 20 would result in it crashing. This application is only present on the menus by default if you install from DVD, not if you install from the KDE live image. The panorama function is really one of the many Kipi image manipulation plugins for KDE, and is usually expected to be accessed from a Kipi-enabled graphics manipulation application; its presence in the menus is only a convenience.
Multiple cases of "group (groupname) does not exist" errors when running yum
If you switched to group_command=compat mode as a workaround for this issue, you can now safely return to group_command=objects mode once you have updated yum, by running
There were several similar and inter-related bugs in Fedora 20's Yum package manager which could cause it to print bogus warnings about groups not existing in certain circumstances. You might have seen any of these warning messages:
- Warning: group (groupname) does not exist.
- Warning: environment (groupname) does not exist.
- Warning: Environment Group (groupname) does not exist.
yum groupinstall (groupname),
yum install @(groupname), or
yum upgrade after having once installed any package or environment group with
yum groupinstall (groupname) or
yum install @(groupname). The most common and most visible case of this bug - where you saw multiple instances of the first warning - would occur only if you had updated to yum-3.4.3-120.fc20 or higher, it did not affect the initial Fedora 20 version, yum-3.4.3-106.fc20.
A less immediately visible but somewhat more significant issue was that, when you installed an "environment group", yum failed to correctly keep track of which "package groups" were installed as a part of that "environment group" - it in fact never considered any package group to have been installed as part of an environment group. This meant that running "yum group remove (environment group)" would not remove anything. Note that any such environment group installations you did with an affected version of yum - anything prior to 3.4.3-127 - will still be affected by this.
We have not yet discovered any very serious consequences of these bugs - they are mostly superficial, though they can be annoying. As far as we are currently aware, there is no possibility of data loss, or of the packaging system becoming seriously broken. It is safe to continue using your Fedora 20 system and working with packages, even if you see these messages. Some of the more advanced group functions related to the Fedora 19 "yum groups as objects" feature, however, would not perform as advertised.
Various 'workarounds' were possible, though all involve in some way interfering with the operation of the aforementioned Fedora 19 "yum groups as objects" feature. Probably the safest and most easily reversible was to run:
yum-config-manager --save --setopt=group_command=compat
This will configure yum to effectively disable the "groups as objects" feature and revert to the simple handling of groups it used prior to Fedora 19. The major drawback of this is that the
yum group remove command almost never does what you want in this configuration. Another possible workaround was to run
yum group mark remove (groupname) for each affected group. This was a little more work, and also harder to reverse in future, but it is safe. It tells yum to consider the group in question as 'not installed', but will not lead to the removal of any packages unless you run a specific command or change a configuration setting.
yum groups mark convert command recommended by yum results in many additional packages being installed on yum update
If you run certain yum commands, it may advise you to run a command
yum groups mark convert. This is related to the Fedora 19 "yum groups as objects" feature: it is intended to look at an existing Fedora system, work out which package groups are installed, and write that information out for the use of the "groups as objects" feature.
Testing has indicated that prior to yum-3.4.3-128.fc20 this command was too aggressive in determining which package groups were installed, and marked for instance groups from which only a single package is present on the system as being 'installed', even if that package was actually installed individually or as part of another group. As one of the "groups as objects" features is that not-currently-installed packages from installed groups will be added when running
yum upgrade, the result is that, on running
yum upgrade after
yum groups mark convert, yum will attempt to install many new packages, most of which you likely do not want.
If you ran the command with an affected version of yum and wish to prevent yum trying to install additional packages, there are several possibilities.
The easiest is to run
yum-config-manager --save --setopt=group_command=compat, which will have the effect of disabling the "groups as objects" functionality entirely, reverting yum to its pre-Fedora 19 handling of package groups. Unless you were interested in taking advantage of the "groups as objects" features, you will likely be happy with this behavior.
If you wish to try and maintain the "groups as objects" functionality (despite this bug and the others discussed above), you can run
yum group list installed hidden -v to print the list of groups that yum now believes is installed, and run
yum group mark remove (groupname) to tell yum to consider a group as 'not installed'. Do this for each of the groups you do not want, until yum no longer wishes to install additional packages you do not want.
Missing attributes in objectclasses in 389 Directory Server (and hence FreeIPA)
A bug in the schema parser in the version of the 389 Directory Server included with Fedora 20 could result in objectclasses missing attributes. This bug could have significant and unpredictable negative effects depending on your LDAP configuration; it is at least likely that you will see unexpected errors when attempting to add or modify any entry with one of the broken objectclasses. This bug has already been reported to cause significant issues when running a FreeIPA server on Fedora 20, and if you replicate a broken Fedora 20 deployment of 389 Directory Server / FreeIPA with a working deployment, the issue may spread to the previously-working servers.
Due to other 389 and FreeIPA issues discussed earlier in this page, we still recommend not deploying any kind of production 389 Directory Server or FreeIPA server using the Fedora 20 release at this point. Updates will be issued to resolve the other bugs listed on this page, and it should be safe to deploy a Fedora 20-based 389 / FreeIPA server with those updates installed.
389 Directory Server referential integrity plugin fails to work
If your configuration of the referint (referential integrity) plugin for the 389 Directory Server is missing these two attributes:
nsslapd-pluginEntryScope: dc=example,dc=com nsslapd-pluginContainerScope: dc=example,dc=com
then the plugin would fail to work correctly (attributes would not be adjusted as expected). These attributes were added to the default referint configuration in 389-ds #47621, but it was not intended that the plugin would break if they were not present. If you were affected by this issue, it could be worked around by adjusting your referint plugin configuration to specify these two attributes.
As there are several other significant bugs in this software stack discussed on this page, we strongly recommend you do not deploy FreeIPA or 389 Directory Server on Fedora 20 in production at all until these issues are resolved.
389 Directory Server crashes after enabling FreeIPA Active Directory trust support
It was reported that, if you set up a FreeIPA server on Fedora 20 and enable the Active Directory trust support by running
ipa-adtrust-install, the 389 Directory Server (LDAP server) could crash. In fact there were two crashes, one in 389-ds itself, and one in the
plugin. The result of this was that the FreeIPA domain will cease to function correctly, since the LDAP server component is a vital one.
Upgrade to Fedora 20 with fedup 0.7 fails, reboots shortly after booting the System Upgrade option
Upgrading from Fedora 18 or Fedora 19 to Fedora 20 using the FedUp utility will fail if you use version 0.7 or earlier. The symptom is that the first stage of upgrade (before rebooting) works successfully, but when you reboot to complete the upgrade, the second stage begins but almost immediately aborts and reboots back to your previous Fedora system. The failure is not harmful in any way - your existing Fedora install will not be damaged, and you will be able to upgrade to Fedora 20 successfully by following the instructions below.
We apologize for this error - pre-release testing of Fedora 20 indicated that fedup 0.7 would work successfully for most upgrades, but this does not seem to have worked out.
Happily, the resolution is simple: use fedup 0.8 or later for a successful upgrade. If you have not yet upgraded to Fedora 20, simply ensure you have version 0.8 or later of fedup installed (it is available from the updates repository) before running. As long as you use fedup 0.8 or later, your upgrade should run successfully.
If you have already run fedup 0.7 and encountered this issue, you can achieve a successful upgrade with fedup 0.8. Note that the location to which fedup downloads files has changed between 0.7 and 0.8. You can simply run 0.8 and achieve a successful upgrade, but it will re-download files unnecessarily, consuming time, bandwidth and space. To avoid this, before running fedup 0.8, run these commands:
su -c 'mv /var/lib/fedora-upgrade /var/lib/system-upgrade' su -c 'mv /var/tmp/fedora-upgrade /var/tmp/system-upgrade'
This will save you time, bandwidth and disk space.
If you have already run both a failed 0.7 and a successful 0.8 upgrade attempt, you may wish to check if the
/var/tmp/fedora-upgrade directories exist, and if so, remove them: they are no longer needed and are simply occupying disk space.
Upgrade to Fedora 20 with fedup 0.8 fails due to GPG key problems
Version 0.8 of the FedUp upgrader adds checking of GPG keys on packages as a feature. This improves the security and verifiability of the upgrade process, but there are a few circumstances in which it may cause problems.
First, it requires that the version of Fedora you are upgrading from have the package signing keys of the version of Fedora you are upgrading to available. This requires that you update to the latest stable version of the
package prior to running fedup. Otherwise, it will fail during the setup phase with the error message Downloading failed: could not verify GPG signature: No public key.
Second, fedup may abort if it cannot find a GPG key for all enabled package repositories. If you have any third party repositories configured, fedup may not be able to find keys for them. If fedup is failing with what looks like a GPG key-related error, and you have any third party repositories enabled, try temporarily disabling them before running fedup. You can re-enable them after the upgrade has completed and then run
yum update to update packages from them.
Alternative on-screen keyboards do not work correctly in GNOME
A bug in the
window manager for GNOME 3 meant that on-screen keyboards other than GNOME's own native one (available from the 'Universal Access' control panel applet or panel menu if enabled) would not work correctly: clicking on a key on the keyboard would not result in the character appearing in the currently-active application.
Testing indicated that, in Fedora 20, it was not possible to browse SMB/CIFS shared resources - i.e. Windows or Samba file or device shares - with the default FirewallD firewall enabled, even if you enabled the 'samba-client' firewalld service. By comparison, in Fedora 19, browsing appeared to work even without needing to enable that service. The issue was not specific to a particular desktop or file manager utility, it seemed to be an issue in the firewalling layer. You could connect to a share by entering the path explicitly, and shares that were advertised via zeroconf/Bonjour may show up when you browse.
Users of the MyPasswordSafe application reported that it commonly crashed on Fedora 20 when generating or entering passwords. If you submitted a bug report it would likely appear as a duplicate of bug #1042667.
Disabling SELinux via configuration file failed with libselinux-2.2.1-4.fc20
After the release of Fedora 20, libselinux-2.2.1-4.fc20 was submitted as an update, passed basic validation testing, and went to the stable updates repository. Unfortunately, it turned out that this update contained a bug which makes it impossible to disable SELinux via the configuration file
/etc/selinux/config. If you set:
in that file, you would instead most likely get permissive mode, rather than a completely disabled SELinux. To work around this issue, you could pass selinux=0 on the kernel command line: this would successfully disable SELinux.
CUPS hangs on shutdown (causing a long wait on system shutdown) if printer sharing is enabled
It was reported that if the Publish shared printers connected to this system option was enabled in Print Settings - Server Settings, then the CUPS daemon would hang when the system tried to stop it (i.e. on shutdown/reboot or when stopping it manually with
systemctl stop cups.service). After a few minutes, systemd would time out and forcibly kill the process allowing the shutdown/reboot to complete.
ARM: HDMI output and USB peripherals not working on Beagle Bone Black
Fedora 20 GA has non functional USB/HDMI. At the moment, to use the Beagle Bone Black, you will need a serial console attached to the 6 pin serial header. There's full details here. The 3.12.7 kernel has full working usb/hdmi/network. There's kernel but not user space support for a virtual serial port over the USB OTG port but this is as yet doesn't have userspace support. Unofficial updated images are planned to be made available by the Fedora ARM team for the convenience of Beagle Bone Black users shortly after the 3.12 kernel lands with the only difference being the 3.12 kernel in the image.
GNOME Shell crashes after creating a keyring without a password
In Fedora 20 with the GNOME desktop, if you attempted to create a new keyring without a password or change the password of your keyring to an empty string (you may do this from the "Passwords and Keys" application, or you may be prompted to create a keyring password the first time GNOME attempts to store some kind of key), the GNOME shell would crash. The workaround for this is to always use a password on your keyring.
Sudden inability to unlock screen, or log in to running system (caused by creation of /var/run/nologin)
The systemd version (208-9.fc20) included with Fedora 20 can, on some systems, cause the file
/var/run/nologin (or - reports differ -
/run/nologin) to be created during normal system operation. This has various consequences: it will prevent new user logins to the system, prevent a shutdown being triggered, and can prevent unlocking an active session. There has been one report that, if the system is hibernated in this state, on resume, the desktop session will not be locked.
This behaviour ultimately appears to be triggered by the issuing of multiple
systemctl commands in quick succession. This can sometimes occur during package installation / update / removal operations.
Attempting to perform an affected operation at a console will present the message "System is booting up. See pam_nologin(8)." The workaround is to remove the file
/var/run/nologin manually: if you are 'locked out', you should be able to log into a virtual terminal (ctrl-alt-f2, ctrl-alt-f3...) as root to remove the file.