From Fedora Project Wiki

(→‎Upgrade issues: Update fedora-release on F19 before attempting fedup 0.8)
m (add category)
 
(117 intermediate revisions by 20 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
{{autolang|base=yes}}


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.
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.


== Release Notes ==
== Release Notes ==
Line 7: Line 7:


== My bug is not listed ==
== My bug is not listed ==
Not every bug is listed in this page, but [http://bugzilla.redhat.com 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.
Not every bug is listed in this page, but [https://bugzilla.redhat.com 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 [http://bugzilla.redhat.com 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.
To see if your bug has already been reported, you can [https://bugzilla.redhat.com/query.cgi 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:
If you believe an already-reported bug report should be added to ''this'' page because it is commonly encountered, you can:
Line 19: Line 19:


For reference, you can query Bugzilla for bugs tagged CommonBugs:
For reference, you can query Bugzilla for bugs tagged CommonBugs:
* [http://bit.ly/fedora-commonbugs-proposed CommonBugs?] (bugs with CommonBugs keyword, but ''do not yet'' have a link to this page)
* [http://bit.ly/fedora-commonbugs-proposed CommonBugs?] (bugs with CommonBugs keyword, but ''do not yet'' have a link to one or more Common Bugs pages)
* [http://bit.ly/fedora-commonbugs-accepted CommonBugs+](bugs with CommonBugs keyword ''and'' contain a link to this page)
* [http://bit.ly/fedora-commonbugs-accepted CommonBugs+](bugs with CommonBugs keyword ''and'' contain a link to one or more Common Bugs pages)


<!--  
<!--  
When adding issues to this page, ensure to add the CommonBugs keyword to the bug report, and add the anchor link to the entry on this page in the Whiteboard field on the bug report.
When adding issues to this page, ensure that you add the CommonBugs keyword to the bug report, and add the anchor link to the entry on this page in the Whiteboard field on the bug report.
-->
-->
<!-- *** FOLLOW THIS FORMAT FOR ALL ENTRIES PLEASE. ***
<!-- *** FOLLOW THIS FORMAT FOR ALL ENTRIES PLEASE. ***
{{Anchor|Issue-Foo}}
{{Anchor|Issue-Foo}}
=== Issue Foo (example) ===
=== Issue Foo (example) ===
<small>[[{{subst:PAGENAME}}#Issue-Foo|link to this item]] - [[rhbug:XXXXXX|Bugzilla: #XXXXXXX]]</small>
<small>[[#Issue-Foo|link to this item]] - [[rhbug:XXXXXX|Bugzilla: #XXXXXXX]]</small>


Words words words. Blah blah blah. Include a good explanation of the problem, and any available workarounds.
Words words words. Blah blah blah. Include a good explanation of the problem, and any available workarounds.


If a build which may fix the problem is made available via updates-testing, add this boilerplate paragraph (appropriately customized for the issue):
If an update that fixes the problem has landed in the stable updates repository, create the entry in or move it to the "Resolved issues" section and add this boilerplate paragraph (appropriately customized for the issue) to the top of the entry:


An updated [http://admin.fedoraproject.org/updates/(advisory)/(name)-(EVR) (name)] package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and [http://admin.fedoraproject.org/updates/(advisory)/(name)-EVR report to Bodhi] whether it solves the problem. To test the update, run this command: <pre>command|su -c 'yum --enablerepo=updates-testing update --advisory=(advisory)'</pre>
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/(advisory)/(name)-(EVR) an update to (name)]. Updating your system according to your usual procedures should resolve this issue.}}


If a scratch build which may fix the problem is made available via Koji (rather than in updates-testing), add this boilerplate paragraph (appropriately customized for the issue):
If a build which may fix the problem is made available via updates-testing, add this boilerplate paragraph (appropriately customized for the issue) to the top of the entry:


A test build that should resolve this problem is available from Koji: [http://koji.fedoraproject.org/koji/taskinfo?taskID=XXXXXXX packagename-EVR]. If you are affected by this issue, please test this update and report your results to the [[rhbug:XXXXXX|bug report]].
{{Admon/tip|Update available for testing|An updated [https://admin.fedoraproject.org/updates/(advisory)/(name)-(EVR) (name)] package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and [https://admin.fedoraproject.org/updates/(advisory)/(name)-EVR report to Bodhi] whether it solves the problem. To test the update, run this command: <pre>su -c 'yum --enablerepo=updates-testing update --advisory=(advisory)'</pre>}}


If the page is in pre-release state and a documented problem has been fixed in Branched repos but no newer pre-release has yet come out, add this boilerplate paragraph (appropriately customized for the issue):
If a scratch build which may fix the problem is made available via Koji (rather than in updates-testing), add this boilerplate paragraph (appropriately customized for the issue) to the top of the entry:


This issue was fixed in the updated ''(name)-(EVR)'' package. To solve the issue, update your (pre-release name, e.g. "Fedora 13 Beta") installation as usual. You should no longer encounter this issue after updating to that version or later of {{package|(name)}}.
{{Admon/tip|Experimental build available for testing|A test build that should resolve this problem is available from Koji: [http://koji.fedoraproject.org/koji/taskinfo?taskID=XXXXXXX packagename-EVR]. If you are affected by this issue, please test this update and report your results to the [[rhbug:XXXXXX|bug report]].}}
 
If the page is in pre-release state and a documented problem has been fixed in Branched repos but no newer pre-release has yet come out, add this boilerplate paragraph (appropriately customized for the issue) to the top of the entry:
 
{{Admon/tip|Resolved with newer package|This issue was fixed in the updated ''(name)-(EVR)'' package. To solve the issue, update your (pre-release name, e.g. "Fedora 13 Beta") installation as usual. You should no longer encounter this issue after updating to that version or later of {{package|(name)}}.}}


When the page is in pre-release state and a new pre-release becomes available, simply remove any issues that are now fixed from the page entirely.
When the page is in pre-release state and a new pre-release becomes available, simply remove any issues that are now fixed from the page entirely.
-->
-->
== Major issues ==
== Major issues ==
{{Anchor|rpm-scriptlets-fail}}
=== RPM scriptlets fail during updates ===
<small>[[#rpm-scriptlets-fail|link to this item]] - [[rhbug:1054350|Bugzilla: #1054350]]</small>
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2014-0870/selinux-policy-3.12.1-117.fc20 selinux-policy-3.12.1-117.fc20] an update to SELinux policy. It however requires the following workaround if you updated to selinux-policy-3.12.1-116.fc20 which contained the bug. If you have a previous version installed, you are not affected and can simply update to the new version without issue.}}
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.
Sample output:
<pre>
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
</pre>
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.
<pre>
# setenforce 0
# yum clean expire-cache
# yum update selinux-policy\*
# setenforce 1
</pre>
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.
{{Anchor|lvm-thinp-fail}}
{{Anchor|lvm-thinp-fail}}
=== System fails to boot after install using LVM Thin Provisioning ===
=== System fails to boot after install using LVM Thin Provisioning ===
Line 54: Line 87:
Fedora 20 introduces [[Releases/20/ChangeSet#OS_Installer_Support_for_LVM_Thin_Provisioning|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.
Fedora 20 introduces [[Releases/20/ChangeSet#OS_Installer_Support_for_LVM_Thin_Provisioning|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.
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.
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.
Line 61: Line 94:
<pre>
<pre>
chroot /mnt/sysimage /bin/bash
chroot /mnt/sysimage /bin/bash
yum update --enablerepo=updates-testing --advisory=FEDORA-2013-23326
yum update dracut
dracut -f
dracut -f
exit
exit
Line 71: Line 104:
=== Crash when switching from a complete mirror repository to a DVD-based repository: ''NoSuchGroup: 3d-printing'' ===
=== Crash when switching from a complete mirror repository to a DVD-based repository: ''NoSuchGroup: 3d-printing'' ===
<small>[[#dvd-repo-crash|link to this item]] - [[rhbug:1033749|Bugzilla: #1033749]]</small>
<small>[[#dvd-repo-crash|link to this item]] - [[rhbug:1033749|Bugzilla: #1033749]]</small>
{{Admon/tip|Fix available|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 <code>inst.updates<nowiki>=http://bcl.fedorapeople.org/updates/1033749.img</nowiki></code> to the installer.}}


'''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.
'''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.
Line 79: Line 114:


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'' [http://wwoods.fedorapeople.org/doc/boot-options.html#_inst_repo boot parameter] or using a [[Anaconda/Kickstart#repo|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.
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'' [http://wwoods.fedorapeople.org/doc/boot-options.html#_inst_repo boot parameter] or using a [[Anaconda/Kickstart#repo|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.
{{Anchor|yum-group-errors}}
=== Multiple cases of "group (groupname) does not exist" errors when running yum ===
<small>[[#yum-group-errors|link to this item]] - [[rhbug:1043207|Bugzilla: #1043207]] - [[rhbug:1014202|Bugzilla: #1014202]] - [[rhbug:1043221|Bugzilla: #1043221]] - [[rhbug:1043231|Bugzilla: #1043231]]</small>
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 {{command|yum groupinstall (groupname)}}, {{command|yum install @(groupname)}}, or {{command|yum upgrade}} after having once installed any package or environment group with {{command|yum groupinstall (groupname)}} or {{command|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 [[Features/YumGroupsAsObjects|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 [[Features/YumGroupsAsObjects|Fedora 19 "yum groups as objects"]] feature. Probably the safest and most easily reversible is to run:
<pre>
yum-config-manager --save --setopt=group_command=compat
</pre>
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 {{command|yum group remove}} command almost never does what you want in this configuration. Once the bugs discussed here are resolved, you can run:
<pre>
yum-config-manager --save --setopt=group_command=objects
</pre>
to return to "groups as objects" mode, if you wish. Another possible workaround is to run {{command|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.
{{Anchor|yum-mark-convert}}
=== ''yum groups mark convert'' command recommended by yum results in many additional packages being installed on ''yum update'' ===
<small>[[#yum-mark-convert|link to this item]] - [[rhbug:1043237|Bugzilla: #1043207]]</small>
If you run certain yum commands, it may advise you to run a command {{command|yum groups mark convert}}. This is related to the [[Features/YumGroupsAsObjects|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 {{command|yum upgrade}}, the result is that, on running {{command|yum upgrade}} after {{command|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 {{command|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 {{command|yum-config-manager --save --setopt<nowiki>=</nowiki>group_command<nowiki>=</nowiki>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 [[#yum-group-errors|the others discussed above]]), you can run {{command|yum group list installed hidden -v}} to print the list of groups that yum now believes is installed, and run {{command|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.
{{Anchor|389-freeipa-broken}}
=== Missing attributes in objectclasses in 389 Directory Server (and hence FreeIPA) ===
<small>[[#389-freeipa-broken|link to this item]] - [https://fedorahosted.org/389/ticket/47631 389-ds #47631]</small>
A bug in the schema parser in the version of the [http://directory.fedoraproject.org 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 [http://www.freeipa.org 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.


{{Anchor|389-search-crash}}
{{Anchor|389-search-crash}}
Line 139: Line 124:


{{Anchor|prerelease-root-perms}}
{{Anchor|prerelease-root-perms}}
=== /root permissions incorrect on pre-release installations ===
=== /root permissions incorrect on pre-release installations ===
<small>[[#prerelease-root-perms|link to this item]] - [[rhbug:1037688|Bugzilla: #1037688]]</small>
<small>[[#prerelease-root-perms|link to this item]] - [[rhbug:1037688|Bugzilla: #1037688]]</small>
Line 148: Line 132:


== Installation issues ==
== Installation issues ==
{{Anchor|mdraid-fstab-crash}}
=== Installer crashes with ''No such file or directory: '/dev/md''' if MD-RAID set is referred to by device node name in {{filename|/etc/fstab}} ===
<small>[[#mdraid-fstab-crash|link to this item]] - [[rhbug:980267|Bugzilla: #980267]]</small>
If you attempt to install Fedora 20 on a system containing an existing Linux system whose {{filename|/etc/fstab}} contains one or more entries referring to a partition on an MD-RAID set by its device node name (e.g. {{filename|/dev/md0p1}} or {{filename|/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 {{filename|/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.
{{Anchor|partial-kickstart-problems}}
{{Anchor|partial-kickstart-problems}}
=== Problem with Installation Source spoke when installing from a partially complete kickstart ===
=== Problem with Installation Source spoke when installing from a partially complete kickstart ===
Line 153: Line 147:


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 <code>https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=x86_64</code> and <code>https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=i386</code> respectively.
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 <code>https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=x86_64</code> and <code>https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=i386</code> respectively.
{{Anchor|uefi-windows-dual}}
=== Booting previously installed OS (including Windows) from the Fedora bootloader menu may fail after UEFI installation ===
<small>[[#uefi-windows-dual|link to this item]] - [[rhbug:986731|Bugzilla: #986731]]</small>
If you have an existing [[Unified_Extensible_Firmware_Interface|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 {{command|efibootmgr}} command from Fedora to direct the system to boot a particular UEFI boot manager entry on the next reboot. {{command|efibootmgr}} should list all the UEFI boot manager entries. Identify the one for Windows, and run {{command|su -c 'efibootmgr -n XXXX'}}, where ''XXXX'' is the (hexadecimal) number that follows the word ''Boot'' in the {{command|efibootmgr}} output for that entry. For instance, if {{command|efibootmgr}} showed:
<pre>
[user@host ~]# efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0002
Boot0000* Fedora
Boot0002* Windows Boot Manager
</pre>
then you could run {{command|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.


{{Anchor|anaconda-nmce-network}}
{{Anchor|anaconda-nmce-network}}
Line 198: Line 213:
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.
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 ==
{{Anchor|texlive-ht-insanity}}
{{Anchor|fedup-07-fail}}
=== Network installation with ''Authoring and Publishing'' group selected fails ===
=== Upgrade to Fedora 20 with fedup 0.7 fails, reboots shortly after booting the System Upgrade option ===
<small>[[#texlive-ht-insanity|link to this item]] - [[rhbug:959696|Bugzilla: #959696]]</small>
<small>[[Common F20 bugs#fedup-07-fail|link to this item]]</small>
 
Due to an unmarked conflict between two texlive-related packages ({{package|ht}} and {{package|texlive-tex4ht-bin}}), 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.
 
{{Anchor|noefi-doesnt-work}}
=== Installer performs a UEFI native installation even if ''noefi'' parameter is specified ===
<small>[[#noefi-doesnt-work|link to this item]] - [[rhbug:1047904|Bugzilla: #1047904]]</small>
 
{{Admon/tip|Fix available|There is an updates image for the installer which fixes this issue available at <nowiki>https://www.happyassassin.net/updates/updates-1047904.img</nowiki>. Instructions on using an updates image are available [[Anaconda/Updates|here]]: in short, simply pass the parameter <code>inst.updates<nowiki>=https://www.happyassassin.net/updates/updates-1047904.img</nowiki></code> to the installer.}}
 
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.
 
{{Anchor|uefi-msdos-label}}
 
=== UEFI install to ms-dos ('MBR') labelled disk fails with unclear errors ===
<small>[[#uefi-msdos-label|link to this item]] - [[rhbug:978430|Bugzilla: #978430]]</small>
 
As veterans of the [https://docs.fedoraproject.org/en-US/Fedora/16/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html 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 <code>gdisk</code> utility from a live image prior to running the installer.  Simply invoke <code>gdisk</code> as root using your hard disk device as the first argument (e.g. <code>su -c 'gdisk /dev/sda'</code>) and it will offer to convert the partition table for you.  After answering "yes", type <code>w</code> and press Enter to commit the changes to disk, then type <code>q</code> and press Enter to exit <code>gdisk</code>.  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 {{command|livecd-iso-to-disk}} tool without passing the <code>--efi</code> parameter.
 
If all else fails, you can boot your installation medium in UEFI native mode, but pass the kernel parameters <code>inst.updates=<nowiki>https://www.happyassassin.net/updates/updates-1047904.img</nowiki> noefi</code> 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 <code>noefi</code> parameter is passed: see [[#noefi-doesnt-work|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.
 
{{Anchor|usb-target-filter}}
 
=== USB stick from which install is running appears as a possible install target ===
<small>[[#usb-target-filter|link to this item]] - [[rhbug:874381|Bugzilla: #874381]]</small>
 
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.
 
{{Anchor|checkmark-disk-select}}
 
=== 'Selected' state for disks is indicated with a small and easily missed check mark ===
<small>[[#checkmark-disk-select|link to this item]] - [[rhbug:967682|Bugzilla: #967682]]</small>
 
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.
 
{{Anchor|bootloader-password}}
=== Bootloader password is required on each boot ===
<small>[[#bootloader-password|link to this item]] - [[rhbug:840160|Bugzilla: #840160]]</small>
 
If you set a bootloader password during installation of Fedora 19 (which is only possible when doing a [[Anaconda/Kickstart|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 [https://bugzilla.redhat.com/show_bug.cgi?id=840160#c14 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.
 
{{Anchor|initial-setup-user}}
=== Non-GNOME initial setup utility does not warn of failure to create a user account ===
<small>[[#initial-setup-user|link to this item]] - [[rhbug:965797|Bugzilla: #965797]]</small>
 
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.


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 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.


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.
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.


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 {{command|su -c 'yum --enablerepo<nowiki>=</nowiki>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.
{{Anchor|kickstart-nopassword-unlock}}
=== Kickstart: if no password is specified for a user account, it will be unlocked ===
<small>[[#kickstart-nopassword-unlock|link to this item]] - [[rhbug:1063540|Bugzilla: #1063540]]</small>


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:
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.
<pre>
su -c 'mv /var/lib/fedora-upgrade /var/lib/system-upgrade'
su -c 'mv /var/tmp/fedora-upgrade /var/tmp/system-upgrade'
</pre>
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 {{filename|/var/lib/fedora-upgrade}} and {{filename|/var/tmp/fedora-upgrade}} directories exist, and if so, remove them: they are no longer needed and are simply occupying disk space.
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!


{{Anchor|fedup-19-gpg}}
This issue will be resolved for future releases.
=== 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''


{{Anchor|fedup-18-gpg}}
== Upgrade issues ==
=== Upgrade from Fedora 18 with fedup 0.8 fails due to GPG key problems ===
{{Anchor|fedup-var-partition}}
<small>[[Common F20 bugs#fedup-18-gpg|link to this item]] - [[rhbug:1040689|Bugzilla: #1040689]]</small>
=== Upgrade fails if ''/var'' is a separate partition ===
<small>[[#fedup-var-partition|link to this item]] - [[rhbug:1045168|Bugzilla: #1045168]]</small>


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.''
If the {{filename|/var}}, or more specifically the {{filename|/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.


You can work around this issue by passing the <tt>--nogpgcheck</tt> 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.
This is fixed in [https://admin.fedoraproject.org/updates/FEDORA-2014-3290/fedup-0.8.0-4.fc19 fedup-0.8.0-4]. You don't need to re-run {{command|fedup}} - just update and reboot.


== Hardware issues ==
{{Anchor|perlLangExpr-depend-error}}
{{Anchor|arm-beagle-bone}}
=== ARM: HDMI output and USB peripherals not working on Beagle Bone Black ===
<small>[[Common F20 bugs#arm-beagle-bone|link to this item]] - [[rhbug:1012025|Bugzilla: #1012025]]</small>


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 [http://nullr0ute.com/2013/10/serial-console-options-on-the-beagle-bone-black/ here]. The 3.12.5 kernel has full working usb/hdmi/network. It is currently in the [https://alt.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/ 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 [[Architectures/ARM|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.
=== Upgrade fails with dependency issues if {{package|perl-Language-Expr}} is installed ===
<small>[[#perlLangExpr-depend-error|link to this item]] - [[rhbug:992666|Bugzilla: #992666]]</small>


== Software issues ==
If you attempt to upgrade a system with the {{package|perl-Language-Expr}} 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.
{{Anchor|php-zip}}
=== ZIP support in PHP ===
<small>[[Common F20 bugs#php-zip|link to this item]] - [[rhbug:999313|Bugzilla: #999313]]</small>


In Fedora 20, support from ZIP has been dropped from main php package and is now provided in a separate php-pecl-zip package.
Until we resolve this problem, the workaround is to remove {{package|perl-Language-Expr}} 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.


If you need zip support, as for any other extension, run {{command|su -c 'yum install php-zip'}}.
{{Anchor|FedUp-boot-arguments}}
=== Fedup: upgrade can't start without rd.luks.uuid/rd.lvm.lv/rd.md.uuid boot args ===
<small>[[#FedUp-boot-arguments|link to this item]] - [[rhbug:974000|Bugzilla: #974000]]</small>


{{Anchor|seahorse-keyring}}
The system may hang during the reboot after running the command {{command|fedup --network 20}} if these parameters are not specified.
=== GNOME Shell crashes after creating a keyring without a password ===
<small>[[Common F20 bugs#seahorse-keyring|link to this item]] - [[rhbug:1012844|Bugzilla: #1012844]]</small>


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.
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.


An updated [https://admin.fedoraproject.org/updates/FEDORA-2013-22280/mutter-3.10.2-3.fc20,clutter-1.16.2-3.fc20 clutter] package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and [https://admin.fedoraproject.org/updates/FEDORA-2013-22280/mutter-3.10.2-3.fc20,clutter-1.16.2-3.fc20 report to Bodhi] whether it solves the problem. '''However''', note that one tester [[rhbug:1036257|has reported]] that the update causes graphical corruption issues on an Intel video adapter. To test the update, run this command:
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.
<pre>su -c 'yum --enablerepo=updates-testing update --advisory=FEDORA-2013-22280'</pre>


{{Anchor|kde-panorama-crash}}
{{Anchor|tmux-upgrade-issues}}
=== Panorama Stitcher application crashes when launched from system menus in KDE ===
=== Upgrading to Tmux 1.9a-2 results in not being able to connect to sessions created previously ===
<small>[[Common F20 bugs#kde-panorama-crash|link to this item]] - [[rhbug:1040922|Bugzilla: #1040922]]</small>
<small>[[#tmux-upgrade-issues|link to this item]] - [[rhbug:1073119|Bugzilla: #1073119]]</small>


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 [http://extragear.kde.org/apps/kipi/ 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 - {{command|panoramagui image.jpg image2.jpg image3.jpg ...}} - and it will run successfully.
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


An updated [https://admin.fedoraproject.org/updates/FEDORA-2013-23252/digikam-3.5.0-2.fc20 digikam] package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and [https://admin.fedoraproject.org/updates/FEDORA-2013-23252/digikam-3.5.0-2.fc20 report to Bodhi] whether it solves the problem. To test the update, run this command: <pre>su -c 'yum --enablerepo=updates-testing update --advisory=FEDORA-2013-23252'</pre>
{{command|/proc/`pgrep tmux`/exe at}}


{{Anchor|smb-browse-firewalld}}
to connect to your older session so you can migrate it - or downgrade.
=== Cannot browse / discover SMB/CIFS (Windows, Samba) shares with firewalld enabled ===
<small>[[Common F20 bugs#smb-browse-firewalld|link to this item]] - [[rhbug:1038959|Bugzilla: #1038959]]</small>


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.
== Hardware issues ==


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 {{command|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.
== Software issues ==
{{Anchor|dvd-package-source}}
=== DVD not available as a package repository after installation ===
<small>[[#dvd-package-source|link to this item]] - [[rhbug:888307|Bugzilla: #888307]]</small>


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.
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.


We are currently investigating and attempting to come up with a correct resolution for this problem.
A [https://bugzilla.redhat.com/show_bug.cgi?id=888307#c1 comment on the bug] provides a partial workaround which will allow you to install packages from the DVD using the {{command|yum}} utility.


{{Anchor|virt-killed-shutdown}}
{{Anchor|virt-killed-shutdown}}
=== libvirt guests are killed on host shutdown ===
=== libvirt guests are killed on host shutdown ===
<small>[[Common F20 bugs#virt-killed-shutdown|link to this item]] - [[rhbug:1031696|Bugzilla: #1031696]]</small>
<small>[[#virt-killed-shutdown|link to this item]] - [[rhbug:1031696|Bugzilla: #1031696]]</small>


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).
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).
Line 285: Line 359:
{{Anchor|sluggish-qxl-guests}}
{{Anchor|sluggish-qxl-guests}}
=== KVM guests using the qxl graphics driver may display sluggish graphics performance on Fedora 20 hosts ===
=== KVM guests using the qxl graphics driver may display sluggish graphics performance on Fedora 20 hosts ===
<small>[[Common F20 bugs#sluggish-qxl-guests|link to this item]] - [[rhbug:1020393|Bugzilla: #1020393]]</small>
<small>[[#sluggish-qxl-guests|link to this item]] - [[rhbug:1020393|Bugzilla: #1020393]]</small>


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.
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.
Line 301: Line 375:
This disables the 'streaming' feature for the virtual machine, which should completely avoid the problem occurring on any guest operating system.
This disables the 'streaming' feature for the virtual machine, which should completely avoid the problem occurring on any guest operating system.


{{Anchor|gnome-onscreen-keyboards}}
{{Anchor|swap-gpt-partition}}
=== Alternative on-screen keyboards do not work correctly in GNOME ===
=== Error messages about swap activation if swap is on a plain partition on a GPT disk ===
<small>[[Common F20 bugs#gnome-onscreen-keyboards|link to this item]] - [[rhbug:1019073|Bugzilla: #1019073]]</small>
<small>[[#swap-gpt-partition|link to this item]] - [[rhbug:1017509|Bugzilla: #1017509]]</small>
 
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 {{command|swapon}} without any parameters if you wish to check that the partition has been successfully activated.
 
{{Anchor|gnome-js-crashes}}
=== Periodic GNOME Shell crashes, always related to Javascript functions ===
<small>[[#gnome-js-crashes|link to this item]] - [[rhbug:1028813|Bugzilla: #1028813]]</small>
 
Some Fedora 20 users have encountered periodic, apparently random crashes in GNOME Shell. As Shell respawns itself automatically when it crashes, this manifests itself as the Shell and all window decorations disappearing for a few seconds, then returning, and a notification that a crash occurred. If you examine or report the crash information, it is always in a Javascript-related function. Often, but not always, an attempt to report it as a bug will result in it being identified as a duplicate of [[rhbug:1028813|bug #1028813]].
 
This issue is proving very tricky to isolate and fix: it appears to be some sort of memory corruption caused by GNOME's particular user of the Mozilla Javascript engine, which it uses. We are treating it as a high priority issue, but work on debugging it is difficult. GNOME's respawning behaviour means it is only really an inconvenience, but we recognize that it's annoying and we do aim to fix it as soon as we can.
 
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 [[rhbug:1034467|bug #1034467]] (the corresponding Rawhide bug) and [https://bugzilla.mozilla.org/show_bug.cgi?id=972725 Mozilla bug #972725].
 
{{Anchor|hidpi-heuristic-fail}}
=== Desktop elements appear too large in GNOME ("high DPI" mode incorrectly enabled) ===
<small>[[#hidpi-heuristic-fail|link to this item]] - [[rhbug:1025391|Bugzilla: #1025391]]</small>
 
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.


A bug in the {{package|mutter}} window manager for GNOME 3 means that on-screen keyboards other than GNOME's own native one (available from the 'Universal Access' control panel applet or panel menu if enabled) will not work correctly: clicking on a key on the keyboard will not result in the character appearing in the currently-active application.
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.


An updated package that addresses this issue should be available soon.
If you are affected by this issue, running the command {{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.


{{Anchor|speech-dispatcher-crash}}
{{Anchor|speech-dispatcher-crash}}
=== Crash in speech-dispatcher process when launching GNOME or KDE screen readers ===
=== Crash in speech-dispatcher process when launching GNOME or KDE screen readers ===
<small>[[Common F20 bugs#speech-dispatcher-crash|link to this item]] - [[rhbug:995639|Bugzilla: #995639]]</small>
<small>[[#speech-dispatcher-crash|link to this item]] - [[rhbug:995639|Bugzilla: #995639]]</small>


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 {{package|orca}}, KDE's is {{package|jovie}}. Commonly, when launching either of these, you will be notified of a crash in the {{package|speech-dispatcher}} component.
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 {{package|orca}}, KDE's is {{package|jovie}}. Commonly, when launching either of these, you will be notified of a crash in the {{package|speech-dispatcher}} component.
Line 319: Line 411:
{{Anchor|modemmanager-dbus-spam}}
{{Anchor|modemmanager-dbus-spam}}
=== Repeated dbus error messages logged with ModemManager.service disabled ===
=== Repeated dbus error messages logged with ModemManager.service disabled ===
<small>[[Common F20 bugs#modemmanager-dbus-spam|link to this item]] - [[rhbug:1018017|Bugzilla: #1018017]]</small>
<small>[[#modemmanager-dbus-spam|link to this item]] - [[rhbug:1018017|Bugzilla: #1018017]]</small>


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:
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:
Line 330: Line 422:
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 {{command|su -c 'yum remove ModemManager'}}.
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 {{command|su -c 'yum remove ModemManager'}}.


{{Anchor|389-adtrust-crashes}}
{{Anchor|eclipse-gtalk-crash}}
=== 389 Directory Server crashes after enabling FreeIPA Active Directory trust support ===
=== Eclipse crashes with Google Talk plugin installed ===
<small>[[Common F20 bugs#389-adtrust-crashes|link to this item]] - [[rhbug:1041732|Bugzilla: #1041732]] - [[rhbug:1043546|Bugzilla: #1043546]]</small>
<small>[[#eclipse-gtalk-crash|link to this item]] - [[rhbug:1040223|Bugzilla: #1040223]]</small>
 
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.
 
{{Anchor|php-zip}}
 
=== ZIP support in PHP ===
<small>[[#php-zip|link to this item]] - [[rhbug:999313|Bugzilla: #999313]]</small>
 
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 {{command|su -c 'yum install php-zip'}}.
 
{{Anchor|preun-fail}}
=== yum reports duplicate packages installed, older version cannot be easily removed ===
<small>[[#preun-fail|link to this item]] - [[rhbug:989145|Bugzilla: #989145]] - [[rhbug:1028430|Bugzilla: #1028430]] - [[rhbug:1029006|Bugzilla: #1029006]] - [[rhbug:1017493|Bugzilla: #1017493]] - [[rhbug:995158|Bugzilla: #995158]]</small>
 
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:
 
{{command|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:
 
* [[rhbug:989145|kde-settings-kdm-19-23.fc19]]
* [[rhbug:1028430|nscd-2.17-13.fc19]]
* [[rhbug:1029006|lightdm-1.4.0-2.fc18]]
* [[rhbug:1017493|usbmuxd-1.0.8-10.fc19 and usbmuxd-1.0.8-10.fc20]]
* [[rhbug:995158|acpid-2.0.19-4.fc20]]
 
{{Anchor|bluez5-profile}}
 
=== Bluetooth HSP/HFP Profile stops working with upgrade from F19 ===
<small>[[#bluez5-profile|link to this item]] - [[rhbug:1045548|Bugzilla: #1045548]]</small>
 
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 [http://fedoraproject.org//wiki/Changes/Bluez5 migrated] to Bluez5 which has a regression causing HSP/HFP Telephone profile to not be available. This regression is documented in the [http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/5.0/ 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."
 
{{Anchor|font-fuzzy}}
=== Text renders fuzzy with Cantarell font (default Gnome font) ===
<small>[[#font-fuzzy|link to this item]] - [[rhbug:1035486|Bugzilla: #1035486]]</small>
 
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).
 
{{Anchor|rsyslog-cpu-consumption}}
=== rsyslogd consumes 100% CPU time ===
<small>[[#rsyslog-cpu-consumption|link to this item]] - [[rhbug:1047039|Bugzilla: #1047039]]</small>
 
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 {{filename|/var/log/journal}} or {{filename|/run/log/journal}} - will resolve the issue, though of course result in you losing the copy of the system logs accessible via {{command|journalctl}} and other journal-related tools.
 
If you continue to run into the issue, it may be easier simply to remove the {{package|rsyslog}} package and rely on the journal for system logging.
 
== Resolved issues ==
{{Anchor|kde-panorama-crash}}
=== Panorama Stitcher application crashes when launched from system menus in KDE ===
<small>[[#kde-panorama-crash|link to this item]] - [[rhbug:1040922|Bugzilla: #1040922]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2013-23252/digikam-3.5.0-2.fc20 an update to digikam]. Updating your system according to your usual procedures should resolve this issue.}}
 
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 [http://extragear.kde.org/apps/kipi/ 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.
 
{{Anchor|yum-group-errors}}
=== Multiple cases of "group (groupname) does not exist" errors when running yum ===
<small>[[#yum-group-errors|link to this item]] - [[rhbug:1043207|Bugzilla: #1043207]] - [[rhbug:1014202|Bugzilla: #1014202]] - [[rhbug:1043221|Bugzilla: #1043221]] - [[rhbug:1043231|Bugzilla: #1043231]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2013-23627/yum-3.4.3-128.fc20 an update to yum]. Updating your system according to your usual procedures should resolve this issue.}} 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 {{command|yum-config-manager --save --setopt=group_command=objects}}.
 
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.''
 
when running {{command|yum groupinstall (groupname)}}, {{command|yum install @(groupname)}}, or {{command|yum upgrade}} after having once installed any package or environment group with {{command|yum groupinstall (groupname)}} or {{command|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 [[Features/YumGroupsAsObjects|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 [[Features/YumGroupsAsObjects|Fedora 19 "yum groups as objects"]] feature. Probably the safest and most easily reversible was to run:
<pre>
yum-config-manager --save --setopt=group_command=compat
</pre>
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 {{command|yum group remove}} command almost never does what you want in this configuration. Another possible workaround was to run {{command|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.
 
{{Anchor|yum-mark-convert}}
=== ''yum groups mark convert'' command recommended by yum results in many additional packages being installed on ''yum update'' ===
<small>[[#yum-mark-convert|link to this item]] - [[rhbug:1043237|Bugzilla: #1043207]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2013-23627/yum-3.4.3-128.fc20 an update to yum]. Updating your system according to your usual procedures should resolve this issue for future runs of {{command|yum groups mark convert}}. However, if you ran {{command|yum groups mark convert}} with an affected version of yum, the update will not resolve the existing incorrect group markings - unfortunately, we cannot reliably determine cases which have been affected by this bug and automatically fix them, the only safe method is for the system administrator to fix the issue manually, following the instructions below.}}
 
If you run certain yum commands, it may advise you to run a command {{command|yum groups mark convert}}. This is related to the [[Features/YumGroupsAsObjects|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 [https://admin.fedoraproject.org/updates/FEDORA-2013-23627/yum-3.4.3-128.fc20 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 {{command|yum upgrade}}, the result is that, on running {{command|yum upgrade}} after {{command|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 {{command|yum-config-manager --save --setopt<nowiki>=</nowiki>group_command<nowiki>=</nowiki>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 [[#yum-group-errors|the others discussed above]]), you can run {{command|yum group list installed hidden -v}} to print the list of groups that yum now believes is installed, and run {{command|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.
 
{{Anchor|389-freeipa-broken}}
=== Missing attributes in objectclasses in 389 Directory Server (and hence FreeIPA) ===
<small>[[#389-freeipa-broken|link to this item]] - [https://fedorahosted.org/389/ticket/47631 389-ds #47631]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2013-23583 an update to 389-ds-base]. Updating your system according to your usual procedures should resolve this issue. We strongly recommend ensuring 389-ds-base is at least at version 1.3.2.9-1.fc20 before bringing up a Fedora 20-based 389 / FreeIPA server in a live environment.}}


It has been reported that, if you set up a [http://freeipa.org/ FreeIPA] server on Fedora 20 and enable the Active Directory trust support by running {{command|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 {{package|slapi-nis}} plugin. The result of this is that the FreeIPA domain will cease to function correctly, since the LDAP server component is a vital one.
A bug in the schema parser in the version of the [http://directory.fedoraproject.org 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 [http://www.freeipa.org 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.


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.
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.


{{Anchor|389-referint}}
{{Anchor|389-referint}}
=== 389 Directory Server referential integrity plugin fails to work ===
=== 389 Directory Server referential integrity plugin fails to work ===
<small>[[Common F20 bugs#389-referint|link to this item]] - [https://fedorahosted.org/389/ticket/47624 389-ds #47624]</small>
<small>[[#389-referint|link to this item]] - [https://fedorahosted.org/389/ticket/47624 389-ds #47624]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2013-23583 an update to 389-ds-base]. Updating your system according to your usual procedures should resolve this issue. We strongly recommend ensuring 389-ds-base is at least at version 1.3.2.9-1.fc20 before bringing up a Fedora 20-based 389 / FreeIPA server in a live environment.}}


If your configuration of the referint (referential integrity) plugin for the 389 Directory Server is missing these two attributes:
If your configuration of the referint (referential integrity) plugin for the 389 Directory Server is missing these two attributes:
Line 347: Line 566:
nsslapd-pluginContainerScope: dc=example,dc=com
nsslapd-pluginContainerScope: dc=example,dc=com
</pre>
</pre>
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 [https://fedorahosted.org/389/ticket/47621 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.
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 [https://fedorahosted.org/389/ticket/47621 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.
 
{{Anchor|389-adtrust-crashes}}
=== 389 Directory Server crashes after enabling FreeIPA Active Directory trust support ===
<small>[[#389-adtrust-crashes|link to this item]] - [[rhbug:1041732|Bugzilla: #1041732]] - [[rhbug:1043546|Bugzilla: #1043546]]</small>
 
{{Admon/tip|Fix released|These issues were resolved by updates to [https://admin.fedoraproject.org/updates/FEDORA-2013-23583 389-ds-base] and [https://admin.fedoraproject.org/updates/FEDORA-2013-23498 slapi-nis]. Updating your system according to your usual procedures should resolve this issue. We strongly recommend ensuring 389-ds-base and slapi-nis are fully updated before bringing up a Fedora 20-based 389 / FreeIPA server in a live environment.}}
 
It was reported that, if you set up a [http://freeipa.org/ FreeIPA] server on Fedora 20 and enable the Active Directory trust support by running {{command|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 {{package|slapi-nis}} plugin. The result of this was that the FreeIPA domain will cease to function correctly, since the LDAP server component is a vital one.
 
{{Anchor|fedup-07-fail}}
=== Upgrade to Fedora 20 with fedup 0.7 fails, reboots shortly after booting the System Upgrade option ===
<small>[[#fedup-07-fail|link to this item]]</small>
 
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:
<pre>
su -c 'mv /var/lib/fedora-upgrade /var/lib/system-upgrade'
su -c 'mv /var/tmp/fedora-upgrade /var/tmp/system-upgrade'
</pre>
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 {{filename|/var/lib/fedora-upgrade}} and {{filename|/var/tmp/fedora-upgrade}} directories exist, and if so, remove them: they are no longer needed and are simply occupying disk space.
 
{{Anchor|fedup-18-gpg}}
{{Anchor|fedup-19-gpg}}
=== Upgrade to Fedora 20 with fedup 0.8 fails due to GPG key problems ===
<small>[[#fedup-18-gpg|link to this item]] - [[rhbug:1040689|Bugzilla: #1040689]]</small>
 
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|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''.
 
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 {{command|yum update}} to update packages from them.
 
{{Anchor|gnome-onscreen-keyboards}}
=== Alternative on-screen keyboards do not work correctly in GNOME ===
<small>[[#gnome-onscreen-keyboards|link to this item]] - [[rhbug:1019073|Bugzilla: #1019073]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2013-23948/mutter-3.10.2-6.fc20 an update to mutter]. Updating your system according to your usual procedures should resolve this issue.}}
 
A bug in the {{package|mutter}} 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.
 
{{Anchor|smb-browse-firewalld}}
=== Cannot browse / discover SMB/CIFS (Windows, Samba) shares with firewalld enabled ===
<small>[[#smb-browse-firewalld|link to this item]] - [[rhbug:1038959|Bugzilla: #1038959]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2013-23712/NetworkManager-0.9.9.0-22.git20131003.fc20 an update to NetworkManager]. Updating your system according to your usual procedures (and restarting NetworkManager or rebooting) should resolve this issue.}}
 
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.
 
{{Anchor|mypasswordsafe-crash}}
=== MyPasswordSafe crashes ===
<small>[[#mypasswordsafe-crash|link to this item]] - [[rhbug:1042667|Bugzilla: #1042667]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/MyPasswordSafe-0.6.7-19.20061216.fc20 an update to MyPasswordSafe]. Updating your system according to your usual procedures should resolve this issue.}}
 
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 [[rhbug:1042667|bug #1042667]].
 
{{Anchor|selinux-config-disable}}
=== Disabling SELinux via configuration file failed with libselinux-2.2.1-4.fc20 ===
<small>[[#selinux-config-disable|link to this item]] - [[rhbug:1046470|Bugzilla: #1046470]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/libselinux-2.2.1-6.fc20 an update to libselinux]. Updating your system according to your usual procedures and rebooting should resolve this issue.}}
 
After the release of Fedora 20, [https://admin.fedoraproject.org/updates/FEDORA-2013-23698/libselinux-2.2.1-4.fc20 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 {{filename|/etc/selinux/config}}. If you set:
<pre>
SELINUX=disabled
</pre>
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.
 
{{Anchor|cups-share-hang}}
=== CUPS hangs on shutdown (causing a long wait on system shutdown) if printer sharing is enabled ===
<small>[[#cups-share-hang|link to this item]] - [[rhbug:1044602|Bugzilla: #1044602]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2014-0151/cups-1.7.0-9.fc20 an update to cups]. Updating your system according to your usual procedures should resolve this issue.}}
 
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 {{command|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 ===
<small>[[#arm-beagle-bone|link to this item]] - [[rhbug:1012025|Bugzilla: #1012025]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2014-0696/kernel-3.12.7-300.fc20 an update to the kernel]. Updating your system according to your usual procedures should resolve this issue.}}
 
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 [http://nullr0ute.com/2013/10/serial-console-options-on-the-beagle-bone-black/ 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 [[Architectures/ARM|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.
 
{{Anchor|seahorse-keyring}}
=== GNOME Shell crashes after creating a keyring without a password ===
<small>[[#seahorse-keyring|link to this item]] - [[rhbug:1012844|Bugzilla: #1012844]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by updates to the GNOME package set. Updating your system according to your usual procedures should resolve this issue.}}
 
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.
 
{{Anchor|cant-unlock-screenlock}}
{{Anchor|systemd-nologin-creation}}
=== Sudden inability to unlock screen, or log in to running system (caused by creation of /var/run/nologin) ===
<small>[[#systemd-nologin-creation|link to this item]] - [[rhbug:1043212|Bugzilla: #1043212]]</small>
 
{{Admon/tip|Fix released|This issue was resolved by [https://admin.fedoraproject.org/updates/FEDORA-2014-2690/systemd-208-14.fc20 an update to systemd]. Updating your system according to your usual procedures should resolve this issue.}}
 
The systemd version (208-9.fc20) included with Fedora 20 can, on some systems, cause the file {{filename|/var/run/nologin}} (or - reports differ - {{filename|/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 {{command|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 {{filename|/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.


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.
[[Category:Common bugs]]

Latest revision as of 23:59, 14 March 2018

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.

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
    1. a summary of the problem
    2. any known workarounds
    3. an assessment on the impact to Fedora users

For reference, you can query Bugzilla for bugs tagged CommonBugs:

  • CommonBugs? (bugs with CommonBugs keyword, but do not yet have a link to one or more Common Bugs pages)
  • CommonBugs+(bugs with CommonBugs keyword and contain a link to one or more Common Bugs pages)


Major issues

RPM scriptlets fail during updates

link to this item - Bugzilla: #1054350

Fix released
This issue was resolved by selinux-policy-3.12.1-117.fc20 an update to SELinux policy. It however requires the following workaround if you updated to selinux-policy-3.12.1-116.fc20 which contained the bug. If you have a previous version installed, you are not affected and can simply update to the new version without issue.

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.

Sample output:

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

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. 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

This should update dracut to the fixed version and re-generate the initramfs to include the necessary tools. Now your system should boot normally (though an SELinux relabel may run on the first boot).

Crash when switching from a complete mirror repository to a DVD-based repository: NoSuchGroup: 3d-printing

link to this item - Bugzilla: #1033749

Fix available
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 here: in short, simply pass the parameter inst.updates=http://bcl.fedorapeople.org/updates/1033749.img to the installer.

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

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 rootfiles 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.

Installation issues

Installer crashes with No such file or directory: '/dev/md' if MD-RAID set is referred to by device node name in /etc/fstab

link to this item - Bugzilla: #980267

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/md0p1 or /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

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.

Booting previously installed OS (including Windows) from the Fedora bootloader menu may fail after UEFI installation

link to this item - Bugzilla: #986731

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 efibootmgr showed:

[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

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.

Exiting shell from rescue mode does not return to menu or reboot, but sticks at Pane is dead

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.

Network installation with Authoring and Publishing group selected fails

link to this item - Bugzilla: #959696

Due to an unmarked conflict between two texlive-related packages (ht and texlive-tex4ht-bin), 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

link to this item - Bugzilla: #1047904

Fix available
There is an updates image for the installer which fixes this issue available at https://www.happyassassin.net/updates/updates-1047904.img. Instructions on using an updates image are available here: in short, simply pass the parameter inst.updates=https://www.happyassassin.net/updates/updates-1047904.img to the installer.

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

link to this item - Bugzilla: #978430

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 --efi parameter.

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

link to this item - Bugzilla: #874381

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

link to this item - Bugzilla: #967682

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

link to this item - Bugzilla: #840160

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

link to this item - Bugzilla: #965797

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

link to this item - Bugzilla: #1063540

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 issues

Upgrade fails if /var is a separate partition

link to this item - Bugzilla: #1045168

If the /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.

Upgrade fails with dependency issues if perl-Language-Expr is installed

link to this item - Bugzilla: #992666

If you attempt to upgrade a system with the perl-Language-Expr 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 perl-Language-Expr 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

link to this item - Bugzilla: #974000

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

link to this item - Bugzilla: #1073119

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

/proc/pgrep tmux/exe at

to connect to your older session so you can migrate it - or downgrade.

Hardware issues

Software issues

DVD not available as a package repository after installation

link to this item - Bugzilla: #888307

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 yum utility.

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.

Error messages about swap activation if swap is on a plain partition on a GPT disk

link to this item - Bugzilla: #1017509

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.

Periodic GNOME Shell crashes, always related to Javascript functions

link to this item - Bugzilla: #1028813

Some Fedora 20 users have encountered periodic, apparently random crashes in GNOME Shell. As Shell respawns itself automatically when it crashes, this manifests itself as the Shell and all window decorations disappearing for a few seconds, then returning, and a notification that a crash occurred. If you examine or report the crash information, it is always in a Javascript-related function. Often, but not always, an attempt to report it as a bug will result in it being identified as a duplicate of bug #1028813.

This issue is proving very tricky to isolate and fix: it appears to be some sort of memory corruption caused by GNOME's particular user of the Mozilla Javascript engine, which it uses. We are treating it as a high priority issue, but work on debugging it is difficult. GNOME's respawning behaviour means it is only really an inconvenience, but we recognize that it's annoying and we do aim to fix it as soon as we can.

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)

link to this item - Bugzilla: #1025391

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

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 orca, KDE's is jovie. Commonly, when launching either of these, you will be notified of a crash in the speech-dispatcher component.

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'.

Eclipse crashes with Google Talk plugin installed

link to this item - Bugzilla: #1040223

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

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'.

yum reports duplicate packages installed, older version cannot be easily removed

link to this item - Bugzilla: #989145 - Bugzilla: #1028430 - Bugzilla: #1029006 - Bugzilla: #1017493 - Bugzilla: #995158

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:

Bluetooth HSP/HFP Profile stops working with upgrade from F19

link to this item - Bugzilla: #1045548

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)

link to this item - Bugzilla: #1035486

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

link to this item - Bugzilla: #1047039

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 /var/log/journal or /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.

If you continue to run into the issue, it may be easier simply to remove the rsyslog package and rely on the journal for system logging.

Resolved issues

Panorama Stitcher application crashes when launched from system menus in KDE

link to this item - Bugzilla: #1040922

Fix released
This issue was resolved by an update to digikam. Updating your system according to your usual procedures should resolve this issue.

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

link to this item - Bugzilla: #1043207 - Bugzilla: #1014202 - Bugzilla: #1043221 - Bugzilla: #1043231

Fix released
This issue was resolved by an update to yum. Updating your system according to your usual procedures should resolve this issue.

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 {{{1}}}.

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.

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 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

link to this item - Bugzilla: #1043207

Fix released
This issue was resolved by an update to yum. Updating your system according to your usual procedures should resolve this issue for future runs of yum groups mark convert. However, if you ran yum groups mark convert with an affected version of yum, the update will not resolve the existing incorrect group markings - unfortunately, we cannot reliably determine cases which have been affected by this bug and automatically fix them, the only safe method is for the system administrator to fix the issue manually, following the instructions below.

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)

link to this item - 389-ds #47631

Fix released
This issue was resolved by an update to 389-ds-base. Updating your system according to your usual procedures should resolve this issue. We strongly recommend ensuring 389-ds-base is at least at version 1.3.2.9-1.fc20 before bringing up a Fedora 20-based 389 / FreeIPA server in a live environment.

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

link to this item - 389-ds #47624

Fix released
This issue was resolved by an update to 389-ds-base. Updating your system according to your usual procedures should resolve this issue. We strongly recommend ensuring 389-ds-base is at least at version 1.3.2.9-1.fc20 before bringing up a Fedora 20-based 389 / FreeIPA server in a live environment.

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

link to this item - Bugzilla: #1041732 - Bugzilla: #1043546

Fix released
These issues were resolved by updates to 389-ds-base and slapi-nis. Updating your system according to your usual procedures should resolve this issue. We strongly recommend ensuring 389-ds-base and slapi-nis are fully updated before bringing up a Fedora 20-based 389 / FreeIPA server in a live environment.

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 slapi-nis 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

link to this item

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/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 to Fedora 20 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. 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 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.

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

link to this item - Bugzilla: #1019073

Fix released
This issue was resolved by an update to mutter. Updating your system according to your usual procedures should resolve this issue.

A bug in the mutter 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.

Cannot browse / discover SMB/CIFS (Windows, Samba) shares with firewalld enabled

link to this item - Bugzilla: #1038959

Fix released
This issue was resolved by an update to NetworkManager. Updating your system according to your usual procedures (and restarting NetworkManager or rebooting) should resolve this issue.

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.

MyPasswordSafe crashes

link to this item - Bugzilla: #1042667

Fix released
This issue was resolved by an update to MyPasswordSafe. Updating your system according to your usual procedures should resolve this issue.

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

link to this item - Bugzilla: #1046470

Fix released
This issue was resolved by an update to libselinux. Updating your system according to your usual procedures and rebooting should resolve this issue.

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:

SELINUX=disabled

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

link to this item - Bugzilla: #1044602

Fix released
This issue was resolved by an update to cups. Updating your system according to your usual procedures should resolve this issue.

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

link to this item - Bugzilla: #1012025

Fix released
This issue was resolved by an update to the kernel. Updating your system according to your usual procedures should resolve this issue.

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

link to this item - Bugzilla: #1012844

Fix released
This issue was resolved by updates to the GNOME package set. Updating your system according to your usual procedures should resolve this issue.

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)

link to this item - Bugzilla: #1043212

Fix released
This issue was resolved by an update to systemd. Updating your system according to your usual procedures should resolve this issue.

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.