From Fedora Project Wiki

(No network connection in VM when both host and guest installed from a Live image|1146232)
No edit summary
Line 85: Line 85:


== Hardware issues ==
== Hardware issues ==
{{Common bugs issue|system reboots after shutting down|The system reboots instead of shutting down|1257131}}
On some specific Intel boards the system reboots after a few seconds instead of shutting down. This is related to the XHCI controller and will likely be fixed with newer kernel releases, but actually there is a workaround listed in the link above to fix this issue.
== ARM issues ==
== ARM issues ==
== Fedora Server issues ==
== Fedora Server issues ==
== Fedora Cloud issues ==
== Fedora Cloud issues ==
== Other issues ==
== Other issues ==

Revision as of 20:36, 18 September 2015

This page documents common bugs in Fedora 23 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.

Note.png
Pre-release version
Fedora 23 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 23 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 F23_Alpha_release_announcement for specific information about changes in Fedora 23 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

Media consistency check fails with an error on DVD/netinst

link to this item - Bugzilla: #1250414

If you choose to verify media consistency using appropriate boot menu item when using the DVD or netinst media, you'll shortly see an error and then the boot will continue. You'll not be able to verify whether the image was burned/created correctly.

We recommend at least verifying the downloaded ISO image sha256 checksum to avoid download errors, or using the Live media if you need to be sure that the image was burned correctly.

Media consistency check times out when using optical media

link to this item - Bugzilla: #1250440

If you choose to verify media consistency using appropriate boot menu item when booting from a optical medium (CD/DVD instead of USB stick), the check is very likely to take more than 90 seconds, after which the boot process times out and you're put into an emergency shell. The consistency check still continues and can you wait for it to finish to make sure the medium is burned correctly. But then you'll need to reboot the machine and boot the installer again, this time avoiding "Test this media" boot options.

Livecd-iso-to-disk script doesn't create working working DVD image on a USB stick

link to this item - Bugzilla: #1247622

If you use livecd-iso-to-disk command line utility to create a bootable USB stick with DVD contents, the installer will crash on boot. It is recommended to use a different tool to create such media for now.

Installer deletes EFI System Partition even in dual boot scenarios

link to this item - Bugzilla: #1183880

If you have several operating systems installed using UEFI boot (booting from EFI System Partition - ESP) and then go into the manual partitioning screen in the installer and select one of the operating systems to be deleted, the ESP will be deleted as well, even though it is required by the other operating systems.

If you need to perform such installation, don't delete the full partition tree under the to-be-deleted operating system, but delete all of its non-ESP partitions individually and leave ESP intact.

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.

Filesystem encrypted with cyrillic or arabic language passphrase can not be decrypted at boot time

link to this item - Bugzilla: #681250

Filesystem encrypted with cyrillic or arabic languages passphrase can not be decrypted at boot time. English (USA) keyboard layout (by default it is set as secondary layout for installation) is used for decryption, if you need to encrypt your system please use this layout for passphrase.

Upgrade issues

Fedup crashes when trying to upgrade to Fedora 23

link to this item - Bugzilla: #1245838

If you try to use fedup to upgrade to Fedora 23, it will crash early in the upgrade process with a message similar to this:

systemd[1]: [/etc/systemd/system/system-upgrade-shell.service:8] Couldn't unescape assignment, ignoring: TERM=linux PS1=system-update:\w\$\x20
systemd[1]: Caught <ABRT>, dumped core as pid 132.
systemd:[1]: Freezing execution.

fedup is going to be replaced with a different tool to perform system upgrades. It is not recommended to try to use it at this moment.

GNOME issues

GNOME does not notify about available updates

link to this item - Bugzilla: #1246252

A bug causes GNOME to not emit notifications when software updates are available. It is recommended to run sudo dnf update (or sudo dnf distro-sync, if you run with updates-testing repository enabled) regularly instead.

Workstation installation from netinst causes random fonts missing

link to this item - Bugzilla: #1236034

If you install Workstation from netinst image instead of Live image, you're very likely to end up with some fonts missing in the desktop. You might or might not spot this problem, depending on which fonts are missing and how exactly you use your computer. You can fix the issue by running sudo fc-cache -f.

Plasma (KDE) issues

Initial setup sometimes starts in text mode instead of in graphics mode

link to this item - Bugzilla: #1185447

Sometimes happens that initial setup starts in text mode instead of graphical mode. Furthermode, it seems that text mode does not display properly. You can either reboot a few times, or log into a console and disable initial-setup-text.service by running command sudo systemctl disable initial-setup-text.service 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

The system reboots instead of shutting down

link to this item - Bugzilla: #1257131

On some specific Intel boards the system reboots after a few seconds instead of shutting down. This is related to the XHCI controller and will likely be fixed with newer kernel releases, but actually there is a workaround listed in the link above to fix this issue.

ARM issues

Fedora Server issues

Fedora Cloud issues

Other issues