Common F14 bugs

In other languages: English (en) italiano (it) 中文 (zh) [edit]

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.

Release Notes

Read the F14 beta Announcement and the Fedora 14 release notes for specific information about changes in Fedora 14: known issues, 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. 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
  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)

= Suspend fails on Thinkpad systems

link to this item - Bugzilla: #644842

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, 2.6.35.6-46.fc14. 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

link to this item - Bugzilla: #646437

Users running preupgrade from Fedora 12 may encounter trouble logging into the system at after upgrade. The problem appears to be resolved by installing a selinux-policy-3.9.7-7.fc14 update. If this package has not already been installed during the uprgade, install the update and relabel your system using the procedures listed below:

1. Access a root shell. This can be accomplished by the system into single-user mode, or by changing to a different TTY by pressing <Ctrl>F2.
2. Apply the selinux-policy update by typing yum update selinux-policy
3. Instruct your system to relabel upon the next reboot by typing touch /.autorelabel
4. Reboot your system

After the system reboot completes, you will be able to login to GDM.

Installation issues

Anaconda fails to modify NTFS partition

link to this item - Bugzilla: #627153

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

link to this item - Bugzilla: #645592

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 plymouth-themes-charge 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 kernel 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:

1. Open a terminal window by selecting Applications → System Tools → Terminal
2. In the terminal window, change to a root shell by typing: su -
3. Reset plymouth to use the default boot theme by typing: /usr/sbin/plymouth-set-default-theme --reset
4. Finally, rebuild your initial ramdisk by typing: /usr/libexec/plymouth/plymouth-generate-initrd

Live install doesn't offer discovery of iSCSI targets

link to this item - Bugzilla: #645523

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.

1. Open a terminal window by selecting Applications → System Tools → Terminal
2. In the terminal window, change to a root shell by typing: su -
3. Load the iscsi_tcp.ko kernel module by typing: modprobe -a iscsi_tcp
4. 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).

Hardware-related issues

Miscellaneous graphical problems

link to this item

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

nomodeset

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:

Driver "vesa"

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:

1. Boot into the old system (rebooting from a failed or hung preupgrade attempt should do so automatically)
2. Login and open a terminal and run su -c 'preupgrade-cli "Fedora 14 (Laughlin)"', and enter the root password when prompted
3. Edit /etc/grub.conf
4. Look for the first entry in the grub configuration, it should state that it is the preupgrade entry
5. Find the kernel line and append the options xdriver=vesa nomodeset
6. Save the file, and reboot

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.

Software issues

Intel BIOS RAID array not activated until running Live installer

link to this item - Bugzilla: #645283

Due to a Live image configuration problem, Intel BIOS RAID arrays are not probed and activated on boot. The issue has no impact when installing because the anaconda installer correctly probes and activates all BIOS RAID devices. However, if you need to inspect, repair or modifiy the array prior to starting the Fedora Live installer, manual intervention is required.

Follow the procedure below to activate any Intel BIOS RAID arrays prior to running the Fedora Live installer.

1. Open a terminal window by selecting Applications → System Tools → Terminal
2. In the terminal window, change to a root shell by typing: su -
3. Create a /etc/mdadm.conf file that contains the following lines:

    # mdadm.conf for livecd
   MAILADDR root
   AUTO +imsm +1.x -all

4. Restart mdmonitor by typing: service mdmonitor restart

You now can access any Intel BIOS RAID arrays from the Fedora Live image.

Additional displays turned off by default in GNOME desktop

link to this item - Bugzilla: #623824

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

link to this item - Bugzilla: #640093

At the time of the Fedora 14 release, the python-cheetah 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 python-cheetah 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

link to this item - Bugzilla: #542255

At each start of the LXDE desktop environment, a crash in the gmixer 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

link to this item - Bugzilla: #643435

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 gnome-keyring-pam. 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

link to this item - Bugzilla: #644771

When you type F7 or F8 key to convert Japanese characters with ibus-anthy, the conversion is failed and ibus-anthy will be SEGV without this fix.

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'