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_Beta_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
Liveinst run from terminal emulator on Plasma fails to start
link to this item - Bugzilla: #1222262
Liveinst run from command line fails to start because LANGUAGE variable is empty. To run liveinst kickstart or --lang parameter must be provided. Installation can be also run by using graphical icon from menu.
Upgrade issues
System does not always reboot automatically when FedUp upgrade is complete
link to this item - Bugzilla: #1209941
If you use FedUp to upgrade to Fedora 22, you may find that once the upgrade is complete, the system does not reboot automatically from the upgrade environment, usually hanging while unmounting filesystems. At this point the upgrade has completed and it is quite safe to reboot manually.
GNOME issues
Totem (Videos) crashes on startup
link to this item - Bugzilla: #1200559
After a fresh installation of Fedora 22 Beta, the GNOME video player Totem (which shows as 'Videos' in the application list) will likely crash when you try to run it. To work around this issue, you can launch it from a console with a path to a video file - e.g. totem ~/Videos/my_awesome_video.ogg. It may also work if launched indirectly by attempting to open a video file from the file manager or web browser.
This issue will be resolved for the final release of Fedora 22.
Plasma (KDE) issues
No system update notifications in Plasma
link to this item - Bugzilla: #1206760
When using the Plasma desktop in Fedora 22 Beta, you will not receive notifications of available system updates by default, as is intended to happen. You can simply check for updates manually every so often, or you can enable update checking from System tray settings: go to the General section, and click the item labelled Software Updates in Extra items.
This issue is expected to be resolved for the final release of Fedora 22.
Initial setup sometimes starts in text mode instead of in graphic
link to this item - Bugzilla: #1185447
Sometimes happens that initial setup starts in text mode instead of graphical mode. In that case you can proceed with text mode or disable initial-setup-text.service by running command systemctl disable initial-setup-text.service as root and restart. The graphical initial setup should be provided then.
Network issues
Hardware issues
Mouse pointer moves too slowly in Gnome
link to this item - Bugzilla: #1195886
The mouse pointer moves too slowly in Gnome once logged in, and adjusting the settings in the Gnome control panel doesn't help. This is caused by the change to libinput. There are some suggestions you can try in the bug report, or you can try removing the xorg-x11-drv-libinput package to use the xorg-x11-drv-evdev driver instead with dnf remove xorg-x11-drv-libinput and dnf install xorg-x11-drv-evdev.
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.
Arabic, Cyrillic, and Hebrew characters not displayed in console
link to this item - Bugzilla: #1209460
The default console font in Fedora 22 has been changed to one ('eurlatgr') which provides greater coverage for Latin and Greek characters, but at the cost of Arabic, Cyrillic and Hebrew characters being dropped. It was intended that installations in languages which use the Arabic, Cyrillic or Hebrew characters should get a more appropriate default console font, but this has not yet been implemented.
Once the system is booted, the setfont command can be used to change the console font - e.g. setfont latarcyrheb-sun16 to use the old default. The font can be changed permanently by editing the file /etc/vconsole.conf and changing the line FONT="somefont" - e.g. change it from FONT="eurlatgr" to FONT="latarcyrheb-sun16".
This change applies only to new installations; the font used by existing installations will not be changed on upgrade.