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, 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 Fedora 20 release announcement and the Fedora 20 release notes for specific information about changes in Fedora 20 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. 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 this page)
- CommonBugs+(bugs with CommonBugs keyword and contain a link to this page)
Major issues
System fails to boot after install using LVM Thin Provisioning
link to this item - Bugzilla: #1040669
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. Once the fix for the issue reaches the official repositories, which should be soon, network installs which include the update repository should not be affected by the issue.
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 --enablerepo=updates-testing --advisory=FEDORA-2013-23326 dracut -f exit reboot
This should update 
dracut
Crash when switching from a complete mirror repository to a DVD-based repository: NoSuchGroup: 3d-printing
link to this item - Bugzilla: #1033749
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 is an updates image for the installer which fixes this issue available at http://bcl.fedorapeople.org/updates/1033749.img (note this is not an SSL-capable server: we assert that the correct sha256sum for this image is cc69aa395a66b1609106d41674f5546ddc5ab330c9bf5e2d8333292011ff381b ). Instructions on using an updates image are available Anaconda/Updates here: in short, simply pass the parameter inst.updates=http://bcl.fedorapeople.org/updates/1033749.img to the installer.
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.
Multiple cases of "group (groupname) does not exist" errors when running yum
link to this item - Bugzilla: #1043207 - Bugzilla: #1014202 - Bugzilla: #1043221 - Bugzilla: #1043231
There are several similar and inter-related bugs in Fedora 20's Yum package manager which can cause it to print bogus warnings about groups not existing in certain circumstances. You may see any of these warning messages:
- Warning: group (groupname) does not exist.
- Warning: environment (groupname) does not exist.
- Warning: Environment Group (groupname) does not exist.
when running 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 see multiple instances of the first warning - will occur only if you have updated to yum-3.4.3-120.fc20 or higher, it does not affect the initial Fedora 20 version, yum-3.4.3-106.fc20.
A less immediately visible but somewhat more significant issue is that, when you install an "environment group", yum fails to correctly keep track of which "package groups" were installed as a part of that "environment group" - it in fact never considers any package group to have been installed as part of an environment group. This means that running "yum group remove (environment group)" will not remove anything.
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, will not perform as advertised.
Various 'workarounds' are 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 is 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. Once the bugs discussed here are resolved, you can run:
yum-config-manager --save --setopt=group_command=objects
to return to "groups as objects" mode, if you wish. Another possible workaround is to run yum group mark remove (groupname) for each affected group. This is 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.
We will work to provide updates that permanently resolve these issues as quickly as possible.
yum groups mark convert command recommended by yum results in many additional packages being installed on yum update
link to this item - Bugzilla: #1043207
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 this command is too aggressive in determining which package groups are installed, and marks 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 have not yet run yum groups mark convert, we advise for the present that you do not do so, regardless of yum's suggestion. If you have run the command 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)
link to this item - 389-ds #47631
A bug in the schema parser in the version of the 389 Directory Server included with Fedora 20 can 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 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.
389 Directory Server crashes during search operation
link to this item - 389-ds #47629
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
link to this item - Bugzilla: #1037688
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 su -c 'chmod 0550 /root' to set those permissions, which will prevent users other than root from reading files in /root.
Installation issues
Problem with Installation Source spoke when installing from a partially complete kickstart
link to this item - Bugzilla: #972265
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 https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=x86_64 and https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=i386 respectively.
Network configuration changes made after clicking Configure in installer (nm-connection-editor) are not applied unless interface is turned off and on again
link to this item - Bugzilla: #1018471
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
link to this item - Bugzilla: #1040445
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
link to this item - Bugzilla: #1040352
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
link to this item - Bugzilla: #1040413
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
link to this item - Bugzilla: #1008732
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.
link to this item - Bugzilla: #1038855
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.
Upgrade issues
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 before running. We will ensure it is pushed to the stable Fedora 18 and 19 repositories as soon as possible, but until then, you may need to run su -c 'yum --enablerepo=updates-testing update fedup' to get a new enough version. 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/lib/fedora-upgrade and /var/tmp/fedora-upgrade directories exist, and if so, remove them: they are no longer needed and are simply occupying disk space.
Upgrade from Fedora 19 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. However, this 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. On Fedora 19, this requires that you update to the latest stable version of the 'fedora-release' 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
Upgrade from Fedora 18 with fedup 0.8 fails due to GPG key problems
link to this item - Bugzilla: #1040689
Version 0.8 of the FedUp upgrader adds checking of GPG keys on packages as a feature. However, this 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. At present, the Fedora 20 package signing keys are not correctly available in Fedora 18, so if you try to upgrade from Fedora 18 to Fedora 20 using a 0.8 version of fedup, it will fail at the end of the package download phase with the error message Downloading failed: The GPG keys listed for the "Fedora 20 - x86_64" repository are already installed but they are not correct for this package.
You can work around this issue by passing the --nogpgcheck parameter to fedup. As the name suggests, this disables the GPG check. We still recommend using fedup 0.8 to upgrade, as it fixes a number of bugs compared to fedup 0.7, and this problem does not represent a regression as there was no GPG checking function in fedup 0.7.
You can also manually verify and import the Fedora 20 key: rpm --import https://fedoraproject.org/static/246110C1.txt before running fedup.
Hardware issues
ARM: HDMI output and USB peripherals not working on Beagle Bone Black
link to this item - Bugzilla: #1012025
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 ping serial header. There's full details here. The 3.12.5 kernel has full working usb/hdmi/network. It is currently in the kernel-nodebug repository, but there is a low expectation of support or testing of nodebug kernels. The 3.12 kernel should make it to updates-testing soon. 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.
Software issues
ZIP support in PHP
link to this item - Bugzilla: #999313
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'.
GNOME Shell crashes after creating a keyring without a password
link to this item - Bugzilla: #1012844
In Fedora 20 with the GNOME desktop, if you attempt 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 will crash. The workaround for this is to always use a password on your keyring.
An updated clutter package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. However, note that one tester has reported that the update causes graphical corruption issues on an Intel video adapter. To test the update, run this command:
su -c 'yum --enablerepo=updates-testing update --advisory=FEDORA-2013-22280'
link to this item - Bugzilla: #1040922
Attempting to launch the application Panorama Stitcher from the KDE menus in Fedora 20 will 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. If you do want to invoke the panorama function directly, you can call it with some image files as arguments - panoramagui image.jpg image2.jpg image3.jpg ... - and it will run successfully.
An updated digikam package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, run this command:
su -c 'yum --enablerepo=updates-testing update --advisory=FEDORA-2013-23252'
link to this item - Bugzilla: #1038959
Testing has indicated that, in Fedora 20, it is 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 enable the 'samba-client' firewalld service. By comparison, in Fedora 19, browsing appears to work even without needing to enable that service. The issue is not specific to a particular desktop or file manager utility, it seems to be an issue in the firewalling layer. You can connect to a share by entering the path explicitly, and shares that are advertised via zeroconf/Bonjour may show up when you browse.
Besides using zeroconf or simply directly entering share addresses, there are two possible workarounds for the bug, but neither is without consequences. You can simply disable the firewall (from the firewall configuration tool, or with su -c 'systemctl stop firewalld.service'), or place the relevant network interface in the 'trusted' firewall zone (which allows all traffic to and from that interface, so is more or less identical in effect to disabling the firewall) - you can do this from your desktop's network configuration utility. Either of these approaches, obviously, results in your losing the security benefits of the firewall. Alternatively, you can configure a custom firewalld rule to accept all from source port 137/udp; this is less drastic than disabling the firewall entirely, but still possibly constitutes a slight lowering of protection.
If you do use a workaround to enable browsing, we would suggest doing so only long enough to discover the shares you wish to configure, then setting up some sort of permanent configuration / bookmark for them, so you no longer need the browsing functionality and can drop the workaround.
We are currently investigating and attempting to come up with a correct resolution for this problem.
libvirt guests are killed on host shutdown
link to this item - Bugzilla: #1031696
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
link to this item - Bugzilla: #1020393
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.
Alternative on-screen keyboards do not work correctly in GNOME
link to this item - Bugzilla: #1019073
A bug in the
An updated package that addresses this issue should be available soon.
Crash in speech-dispatcher process when launching GNOME or KDE screen readers
link to this item - Bugzilla: #995639
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
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
link to this item - Bugzilla: #1018017
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[671]: dbus[671]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Dec 14 09:27:02 localhost dbus[671]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Dec 14 09:27:02 localhost dbus[671]: [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[671]: dbus[671]: [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'.
389 Directory Server crashes after enabling FreeIPA Active Directory trust support
link to this item - Bugzilla: #1041732 - Bugzilla: #1043546
It has been 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) can crash. In fact there are two crashes, one in 389-ds itself, and one in the
Updates will arrive to resolve these issues very shortly. In the mean time, we advise you do not attempt to enable Active Directory trust support for a FreeIPA server based on Fedora 20. In fact, 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 referential integrity plugin fails to work
link to this item - 389-ds #47624
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 will fail to work correctly (attributes will 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 are affected by this issue, it can be worked around by adjusting your referint plugin configuration to specify these two attributes.
Updates will arrive to resolve this and other issues very shortly. 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.