This page documents common bugs in Fedora 17 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.
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. Please follow the style and guidelines explained in the comments in the page source.
- 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)
Post-install reboot fails after NFS installation
Sometimes, after the completion of a Fedora 17 installation using an NFS repository, the reboot which ends the install process will fail, leaving the system stuck at a black screen or some kernel messages. It is quite safe to reboot manually at this point, the installation has completed successfully and the installed system will work correctly. We recognize that manual rebooting may be more difficult in the case of automated deployment of headless and/or remote systems. The issue occurs when the NFS repository in use is unmounted too quickly, while the installer is still attempting to use resources from it; it appears to be a race-prone issue, as it does not occur in every test, and seems to occur much more frequently on some test systems than in others.
There is an installer updates image which should work around the issue. For details on how to use an installer update image, see this page. Note that you will need to rename this file to updates.img for this to work.
You can also work around the issue by accessing the remote repository via HTTP or FTP rather than via NFS. HTTP/FTP repositories are not mounted, and so are not subject to the bug.
Kernel from previous release may still be used after upgrade, prevents clean shutdown
Starting during the Fedora 17 development cycle, the Fedora kernel team has started keeping the kernel package on all currently-supported releases as closely synchronized as possible. One unfortunate consequence of this policy is that it is now much more likely than previously that, on upgrading from one Fedora release to the next, no kernel from the new release will be installed. This will very likely be the case if you use the Fedora 17 DVD to upgrade from an updated Fedora 16 installation without enabling the updates online repository during the upgrade.
Unfortunately, due to the /usr move feature of Fedora 17, if you boot a Fedora 17 system using a kernel that was installed while the system was still running Fedora 16, it will be unable to shut down cleanly. You must use a kernel installed after the upgrade to Fedora 17 in order to shut down cleanly.
To avoid this problem we recommend enabling the updates repository when upgrading to Fedora 17 whenever possible. If you do an upgrade to Fedora 17 and find the system will not shut down cleanly, check with
uname -r whether the kernel you are using is from a previous release. If so, try to install and use a Fedora 17 kernel from the online repositories.
preupgrade fails with small /boot partition
If you attempt to preupgrade from an earlier Fedora release to Fedora 17 on a system with a small /boot partition - less than 500MB in size - the second phase of the upgrade (when the system reboots to the Fedora installer to complete the upgrade) will fail to boot properly, dropping you to an emergency shell after repeatedly failing to download a file.
You can work around this issue by editing the bootloader entry for the upgrade and removing /LiveOS/squashfs.img from the end of the stage2= parameter, so that it ends with /os/. Doing so should allow the upgrade to proceed as normal.
New EFI system partition created every time you install on a Mac
Re-installing Fedora 17 on Macs in UEFI mode creates superfluous 200MB HFS+ partitions.
When re-installing Fedora 17 on Macs using UEFI boot, and choosing the "Replace Existing Linux" installation type, the previous 200MB HFS+ partition used as
/boot/efi will not be replaced. Instead a new one will be created. Both old and new boot options will appear in the option-key startup boot menu, and in Mac OS System Preferences > Startup Disk panel. It will not be clear which option is functional. To avoid this ambiguity, delete the 200MB HFS+ partition prior to re-installing Fedora 17, either from within the Anaconda user interface, or a CLI tool capable of editing a GPT. This does not affect first time installs.
ksdevice install parameter values are case-sensitive
In Fedora 17, the values for the ksdevice= parameter which can be passed to the installer are case sensitive. That is to say, ksdevice=bootif and ksdevice=link are valid, but ksdevice=BOOTIF or ksdevice=Link are not. Invalid values can cause the installer to fail to boot. This differs from previous releases, where the values were not case sensitive, so configurations which previously worked may no longer do so.
preupgrade from Fedora 16 does not update bootloader configuration
Due to several issues with grub and with the way preupgrade attempts to update the bootloader configuration, when you preupgrade from Fedora 16 to Fedora 17, the first stage of the process - the preupgrade application which runs within Fedora 16 - fails to upgrade the bootloader configuration on completion. This means that, when you reboot in order to complete the upgrade via the Fedora 17 installer, the system will by default boot not to the installer to complete the update process, but back to the existing Fedora 16 installation.
There is no danger in this, and the upgrade can still be run successfully, no matter how many times the system is booted to Fedora 16. To complete the upgrade, you only have to access the boot menu before the timeout expires and manually select the 'Upgrade to Fedora 17' entry. This will cause the installer to run and complete the upgrade.
Installer crashes if you edit an existing btrfs partition
If you use the 'custom partitioning' option in the Fedora 17 installer and attempt to edit an existing btrfs partition in any way, the installer will crash with the error "KeyError: 'fstypeCombo'". If you report the error it will show as a duplicate of bug #810141.
There is no direct workaround for this bug. Fedora 17 is not capable of interactively creating or modifying btrfs partitions in the installer. If you wish to use btrfs partitions in a Fedora 17 installation, the options available are either to use a kickstart (scripted installation) or install Fedora 16 and then upgrade.
Bootloader password is required on each boot
If you set a bootloader password during installation of Fedora 17 (which is only possible when doing a kickstart-based install), the password will be required at each boot of the system. This is a change in behaviour from Fedora 15 and earlier, where the password was required only to change settings from within the bootloader.
Lawrence Lowe suggests that the --unrestricted parameter can be added to menuentry lines in the grub config file to make them available without the password being entered.
Systems hangs on X startup with NVIDIA GeForce GTX 580 adapter (affects installation)
It has been reported that a bug in the nouveau video driver causes systems with an NVIDIA GeForce GTX 580 video adapter to hang as soon as the X graphical environment starts up. This issue also affects installation, so as soon as X is started, installation hangs.
This issue can be worked around by disabling hardware acceleration. To do this, pass the kernel parameter nouveau.noaccel=1. You can append kernel parameters at boot time - of a live image, DVD or network install image, or an installed system - by hitting the Tab key when the system reaches the bootloader menu, and typing in the desired additional parameter.
You can make the workaround 'permanent' on an installed system either by editing it into the
/boot/grub2/grub.cfg file, or by creating a file named
/etc/modprobe.d/noaccel.conf containing a single line reading:
options nouveau noaccel=1
Boot hangs when using NVIDIA discrete graphics on some Thinkpad models (W520, T420)
Multiple testers have reported that various Thinkpad models - including at least the W520 and T420 - that have hybrid Intel/NVIDIA graphics will fail to boot Fedora 17 when using the discrete NVIDIA graphics adapter. Using the onboard Intel adapter, Fedora will boot successfully.
Further testing indicates that this bug is an interaction between several features of these systems and of Fedora: the VT-d advanced virtualization feature, the X2APIC level APIC, and the NVIDIA adapter. If all three of these things are used together, boot fails. If any one is removed from the equation, boot succeeds.
So if you are affected by this bug, you can choose to boot with any two of those things, but not all three together. You can disable the VT-d feature and select which graphics adapter to use through the system firmware. You can disable X2APIC functionality by passing the kernel parameter nox2apic. In this way, you should be able to determine which of the features you want to use.
The kernel developers plan to address this issue in a future kernel update by blacklisting X2APIC functionality on affected systems, when the NVIDIA adapter is in use.
Hibernation may lead to data corruption
There have been some reports that use of hibernation (suspend to disk, as opposed to suspend to RAM) may result in data corruption, possibly to files in
/var/tmp. After a hibernate/resume cycle, the partition is reported as damaged by fsck. These reports are still being investigated, but as a precaution we highly recommend you avoid use of the hibernation function on systems containing important data. Sleep - suspend to RAM - is usually sufficient for most purposes.
GNOME login screen (GDM) always uses US keyboard layout if available
In Fedora 17, GDM (the GNOME login manager) is designed to always use the U.S. keyboard layout if it is available. This design is now considered to be flawed, but there was not time to change it for the release of Fedora 17. This means that if you install Fedora 17 using any of the keyboard layouts that are, by default, 'twinned' with the U.S. English layout - including Czech QWERTZ, Russian, several Indian layouts, and several others, all listed in this Bugzilla comment, then the chosen layout will be used during user creation in the firstboot utility, but the U.S. English layout will be selected by default in GDM. This is, obviously, confusing, and may lead to your 'correctly typed' password not being accepted, if the keys used to enter it differ between the two layouts. You can change the keyboard layout in GDM simply by clicking on the layout selector at the top-right hand corner of the screen.
Of course, you will also be affected by this issue if you typically use a layout other than U.S. English which does not come 'twinned' with the U.S. English layout by default, but you manually install the U.S. English layout after system installation.
DKMS broken due to executable being named dkms.old instead of dkms
package contains a very old post-install scriptlet which checks for
/sbin/dkms and renames it to
/sbin/dkms.old. This appears to have been intended to prevent an old copy of dkms in /sbin from overriding the Fedora-provided copy in /usr/sbin. However, with the /usr move feature in Fedora 17,
/sbin is a symlink to
/usr/sbin, and consequently the Fedora package itself effectively provides a copy of
/sbin/dkms - which its own script promptly renames. The upshot is that there is no 'dkms' executable after installation of Fedora 17's
package, and so DKMS fails to work at all.
We hope to issue an update to resolve this bug shortly.
SELinux deny_ptrace flag on by default: will prevent gdb etc. from working
The SELinux deny_ptrace flag is enabled in Fedora 17. This will prevent applications that use the kernel ptrace(2) API - like gdb and strace, and other debugging utilities - from working: you will see an SELinux denial when trying to use them. To toggle the flag off (until reboot), so you can use a debugger, run
setsebool deny_ptrace 0 as root. To make this change permanent even after rebooting, run
setsebool -P deny_ptrace 0.
Soundcard inaccessible after upgrade from a previous Fedora release
A few users reported that after upgrading from Fedora 16 their /etc/pam.d/* configuration files did not reference the pam_systemd.so module. As a result, the user login sessions are not properly tracked by the systemd-logind daemon and the users are not granted access to sound and other devices. It is unclear what the exact conditions for the wrong PAM configuration to occur are. The problem does not seem to be easily reproduced. To fix the problem, run
authconfig --updateall which will correct the PAM configuration files.
Disabling chronyd service does not stop chronyd from running
Due to the design used to allow the GNOME control center to enable or disable network time configuration, disabling the chronyd.service service will not in fact prevent chronyd from running if at least one of these conditions is true:
- Network time is enabled in the GNOME control center.
- ntpd.service is installed as well and enabled.
GDM fails to run in some virtual machine configurations with fprintd installed
Several users have reported that Fedora 17 installations to various virtual machine configurations, including Xen, VMware, and KVM systems, fail to run the default login manager (GDM). The Oh no! An error has occurred error screen appears instead. The GDM logs, if examined, show JS ERROR: !!! Exception was: Error: Error invoking Gio.init: Error calling StartServiceByName for net.reactivated.Fprint: GDBus.Error:org.freedesktop.DBus .Error.Spawn.ChildExited: Launch helper exited with unknown return code 157.
Keyboard "dies" (becomes unresponsive)
Fedora 17's X server has a feature called "slow keys" which can engage when you hold down the Shift key for more than 10 seconds. On some window managers such as XFCE there is no visual notification when this happens. The bug link gives various possible remedies.