From Fedora Project Wiki

(System hang when creating a user during GNOME first boot in basic graphics mode|1206404)
(Installer might not redraw its progress bar in KDE|1210042)
Line 14: Line 14:


== Installation issues ==
== Installation issues ==
{{Common bugs issue|liveinst-on-kde-fails|Liveinst run from terminal emulator on Plasma fails to start|1222262}}
{{Common bugs issue|anaconda-redraw-progress|Installer might not redraw its progress bar in KDE|1210042}}
 
In certain environments (seen in KDE, might affect some others as well), sometimes the installer does not redraw its progress bar properly and seems stuck, even though the installation is making progress sucessfuly. This seems to be an issue with the widget toolkit or the display manager.


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.
If the progress bar seems stuck for a long time and there's no progress indicated elsewhere, you can try to open and close the root password dialog, visible from the installation overview screen. You can also try to Alt+Tab between the installer and some other windows, to force it to redraw.


{{Common bugs issue|anaconda-minimal-partition-size-netinst|Installer does not correctly compute the minimal required partition size when using network installation|1224048}}
{{Common bugs issue|anaconda-minimal-partition-size-netinst|Installer does not correctly compute the minimal required partition size when using network installation|1224048}}
Line 25: Line 27:


To be safe from this issue, please don't try to set an extremely small root partition.
To be safe from this issue, please don't try to set an extremely small root partition.
{{Common bugs issue|liveinst-on-kde-fails|Liveinst run from terminal emulator on Plasma fails to start|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.


{{Common bugs issue|anaconda-hard-to-remove-snapshotted-partitions|Installer does not allow convenient removal of volumes including snapshots (btrfs, LVM) in manual partitioning|1185117}}
{{Common bugs issue|anaconda-hard-to-remove-snapshotted-partitions|Installer does not allow convenient removal of volumes including snapshots (btrfs, LVM) in manual partitioning|1185117}}

Revision as of 14:02, 25 May 2015

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_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
    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

Installer might not redraw its progress bar in KDE

link to this item - Bugzilla: #1210042

In certain environments (seen in KDE, might affect some others as well), sometimes the installer does not redraw its progress bar properly and seems stuck, even though the installation is making progress sucessfuly. This seems to be an issue with the widget toolkit or the display manager.

If the progress bar seems stuck for a long time and there's no progress indicated elsewhere, you can try to open and close the root password dialog, visible from the installation overview screen. You can also try to Alt+Tab between the installer and some other windows, to force it to redraw.

Installer does not correctly compute the minimal required partition size when using network installation

link to this item - Bugzilla: #1224048

If you use the network install image (netinst), the installer will not always correctly warn you when your root partition is too small to contain the installed system. If the disk space runs out during package installation, anaconda reboots the machine without a warning, and the partial Fedora installation is broken and unusable. If this happens, please repeat the installation, but assign more space to the root partiton. For example, the absolute minimum for a Workstation package set is 6 GiB.

In the vast majority of cases, this issue does not affect Live or DVD (offline) installations. There is a very slight chance that if you set the partition to be almost exactly the same size as is the installed package set, the filesystem metadata will occupy enough space so that the installed system does not fit into the free space.

To be safe from this issue, please don't try to set an extremely small root partition.

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.

Installer does not allow convenient removal of volumes including snapshots (btrfs, LVM) in manual partitioning

link to this item - Bugzilla: #1185117

If you enter manual partitioning in the installer (a dialog where you're able to create your own partition layout, as opposed to a automatic partitioning dialog where you can only remove partitions), and you have some existing partitions which include a large number of snapshots (usually related to btrfs or LVM), the installer displays every single such snapshot as a separate system tree. In certain cases, it might be very difficult and tiring to remove some of those partitions including snapshots and keep others intact, because it would involve clicking and manually removing each of those partitions. The installer is not currently able to let you conveniently work with snapshotted volumes, or disks with ten or hundreds of partitions.

If you do not need to create your own partition layout and you don't need to preserve certain logical volumes/btrfs subvolumes, you can use the automatic partitioning dialog to delete unneeded partitions easily. In other cases, please use external tools to configure your disk layout to your needs first, and run Fedora installer after that.


Upgrade issues

Upgrade from Fedora 20 complains about missing GPG keys with an outdated fedora-release

link to this item - Bugzilla: #1220358

If you want to upgrade Fedora 20 to Fedora 22 using fedup, you need to update fedora-release package to version fedora-release-20-4 first. Otherwise you'll encounter an error about missing GPG keys.

Please note that you should always fully update your system before starting a distribution upgrade.

Upgrade from Fedora 21 hangs at boot with an outdated systemd

link to this item - Bugzilla: #1223735

If you want to upgrade Fedora 21 to Fedora 22 using fedup, you need to update systemd package to version systemd-216-24.fc21 first. Otherwise the upgrade process will hang and not start. There is no data loss, just reboot, update systemd, and start fedup again.

Please note that you should always fully update your system before starting a distribution upgrade.

GNOME issues

PackageKit (GNOME Software, GNOME offline upgrades) ignores kernel modules updates from RPMFusion (VirtualBox, Nvidia driver, NDISwrapper, etc)

link to this item - Bugzilla: #1205649

If you have installed a kernel module from RPMFusion repository (the most common are VirtualBox or the proprietary Nvidia graphics driver), you will not see updates to these kernel modules in PackageKit package manager, and therefore neither in GNOME Software application. This will also make main kernel updates ignored as well.

In order to install latest Linux kernel (very recommended due to occasional security issue) and the relevant modules from RPMFusion, please regularly run sudo dnf update from a terminal.

System hang when creating a user during GNOME first boot in basic graphics mode

link to this item - Bugzilla: #1206404

If you run the installer in "basic graphics" mode and do not create a user during the installation, you'll be offered to create the user the first time GNOME starts in the installed system. However, due to an issue with the basic graphics mode, the system will show you just an empty screen after the user is created, instead of logging you in or showing you the login screen. You'll need to reboot your computer, and then you'll be able to log in with your created user.

Plasma (KDE) issues

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

No network connection in VM when both host and guest installed from a Live image

link to this item - Bugzilla: #1146232

If you install Fedora from a Live image, and then create a virtual machine on it and install another Fedora from a Live image as a guest, your networking in guest will probably not work. The is reason is that libvirt virtual network address ranges are the same both in the host and the guest and clash. This does not happen if you install the libvirt packages in guest manually at some point later (it is detected during package installation), just when you install from a LiveCD.

If you don't need libvirt to work in the VM, you can remove libvirt networking there by running sudo virsh net-destroy default && sudo virsh net-undefine default, and then renewing the network connection in NetworkManager. If you need libvirt to work in VM, you need to edit its configuration files and assign a different IP range to it.


Hardware issues

ARM issues

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.

Fedora Cloud issues

Other issues

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.