|(14 intermediate revisions by 6 users not shown)|
|Line 1:||Line 1:|
Latest revision as of 14:05, 11 April 2012
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, please do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.
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)
Kickstarts listing default repos by name only are not properly handled
When doing a kickstart install, you are supposed to be able to enable repositories that are present in
/etc/anaconda.repos.d but not enabled by default - e.g. - by including a line which simply specifies the repo by name:
Unfortunately, this feature was inadvertently broken by an over-enthusiastic check in Fedora 23. If the installer is run in graphical mode, such a kickstart will cause it to stop at the hub screen, showing an error condition for the INSTALLATION SOURCE spoke; if the installer is run in text mode, such a kickstart will cause a crash.
We have provided an installer update image including the fix for this. If you need to use such a kickstart line, you can use the updates image by adding the kernel parameter when booting the installer. Of course, you can also download the updates image and use any of the other available updates image delivery mechanisms.
Installer deletes EFI System Partition even in dual boot scenarios
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 always correctly compute the minimal required partition size
The installer uses a set of heuristics to determine the minimal partition size to fit your installation in. Sometimes if you get very unlucky or you intentionally try to get the install partitions as small as possible, the installer might approve the partition size, but the installation fails at the beginning of the installation transaction (after your partitions have been created and formatted) due to insufficient disk size.
To be safe from this issue, please don't try to set an extremely small root partition (or any other system-critical partition, likepartition, if you decide to define one). Always plan for at least 500+MB of free disk space on such partitions (of course, in majority of cases you want much much more free space to have your system usable and useful).
Filesystems encrypted with passphrases using Cyrillic, Arabic or other switched keyboard layout characters cannot be decrypted at boot time
If the console keyboard layout for your language is 'switched' (you use a key combination to switch between typing Latin characters, and characters from your language), you will not be able to switch when entering encryption passphrases. Therefore, you will only be able to enter passphrases using whichever layout is the default. Usually, the Latin layout is the default. Therefore, if you are doing an encrypted installation using a language with a switched keyboard layout, we recommend you use only Latin characters in the passphrase.
System boots into an older kernel instead of the latest one
This bug only affects systems installed from a pre-release version of Fedora 23 (before Fedora 23 RC2). If you have used the final release for installation (or upgraded from a previous Fedora), you're not affected.
The affected systems do not boot with an updated kernel, but to the old kernel version. This can be fixed by manually changing a line infrom:
Software RAID (mdraid) from existing Fedora installations not recognized by Workstation/Live installs
Installation from Workstation/Live image does not properly recognize software RAID (mdraid) devices from existing (e.g. previous) Fedora installations. Those devices are listed as "Unknown" (0 bytes size) and cannot be used in the device selection dialog which makes it basically impossible to install Fedora 23 or keep existing data.
This bug exists since Fedora 22 (several Bugzilla reports has been filed for this issue). The Server image does not have this problem and can be used as a workaround to install the Workstation spin from network remotely. Fedora Workstation may no longer be the proper distribution for systems with Software RAID devices.
System-upgrade does not work under Chinese and Japanese (and probably some other) locales
System upgrade cannot be performed on system using certain languages - we currently know about Chinese and Japanese, but it's likely that further languages are affected as well. Until that bug is resolved, the simplest workaround is to switch your system temporarily to English, perform the upgrade, and then switch back to your language. First, see what language (locale) you are currently using:
It should list something like
LANG=zh_CN.UTF-8 (for Chinese). Mark this down. Then switch the system to English:
$ sudo localectl set-locale LANG=en_US.UTF-8
Reboot. If you run
locale, you should see
LANG=en_US.UTF-8 output (unless your session uses a different language from the default one in system, in that case you need to change language in your session as well, for example in gnome control center). Now perform the upgrade according to instructions. Once it is done and you're running Fedora 23, change the system locale back to your original one:
$ sudo localectl set-locale LANG=YOUR_PREVIOUS_LOCALE
Packages downloaded for system upgrade are removed if you perform a package transaction before starting the upgrade
If you want to upgrade your system, you first need to download all necessary packages, and then trigger the upgrade process. However, if you do any package transaction between these two actions, e.g. because there is some dependency issue between your currently installed packages and the downloaded packages, or because you decide to install/remove something before starting the upgrade process, the whole package cache (including all of your downloaded packages) are cleaned. If you try to start the upgrade process, you'll receive unhelpful error message. You'll need to download all the packages again (using
dnf system-upgrade download ... command).
If you download all the packages for upgrade, and then want or need to perform some other transaction before starting the upgrade, use
--setopt=keepcache=True DNF option. That will make sure your package cache is not cleaned and you will not need to re-download everything again.
Upgrade path for Vagrant broken (rubygem-celluloid retired)
was retired between Fedora 22 and Fedora 23, but no package was set to obsolete it. If you have the package installed when you try to upgrade to Fedora 23, and you do not use the option, the upgrade will fail to resolve dependencies. We recommend using to enable DNF to remove the rubygem-celluloid package and allow the upgrade to proceed, but please check the list of packages to be removed carefully and make sure the upgrade will not remove anything vital to you.
Core software issues
Initial setup sometimes starts in text mode instead of in graphics mode
Sometimes, the initial setup utility that runs on first boot when a user account is not created in the installer starts in text mode instead of graphical mode. This looks a little surprising, but the text mode utility will work correctly and allow you to create a user account if desired, and the login screen should be shown correctly after it is complete.
Initial user creation hands off to login screen (not desktop) and first attempt to log out fails
GNOME includes its own 'first boot' utility,
. If you install Workstation and do not create a user during the installation process, it will appear the first time you boot the installed system and require you to create a user account. When you complete the utility, it is intended to transfer you directly to the desktop logged in as the newly created user. However, sometimes, this does not work as intended and instead you see the GNOME login screen after creating the user account. When this happens, and you log in as the user you just created, your first attempt to log out will not work correctly, but instead will return you to a fresh logged in desktop session.
It appears that there is a timing problem, where gnome-initial-setup creates the logged in desktop session but does not successfully hand off to it, and when you then log in normally and log out, you are sent to the session created by gnome-initial-session.
This problem is a one-time issue and has no further effects. Once you log out a second time, everything will work normally from then on.
Plasma (KDE) issues
No network connection in VM when both host and guest installed from a live image
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 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 the guest manually at some point later (it is detected during package installation), only when you install from a live image.
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.
Three monitors with an Intel GPU results in instability and display issues
Since kernel 4.2, some people with Intel graphics cards have reported issues when they have three (or possibly more) monitors attached. The issues can range from desktop environment crashing, to monitor layout being reset from time to time, or certain monitors not waking up from sleep/locked desktop mode.
If you're affected, you can install and boot an older kernel 4.1 to work around this, or please wait until the issues are fixed in some future kernel update.
Fedora Server issues
FreeIPA web UI (and potentially other webapps) does not work, SELinux denies 'execmem' access
There is a complex bug in Fedora 23 which is known to affect the FreeIPA web UI and may affect other webapps written in Python. In Fedora, SELinux is configured by default to prevent web server processes from executing writeable memory - referred to as 'execmem' access. We have determined that use of the
module version in Fedora 23 commonly triggers such 'execmem' accesses. Notably, using the widely used
module loads the python-cryptography module if the
package is installed. This package was a dependency of
in Fedora 21, so it is fairly common to have it installed.
The result of this is that, if you have
installed, any Python webapp that uses the requests module is likely to crash. In the system logs you will see an SELinux denial of the 'execmem' access, and in the web server logs you will likely see a note that the affected process crashed. This is known to affect at least the FreeIPA web UI - the web server will continually try to launch child processes, and each one will crash - and may possibly affect other webapps.
The actual problematic code is likely in the
module or the
library it uses. We are working with the upstream developers on getting this fixed, in an upstream bug report.
One possible workaround for this problem is to remove the
package. Note that doing this will prevent SNI working in any python-requests based application. Another workaround is to allow the 'execmem' privilege for web server processes, although this restriction exists for good reason and bypassing it reduces your protection against some types of security exploit: please make sure you understand the consequences of this change. To do this, run the command
setsebool -P httpd_execmem 1 with root privileges.
Fedora Cloud issues
Atomic images have incorrect permissions on the /tmp directory
The permissions of the
/tmp dir on Fedora 23 Atomic host images are 755 when they should be 777. This breaks things that want to write to tmp but don't have permissions to. To get around this:
chmod 1777 /sysroot/tmp. Updated Atomic host images are expected to be provided regularly for Fedora 23, and this issue should be resolved in those.
FreeIPA fails to upgrade properly
If you upgrade a system running FreeIPA to Fedora 23, FreeIPA will not start on the upgraded system. The logs will instruct you to run FreeIPA's upgrade process: . However, if you ran the upgrade script with the original FreeIPA packages released with Fedora 23, it would fail, and FreeIPA would still not work.
We strongly advise you ensure the updates repository is enabled when upgrading FreeIPA servers to Fedora 23 and ensure the updates listed above are included.
If you ran the upgrade script before the updates were released and encountered the bugs, you may be able to recover and get FreeIPA working by doing the following:
- Find the entry (split across three lines) that starts
- Replace it with:
attributeTypes: ( 2.16.840.1.113722.214.171.124.2.3 NAME 'ipaVaultPublicKey' DESC ' IPA vault public key' EQUALITY octetStringMatch SYNTAX 126.96.36.199.4.1.1466.115.1 21.1.40 X-ORIGIN ( 'IPA v4.2' 'user defined' ) )
pki-server migrate --tomcat 8
systemctl start email@example.com
- Re-run the upgrade script:
However, results may vary.
Certain plymouth themes are problematic during system upgrade
Certain plymouth (boot screen) themes were buggy inside the system upgrade environment. The known issues are withand themes - for the first one, the progress information scrolled off the screen soon, for the second one the screen stayed black during the whole upgrade. The upgrade itself would execute just fine, but you wouldn't see the progress properly (if this happened to you, do not force-reboot the computer in the middle of the operation, wait for it to finish, it will automatically reboot once the upgrade is done).
After installing the update, you can executemanually to regenerate the ramdisk for your current kernel. Otherwise the fix will only kick in with the first kernel update after the plymouth update.
Alternatively, you can revert to the default theme before performing the upgrade:
sudo dnf install plymouth-theme-charge sudo plymouth-set-default-theme charge sudo dracut -f
SELinux denial appears on application crash
There was a known issue in Fedora 23's SELinux policy which caused a denial to occur often when an application crashed. SELinux was forbidding the ABRT crash reporting tool from doing something it wants to do to analyze the crash. The denial was.
The system reboots instead of shutting down
On some specific Intel boards the system would reboot after a few seconds instead of shutting down.