Common F14 bugs
This page documents common bugs in Fedora 14 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)
Suspend fails on Thinkpad systems
Due to a bug in the TPM (Trusted Platform Module) support in the kernel, suspending will fail with almost all IBM and Lenovo Thinkpad laptops using the Fedora 14 release kernel, 220.127.116.11-46.fc14. An error of the form tpm_tis 00:0a: tpm_transmit: tpm_send: error -5 will be present in the system logs.
An updated kernel package has been released to address this issue. Update your system as usual to receive this update, if you do not yet already have it.
Issues when upgrading from previous releases
After preupgrading from Fedora 12, unable to login to GDM
from Fedora 12 may encounter trouble logging into the system after the upgrade - the GDM login screen may not show up or it may keep restarting. To avoid this problem, please be sure to fully update your Fedora 12 installation (and reboot) before using preupgrade tool.
If you did not perform the recommended procedure (or encountered this issue despite that), resolve it by installing a selinux-policy-3.9.7-7.fc14 update. You can install the update and relabel your system using the following approach:
- Access a root shell - press
<Ctrl><Alt>F2to change to a different TTY and log in as root.
- Apply the
update by typing
yum update selinux-policy
- If yum complains about inaccessible repositories, your network devices may have not been started up. Type
dhclient eth0to enable your default network card and repeat the previous step.
- Instruct your system to relabel upon the next reboot by typing
- Reboot your system. The boot process will take a bit longer as it relabels your system, that's expected.
After the system reboot completes, you will be able to login to GDM.
Anaconda fails to modify NTFS partition
Installing Fedora 14 on a system that contains NTFS formatted partitions may result in a traceback when attempting to modify the partitions. Investigation has identified a problem with the Fedora installer (see patch). To workaround this problem, users are advised to refrain from modifying NTFS formatted partitions during installation, and instead make necesary changes on a running Fedora 14 system using
palimpsest. If your use case absolutely requires modifying existing NTFS partitions during installation, an updates.img is available that resolves the issue. For instructions for creating and using an updates.img are available on the wiki at Anaconda/Updates.
Multiple CD-ROM installation may result in incorrect boot progress theme
Fedora CD-ROM installation images are constructed with many different packages spread across six ISO images. Due to an issue with how packages are split into different ISO media, the
package is available on Disc 2. This will cause CD-ROM installations to use the plymouth text boot progress theme on boot. When a new
update is available and installed on the system, the problem will be resolved.
Users wishing to manually set the plymouth theme can run the following commands:
- Open a terminal window by selecting Applications → System Tools → Terminal
- In the terminal window, change to a root shell by typing:
- Reset plymouth to use the default boot theme by typing:
- Finally, rebuild your initial ramdisk by typing:
Live install doesn't offer discovery of iSCSI targets
When running the Fedora 14 installer from a Live image, the option to add a remote iSCSI target is disabled (see screenshot). The problem is that the
iscsi_tcp kernel module hasn't been loaded by the
liveinst installer script, and the iSCSI application paths used by the installer are incorrect. The problem is resolved in future versions of the installer (see anaconda patches 67605ee53bdf4453b469e74ca1759b1797f1ef93 and 19ed4f132069eb06c00fd366ad06d1a3d658ec14).
To install Fedora 14 to iSCSI targets using the Fedora 14 Live image, you must follow the procedure outlined below.
- Open a terminal window by selecting Applications → System Tools → Terminal
- In the terminal window, change to a root shell by typing:
- Load the
iscsi_tcp.kokernel module by typing:
modprobe -a iscsi_tcp
- Allow anaconda to see the iSCSI application binaries by typing:
cp -vl /sbin/iscsi* /usr/sbin/
Now you can use the live image to discover and install Fedora 14 to remote iSCSI targets (see screenshot).
Miscellaneous graphical problems
If you are suffering from problems such as failure of X to start at all (including installer failure when switching to graphical mode), hangs or freezes or crashes in the graphical environment, display corruption, failure of 3D accelerated applications to work properly or similar problems, and your issue is not specifically covered elsewhere on this page, the following general advice may be of use.
First, make sure you have applied all system updates, in case the problem has already been fixed.
For AMD/ATI graphics adapters, several such issues may be worked around by disabling kernel mode setting. To do this, add
as a kernel parameter. If this solves your problem, please check whether a bug has already been reported for it, and if not, file a new bug report on the xorg-x11-drv-ati component, explaining your symptoms, and providing all the usual information required for X.org bug reports. In future kernel mode setting will be the only available method, and so we wish to ensure all problems caused by kernel mode setting are fixed. Please note that for Fedora 14, this workaround is no longer available for NVIDIA or Intel graphics adapters; using the nomodeset kernel parameter will result either in a non-functional display, or in the fallback vesa driver being used.
For further instructions on attempting to debug graphics issues, please refer to How_to_debug_Xorg_problems. That page also explains how to file good bug reports, if you cannot resolve the issue. In such cases, you can use the fallback vesa driver to get a graphical desktop working, though performance will be slow, 3D acceleration will not be available, it may not be possible to use the native resolution of your display, and more complex graphical operations such as video playback may be problematic. To enable the vesa driver on an installed system, follow the instructions at How_to_create_xorg.conf to create a
/etc/X11/xorg.conf file, then edit this file and set the Driver line in the Device section to read:
You may also need to set the nomodeset kernel parameter to prevent the native kernel driver for your graphics card interfering with the operation of the vesa driver.
To use the vesa driver during installation, at the initial screen that appears on booting the installer, select the option labelled "Install system with basic video driver". This will use the vesa driver for installation and will also configure the installed system to use the vesa driver.
To use the vesa driver during installation from a Fedora live image, press any key at the 10 second boot countdown to access the boot menu, and select the option labelled "Boot (Basic Video)".
To use the vesa driver during upgrade from a previous version of Fedora using preupgrade:
- Boot into the old system (rebooting from a failed or hung preupgrade attempt should do so automatically)
- Login and open a terminal and run
su -c 'preupgrade-cli "Fedora 14 (Laughlin)"', and enter the root password when prompted
- Look for the first entry in the grub configuration, it should state that it is the preupgrade entry
- Find the kernel line and append the options xdriver=vesa nomodeset
- Save the file, and reboot
Blank screen displayed on many laptops using eDP displays (Dell E4310, E6410, E6500, E6510, Sony Vaio VPCZ1)
New laptops are increasingly using the embedded DisplayPort (eDP) standard for connecting their internal display panels to their graphics adapters. Unfortunately, support for this new standard is incomplete within the current Linux kernel and X.org drivers, and many systems which use eDP may have problems with Fedora 14. In particular, one popular line of Dell Latitude laptops - the E6xxx series - uses the eDP protocol and fails to work correctly with Fedora 14 (though it worked with Fedora 13). This is an area of intense development focus upstream, but it is not straightforward to port specific fixes back to the Fedora kernel, and backporting the changes wholesale runs a significant risk of introducing new regressions. We will attempt to backport safe fixes for these problems to Fedora 14 as and when this is feasible.
Users of affected systems who are comfortable with the process of building and testing kernels may wish to try compiling the drm-intel-next branch of Jesse Barnes' drm-intel tree, which contains the latest work on eDP problems, and resolves the case of the Sony Vaio VPCZ1 in Intel graphics mode (though reports indicate it does not help most of the affected Dell models yet). They may also wish to follow Freedesktop.org bug #29278, which is the upstream report for the Dell E6xxx series issue. Aside from this, the only available workaround is to use the vesa driver, as described above.
Intel wireless adapters stop working when in 802.11n mode
Intel has acknowledged an issue in the firmware for its wireless chipsets (widely used in laptops from various manufacturers) which can result in the wireless adapter stopping working some time after system boot, if it is operating in 802.11n mode. An error message of the form:
BA scd_flow 0 does not match txq_id 10
may be found in the system logs. The only reliable way to work around this issue is to disable 802.11n functionality. To do this, create a file named
/etc/modprobe.d/intel-80211n.conf, with the contents:
options iwlagn 11n_disable=1
and reboot the system. Obviously, this will restrict the connection to 802.11a/g speeds as a maximum, and you must configure your wireless router to enable 802.11a and/or 802.11g support. Intel is working to provide a fix for this issue.
USB 3.0 ports not working
Due to USB 3.0 support preventing users from being able to suspend their laptops, it has been disabled by default for the release of Fedora 14. USB 2.0 ports (ehci_hcd) will continue to work as expected. If support for USB 3.0 is more important to you than support for suspend/resume is not necessary, you can pass the kernel parameter xhci.enable=1, which will allow the xHCI support to load. There is also a workaround which will allow you to enable USB 3.0 support and still suspend successfully. After adding the xhci.enable=1 kernel parameter, create a file named
/etc/pm/config.d/xhci, with the contents:
You should now be able to suspend and resume the system successfully.
Slow rendering of older applications with nouveau driver
A change was made to the nouveau driver for NVIDIA graphics cards during the Fedora 14 development cycle which fixes performance and rendering issues in some newer applications at the cost of causing performance issues in some older applications, particularly those which use bitmap fonts. If you notice very slow performance in certain older applications (examples cited in the bug report include emacs and xterm when using bitmap fonts rather than freetype), you may try an X configuration option which restores the old behaviour. Add this line to the Device section of your
/etc/X11/xorg.conf or a new X configuration snippet in
Option "WrappedFB" "on"
This should resolve the issue (though you may possibly notice performance issues or rendering problems in other applications).
Meego environment does not work
The Meego 1.0 desktop environment was listed as a feature of Fedora 14 until release day, and consequently was mentioned in many news stories regarding Fedora 14. Unfortunately, our volunteer Meego developers were unable to complete work on the Meego environment for release, and so although all the Meego-related packages are present, bugs remain which result in the Meego environment currently being entirely unusable (it is not possible to even log in to Meego successfully). We will continue to work on this and try to provide a usable Meego environment for Fedora 14 through official updates. We apologize for any inconvenience or confusion caused by our incorrect messaging regarding this feature.
Some Intel BIOS RAID arrays not activated correctly when booting live
When booting Fedora 14 live images, some Intel BIOS RAID arrays are not correctly activated on boot. No /dev/md* nodes will appear for the partitions that are part of the array, and hence you will not be able to access them. The issue should have no impact when installing because the
installer should correctly activate the array.
Additional displays turned off by default in GNOME desktop
Due to a problematic change to the way upstream GNOME handles multiple monitor configurations, on new Fedora 14 installations on laptops with external displays attached, the external displays will often be active during boot but then be deactivated within GNOME by default. The previous Fedora behaviour was to enable such displays by default. You can enable the external display within GNOME by using GNOME's Monitor Preferences tool, which is available within the system menus.
Cheetah isn't compliant with python-2.7
At the time of the Fedora 14 release, the
package had not yet been updated to work with the python-2.7 update. However, an updated python-cheetah package is now available that resolves the reported issue. Users experiencing this problem are encouraged to update
and report any problems into bugzilla. To update, run the following command:
su -c 'yum update python-cheetah'
Crash of gmixer application reported each time LXDE starts
At each start of the LXDE desktop environment, a crash in the
application occurs (and is reported by the automated crash report tool ABRT). Consequently, no mixer (volume control) applet appears in the LXDE panel. This is a known issue in gmixer; it is not necessary to submit the ABRT report. There is no known workaround for this issue, but it has no consequences beyond the lack of a volume control applet. This issue will be resolved in the final Fedora 14 release by fixing the gmixer bug or switching to a different volume control applet.
Gnome keyring asks for password each time LXDE starts
At each start of the LXDE desktop environment, a password dialog appears when an application wants to unlock the default keyring. In order to have the keying unlocked automatically through the LXDM display manager, you need to install
. To install gnome-keyring-pam, run this command:
su -c 'yum install gnome-keyring-pam'
ibus-anthy crashes on use of F7 or F8 keys
An updated ibus-anthy package has been submitted to the updates-testing repository for testing. To test the update, run this command:
su -c 'yum --enablerepo=updates-testing update ibus-anthy'