This page documents common bugs in Fedora 22 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.
Fedora 22 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 22 pre-releases. Issues that are fixed will be removed from the page once a fix is available (for instance, an issue that affects the Beta but is fixed in the final release will be removed at the time of that release).
Release Notes
Read the F22_Alpha_release_announcement for specific information about changes in Fedora 22 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. Common bugs instructions provides guidance on how to add an entry to the page correctly, but the most important thing is to make sure that the bug is listed - don't worry if you don't get the format quite right, we can clean it up later.
- 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)
Installation issues
Default language for installation not chosen according to location
link to this item - Bugzilla: #1209927
Recent Fedora releases have guessed an appropriate language for the installer based on the apparent physical location of the system (based on its public internet IP address, using a system called 'geolocation'). For instance, if the system appears to be in France according to the IP address, the first screen of the installer should appear with French as the default language choice.
In Fedora 22 Beta, this feature is broken, and the default language on the Welcome screen is always U.S. English.
This bug will be resolved for the final release of Fedora 22.
Upgrade issues
GNOME issues
KDE issues
Network issues
Hardware issues
ARM issues
Fedora Server issues
Rolekit fails to deploy a Domain Controller on a virtual machine
Creation of a Domain Controller role requires the system to have a sufficient amount of entropy available to securely create the keys for the included certificate authority and Kerberos key distribution center. It is very common when deploying on a virtual machine that has just been created that there will not be sufficient entropy available, which will result in the Domain Controller deployment timing out waiting on /dev/random and then failing with error code 256.
On VM hosts that support it (such as KVM on Fedora 20 and later or RHEL 7.1 and later), it is recommended to create the VM using the virt-RNG device (which the Fedora Server 22 guest will automatically detect). This will allow it to collect entropy from the host machine and should reduce the likelihood of encountering this issue. As a workaround (if you do not have a host capable of providing entropy), you can also run su -c '/usr/sbin/rngd -r /dev/urandom' to make the system use the less-secure /dev/urandom entropy device.
For an in-depth explanation of entropy issues and how they can be resolved, see this excellent blog post.
Fedora Cloud issues
Other issues
link to this item - Bugzilla: #1211887
For a short period of time a particular version of the 
grubby
The broken grubby never reached stable state, and has been replaced by a fixed version, but if you ever encountered this bug, it is possible that future kernel updates will continue to get the nonsense names even though you install the fixed grubby. If you find yourself in this situation, there are two options. You can edit the configuration file - /boot/efi/EFI/fedora/grub.cfg on a UEFI system, or /boot/grub2/grub.cfg on a BIOS system - and replace the nonsense string with a name in the normal format. Or you can take a backup copy of the same file and run grub2-mkconfig -o /boot/grub2/grub.cfg or grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg to re-generate it from scratch.