Common F20 bugs
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.
Read the F20_Alpha_release_announcement for specific information about changes in Fedora 20 and other general information.
My bug is not listed
Not every bug is listed in this page, but Bugzilla should be a comprehensive database of known bugs. This page is a sampling of the bugs most commonly discussed on our mailing lists and forums.
To see if your bug has already been reported, you can search Bugzilla. If it has not yet been reported, we encourage you to do so to help improve Fedora for yourself and others. A guide to Bugs and feature requests has been prepared to assist you.
If you believe an already-reported bug report should be added to this page because it is commonly encountered, you can:
- Add it yourself, if you have wiki access. Please follow the style and guidelines explained in the comments in the page source.
- Or, add the CommonBugs keyword to the bug report. Someone from the QA team will then inspect the issue to determine whether the bug should be listed as a common bug. To expedite your request, please add a comment to the bug that includes
- a summary of the problem
- any known workarounds
- an assessment on the impact to Fedora users
For reference, you can query Bugzilla for bugs tagged CommonBugs:
- CommonBugs? (bugs with CommonBugs keyword, but do not yet have a link to this page)
- CommonBugs+(bugs with CommonBugs keyword and contain a link to this page)
Live installer crashes on adding a keyboard layout
The Fedora 20 Alpha live installer will crash immediately if you visit the Keyboard spoke and attempt to add a layout. This bug and the fix for it were introduced and identified shortly before Alpha release, and there was not quite time to get the fix included.
anaconda-20.19 fixes the bug: if you want to do a live install and modify the keyboard layout configuration during installation, install that version of anaconda into the live system prior to running the installer. It is not available as an update at present, but you can download and install the build directly from the link.
Otherwise, you can simply defer keyboard configuration until post-install, or use a traditional installer image instead of the live image.
Installer crashes when creating a custom btrfs layout or assigning / mount point to an existing volume
Multiple reports indicate that the Fedora 20 Alpha installer will crash with the error AttributeError: 'NoneType' object has no attribute 'id' in at least two general scenarios:
- If you set the storage type drop-down on Installation Options to btrfs, enter custom partitioning, and create a partition
- If you assign the / mount point to an existing ext4 partition (or likely any existing storage volume) during custom partitioning
python-blivet-0.22-1.fc20 fixes this issue, but was not included in Fedora 20 Alpha. You can work around the bug by booting a live image and updating to that build of python-blivet before running the live installer. Otherwise, there is no exact workaround for this crash besides handling partitioning in a way which avoids either of those actions. This issue will be resolved for the release of Fedora 20 Beta.
Installer crashes if NFS ISO repository is used
Testing suggests that the Fedora 20 Alpha installer is likely to crash with the error KeyError: 'name' if you attempt to use an NFS repository containing an ISO file as an install source. As we currently understand the issue, an NFS repository containing a full repository tree (rather than an ISO file) should work, and FTP and HTTP repositories have also been tested to work: please use one of these or another method instead of NFS ISO for Alpha testing.
Apple EFI Macs: EFI install alongside existing EFI installed OS (including OS X) results in you have not created a bootloader stage1 target device error
If you try to do a native UEFI install of Fedora 20 alongside a native UEFI install of OS X and re-use the existing EFI system partition, the installer will incorrectly consider the existing EFI system partition as invalid and report that you have not created a bootloader stage1 target device. Unfortunately, the Fedora automatic partitioning algorithm will actually attempt to re-use the EFI system partition, and so you will run into this bug in any Fedora 20 installation attempt where you use the automatic partitioning algorithm and do not choose to delete the existing EFI system partition.
Practically speaking, there are a few different approaches to dealing with this problem. If you do not mind losing your OS X installation, you can simply choose to delete it (including the EFI system partition), and let Fedora occupy the rest of the disk. Fedora should create a new EFI system partition and install successfully.
If you wish to preserve your OS X installation, install Fedora 20 Final, and dual boot, you must use the installer's 'custom partitioning' path. Make sure to leave the existing EFI system partition intact, but do not set a mount point for it. Do not use the Create partitions for me button. Instead, manually create a new EFI system partition, and set it to be mounted at
/boot/efi. Manually create other partitions as usual. Complete custom partitioning, and your installation should proceed successfully. See the Installation Guide for general instructions on the partitioning process, if necessary.
You could also try installing Fedora 18 or Fedora 19 Beta. These should allow you to use automatic partitioning to install alongside OS X, assuming you do not run into any other bugs they may have contained. You could then upgrade to Fedora 20 with yum. You will still wind up with two EFI system partitions in this case.
Updating system with GNOME Software fails
Some testers have reported that attempting to update a Fedora 20 Alpha system using the new GNOME Software application fails, with the error updates-plugin-WARNING **: failed to download: The backend exited unexpectedly. visible in system logs. If you are affected by this, we recommend updating using the older
gpk-update-viewer utility for now, or simply
yum from a console.
Removing applications with GNOME Software fails
Some testers have reported that attempting to remove software from a Fedora 20 Alpha system using the new GNOME Software application fails, with segmentation fault of the GNOME Software application. If you are affected by this, we recommend removing software using
yum from a console.
Disappearing mouse cursor
After logging in to a desktop in Fedora 20 Alpha, the mouse cursor can become invisible. The mouse still functions, but can't be seen. This has been seen occasionally in testing on bare metal and more often in testing on virtual machines. It definitely affects GNOME and may affect other desktop environments.
Moving to another tty and back typically resolves the issue.
Wired connection indicator
In Fedora 20 Alpha, for wired connections, the network-manager-applet displays an 'X' over the network icon, regardless of connectivity. The fix for this issue has been pushed to stable, but we are noting it here as it is highly visible on initial installation. Note that the fix for this issue is that no connection indicator will be shown at all for wired connections after update: this is a GNOME 3.10 design decision, not a bug in itself. A connection indicator will still be shown for all forms of wireless connection.
To fix this issue simply run
su -c 'yum update NetworkManager' and then reboot the system or simply
su -c 'systemctl restart NetworkManager.service'.