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)
Multiple issues with resizing existing volumes during installation
Multiple bugs have been reported in Fedora 20 Beta which are related to resizing existing storage volumes as a part of the installation process. Problematic scenarios include specifying a size for a partition which is larger than it could possibly be, attempting to resize partitions at the end of the disk that leave no padding space after the partition, choosing a new size for a volume and then changing your mind and returning it to the previous size, and others.
So far as we are aware, all the bugs manifest as crashes - either immediately on trying the problematic operation, or during the first stage of installation - and none of them result in a dangerous or incorrect resize operation actually being run, so there is no known risk of data loss. Nevertheless, we particularly stress the standard advice not to install Fedora 20 Beta to a system that contains existing data of value to you, and strongly advise you not to attempt to resize storage volumes that contain data of value to you using the Fedora 20 Beta installer.
Btrfs /boot partition results in a kernel panic after kernel update
Placing /boot on a btrfs volume results in a kernel panic on reboot. Running either of the below commands (based on your setup) after a kernel update will fix this issue.
grub2-mkconfig -o /boot/grub2/grub.cfg
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Then reboot your machine.
ARM: Beagle Bone Black HDMI issues
Some testers have reported that attempting to run the Beagle Bone Black over HDMI doesn't currently work. At the moment to use the Beagle Bone Black you need a serial console. As on Fedora 20 Beta TC4 the Network/MMC/Serial console currently works and the BBone Black successfully boots. Further kernel updates to resolve the other outstanding issues will be forthcoming.
Non-US keyboard layouts not used at console
If you pick a non-US keyboard layout as the default or only layout during Fedora 20 Beta installation, that choice won't be honored after installation in virtual terminals or when decrypting filesystems during the boot process. Graphical sessions, however, will use the keyboard layout picked during installation.
Re-doing keyboard layout selection after installation may help to work around this issue, but we are still investigating the precise cause, workarounds, and solution.
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.
ZIP support in PHP
In Fedora 20, support from ZIP have 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'
KDE crashes when in a VM
When installing Fedora 20 Beta with the KDE desktop to a KVM-based virtual machine using the qxl virtual graphics adapter and driver, KDE will likely crash shortly after login. This can be worked around by disabling Desktop Effects. (Alt+Shift+F12) toggles desktop effects, and you can set them not to be enabled by default in the KDE Control Center.
An updated xorg-x11-drv-qxl package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, run this command:
su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-qxl'
KDE live wireless networking doesn't work
When using a Fedora 20 Beta KDE live image, the plasma-nm applet doesn't connect to available networks. The workaround is to logout and then log back in and connect.
GNOME Shell crashes after creating a keyring without a password
In Fedora 20 Beta 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. A patch is currently pending from upstream to fix this issue.
GNOME initial setup tool crashes if you cancel online account creation
If, during the 'initial setup' wizard that appears on first boot after a Fedora 20 Beta GNOME install, you enter the module for creating an 'online account' then change your mind and cancel the account creation, the tool may crash. This may result in the tool running again on your next boot, which may force you to create a second user account. If this happens to you, you can safely delete one or other account once you have successfully completed the wizard, and it will not run again.
Other than this there should be no significant consequences of the bug: the crash occurs quite late in the process, and no actions from earlier in the process should be lost.
Fedora services configuration tool (system-config-services) crashes on startup
Several testers have reported that the Fedora tool for configuring system services,
system-config-services, crashes on startup in Fedora 20 Beta. There is no known direct workaround that makes it possible to use the tool, but you can use the
systemctl command to manipulate services from the command line: see
man systemctl for more details.