Common F22 bugs

Click here to set up this language box

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.

Pre-release version
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
  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 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.

Live installer not fully translated

link to this item - Bugzilla: #1209563

If you install Fedora 22 Beta from a live image and choose a language other than English, many elements of the installer will not be translated even if a translation has been provided by our fine L10N team. This is due to a rather tricky conjunction of circumstances which is analyzed in detail in the bug report. The only known workaround is to install from a non-live image (or, of course, use the minimally-translated installer if your English is good enough). The bug only affects the installer; the installed system will be as well or poorly translated as would be the case with any other installation process.

Although resolving it is not straightforward, we strongly hope to have this fixed for the final release of Fedora 22.

Installer crashes or does something unexpected when re-using existing encrypted LVM disk layout

link to this item - Bugzilla: #1208979 - Bugzilla: #1210254

Several testers have reported either an installer crash or unexpected result when installing Fedora 22 and re-using existing encrypted LVM volumes. Depending on the exact existing configuration, the installer may crash, or it may create a 'double encrypted' configuration.

Several fixes for these cases should be included in the final release of Fedora 22.

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.

Fedora Server issues

Rolekit fails to deploy a Domain Controller on a virtual machine

link to this item

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.

Other issues

Bootloader menu entry names are nonsense

link to this item - Bugzilla: #1211887

For a short period of time a particular version of the grubby package was available in the updates-testing repository which contained a significant bug. If you ever updated your kernel while grubby-8.39-1.fc22 was installed, the new boot menu entry was likely given a short nonsense string for a name.

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.