Common F12 bugs

This page documents common bugs in Fedora 12 and, if available, provides 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 Fedora 12 release notes for specific information about intentional changes in Fedora 12, and other general information.

My bug is not listed

Not every bug is listed on 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 a previously reported bug report should be added to this page because it is commonly encountered, you can:

• Add it yourself, if you have wiki access. Remember to try and follow the style and guidelines explained in the comments in the page source.
• Add the CommonBugs keyword to the bug report, and contact the Fedora QA team with the Bugzilla report number explaining why you believe that particular report qualifies as a common issue. You can contact Fedora QA through any of the methods listed here.

Resolved issues

Problems updating

link to this item - Bugzilla: #541645

If you are updating using a graphical user interface to PackageKit (the default for desktop users) and you receive this error:

Error Type: <class 'yum.Errors.RepoError'>
Error Value: Error getting repository data for installed, repository not found

Run yum update PackageKit yum rpm as root. After rebooting, the update system should perform normally again. You may wish to instead run yum update to get all available updates all at once (so if any other updates require it, you will only need to reboot once).

This update cannot happen automatically because there is a transient problem in PackageKit itself. Fortunately, "yum" is available as an alternative updater interface. This should not happen again for Fedora 13 or new upgrades to Fedora 12, but Fedora 12 users who upgraded during a certain window of time will need to apply the manual workaround.

Kernel crashes when booting on systems with Intel GMA 4500 graphics adapters

link to this item - Bugzilla: #540218

Several users reported kernel crashes when booting Fedora 12 on systems with Intel GMA 4500 graphics adapters. The full crash message can be found in the bug report; the crash occurred in the intel_tv_mode_set function. This issue can be worked around by disabling kernel mode setting with the nomodeset kernel parameter, as described below.

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.

Systems fail to boot, USB is not functional, network adapter fails to work (or possibly other symptoms) due to imperfect handling of BIOSes with broken IOMMU handling

link to this item - Bugzilla: #524808 and Bugzilla: #533952

Some manufacturers ship systems with a BIOS whose handling of IOMMU hardware is incorrect. The BIOS is supposed to tell the operating system where in memory to find the IOMMU hardware, but some BIOSes do not do so correctly, providing a garbage location or a location which is valid but is not actually where the device is located. The kernel attempts to handle these cases, but some were still not fully handled in the Fedora 12 release kernel. If you have a system affected by this problem, the most common symptom is that the USB subsystem will fail to work (no USB peripherals will work), but other symptoms have included systems that completely fail to boot, and non-functional network adapters.

There are some systems currently known to be potentially affected by this issue. For all of those except the HP xw4600 Workstation and the Dell Precision M6400, all of the following conditions must be true before you hit the bug:

• You must be using the 32-bit edition of Fedora 12
• You must have no memory beyond the 4GB address area (practically speaking, this means you must have around 2.5GB of physical RAM or less)
• Virtualization features (VT-d) must be disabled in the BIOS

If any of the above is not the case, you should not encounter this issue. If you think you may be suffering from this issue, look for a kernel log message including something similar to:

Your BIOS is broken; DMAR reported at address fed10000 returns all ones!

or:

Your BIOS is broken; DMAR reported at address zero!

Please note that if you are using a system with such a broken BIOS, the kernel message will always appear, even if the kernel in fact handles your case correctly, or you have successfully worked around the issue. So don't worry that you still see the message once you have worked around the problem.

There are several ways to work around this issue. In most cases (see above), installing the 64-bit edition of Fedora 12 would be enough. If your BIOS has an option for it, enabling virtualization features in the BIOS should also work around this problem. Finally, you can work around this issue by appending the kernel parameter iommu=soft to your boot configuration.

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. Obviously, if you are affected by the problem, you will need to use one of the above workarounds to first bring your system to a state from which you can install a fixed kernel.

LXDE live images are unusable

link to this item

Due to a severe bug which was not noticed during the LXDE group's testing, the initial LXDE live images for Fedora 12 were completely unusable. lxde-settings-daemon would crash on startup and get stuck in an infinite restart loop, rendering the desktop useless. For more details, see this blog post from the Fedora LXDE group leader. The original images have been removed and updated images are now available. If you downloaded one of the original LXDE live images, please discard it and download an updated image. You can also install Fedora 12 from the DVD or any of the other live spins and install LXDE by installing the LXDE package group.

Problems when using KDE with the proprietary NVIDIA graphics driver, some Radeon dual-head configurations, or nouveau with KMS disabled

link to this item - Bugzilla: #533620 and X.org bug #25136

We encourage Fedora users to use the free nouveau driver, rather than the proprietary nvidia driver, whenever possible.

A patch added to Fedora 12's X.org server package to fix another bug results in severe performance regressions in certain configurations when using KDE. Known affected configurations include any use of the NVIDIA proprietary driver, some configurations using the nouveau NVIDIA driver with kernel mode setting disabled, and some configurations using the radeon driver with dual monitors. The cause of this issue was identified by NVIDIA developers.

An updated xorg-x11-server set of packages has been released to address this issue. Update your system as usual to receive this update, if you do not yet already have it.

New kernels installed with yumex do not function correctly

link to this item - Bugzilla: #527528

Due to an SELinux problem, installing updated Fedora 12 kernels using the yumex utility does not work correctly if SELinux is active. The installed kernel will be unable to load any modules at boot time, which will cause many hardware components not to work, if the system is able to boot at all. To avoid this issue, use yum or PackageKit to install new kernels, rather than yumex. If you have already installed a kernel using yumex, boot to an older kernel, remove the newer kernel package (and any related packages), and then re-install it using yum or PackageKit.

An updated selinux-policy 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.

Encrypted disks can't be unencrypted for non-graphical boot

link to this item - Bugzilla: #530896

Due to an unidentified bug early in the boot cycle, some users are unable to access encrypted disks or partitions at boot up when using a non-graphical boot splash. This issue can be worked around by booting with:

rhgb vga=0x318

on the kernel command line (specified at grub time).

If you are installing Fedora 12 and intend to use encrypted partitions, or are upgrading a system with encrypted partitions to Fedora 12 from an earlier release, it is recommended that you use the traditional installer - not a live image - to install, and make sure to enable the Fedora 12 - Updates repository during installation. This will ensure you are not affected by this issue.

An updated plymouth 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. You may need to rebuild your initial ramdisk after applying the update on an installed Fedora 12 system by running the following command /usr/libexec/plymouth/plymouth-update-initrd as root. Make sure you are booted into the latest installed kernel before rebuilding the initial ramdisk.

Missing printer drivers

link to this item - Bugzilla: #536831

The foomatic package is not installed by default in a standard Fedora 12 installation. If you have a PostScript printer, or your printer requires an older driver such as one of the ghostscript built-in drivers, you may need to install this package before a driver for your printer will be available from the Fedora printer configuration tool. To install it, select System->Administration->Add/Remove Software from the main menu and search for "foomatic", or run this command from the command line as root: yum install foomatic.

If you apply system updates, system-config-printer-1.1.13-10.fc12 or greater should automatically suggest installation of the appropriate drivers.

System hangs when booting on some Broadcom wireless systems: Acer Aspire One, HP Mini 311

link to this item - Bugzilla: #533746

Several Acer Aspire One users (models known to be affected include some AO751h and some D250 models) and users of the HP Mini 311 have reported that Fedora 12 hangs when booting on their systems. The live images hang when attempting to start udev, and the traditional installer images hang when detecting hardware. To work around this issue, add this kernel parameter to the bootloader configuration:

ssb.blacklist=1

For the traditional installer, you can also use:

noprobe

Once the installation has completed, create a file /etc/modprobe.d/blacklist-ssb.conf with the contents:

blacklist ssb

Note that this will prevent the wireless network adapter from working. On some systems, it may also prevent the wired ethernet adapter from working.

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. After updating, you can remove the workaround /etc/modprobe.d/blacklist-ssb.conf file.

Adobe Reader fails to run

link to this item

Third-party vendor issue
The root cause of this problem is not Fedora, but rather software provided by Adobe. If you are interested in a fix for this issue, you must contact that vendor through their web site.

We encourage Fedora users to use a free alternative to Adobe reader, such as Evince or Okular, whenever possible.

The latest release of Adobe Reader (AdobeReader_enu-9.2-1.i486) works in Fedora 12. Previous releases of Adobe Reader do not run by default on Fedora 12. To work around this problem, launch Adobe Reader with the following command: GDK_NATIVE_WINDOWS=1 acroread.

Non-responsive Flash objects

link to this item - Bugzilla:#542424

When compiz is enabled, some flash objects in web pages may be unresponsive to mouse clicks.

An updated nspluginwrapper 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.

Live USB sticks created with unetbootin do not work

link to this item - upstream report

Third-party vendor issue
The root cause of this problem is not Fedora, but rather software provided by UNetbootin. If you are interested in a fix for this issue, you must contact that vendor through their web site.

All versions of UNetbootin since version 393 are fully compatible with making Fedora 12 Live USB drives.

Multiple reports have been received that trying to create a Fedora 12 live USB stick from the live CD images using the popular UNetbootin utility results in a non-bootable stick. Attempting to boot the stick fails completely at an early stage. No known workaround is available to make a UNetbootin-created stick work. However, you can create the stick on a Linux system using simply dd or on Fedora systems using the console livecd-iso-to-disk or graphical cross platform liveusb-creator tools. On existing Fedora systems, livecd-iso-to-disk is available in the livecd-tools package and liveusb-creator is available in the liveusb-creator package. On other Linux systems or on Windows, you can install liveusb-creator following the official instructions.

This issue has been reported to the UNetbootin developers, so they may be able to release an updated UNetbootin which works with Fedora 12 images in the future.

This issue should no longer occur with recent (newer than version 393) versions of UNetbootin.

Issues when upgrading from previous releases

As usual, the supported methods for upgrading from previous Fedora releases are to do an 'upgrade install' from the regular installation media, or to use preupgrade (see How_to_use_PreUpgrade). If you intend to upgrade using preupgrade, it is highly recommended that you install the latest preupgrade package for your current Fedora release from the updates-testing repository before proceeding, due to several issues which are documented below. Upgrading by using yum directly is not supported, but may in practice work. For known issues when upgrading via yum, see the page on this upgrade method. For additional guidance on supported upgrade methods, see section 17.2. Upgrading Your System in the installation guide.

Preupgrade free space check on /boot not thorough

link to this item - Bugzilla: #530541

Preupgrade is intended to provide a hassle-free method for upgrading a system to the current release of Fedora. Testing identified that users of Fedora 11 (and earlier) who installed their systems using the recommended /boot partition size of 200MB may not be able to upgrade their systems using preupgrade. The /boot filesystem is used to store the kernel and initial ramdisk images that form the core of the Fedora operating system. required by several utilities including grub, kernel and preupgrade.

The preupgrade utility was not properly detecting the amount of available space on the /boot filesystem prior to beginning the system update process. As a result, preupgrade would successfully complete pre-upgrade operations, and reboot the system into the installer to continue with the upgrade. After reboot, the installer would then fail indicating that insufficient disk space was available to perform the update. A screenshot of the failure message is available.

A preupgrade update is available that will properly detect the amount of disk space available in /boot. Users are advised to update to the following preupgrade package for their release before using preupgrade to upgrade to Fedora 12.

• Fedora 12 - https://admin.fedoraproject.org/updates/F12/FEDORA-2009-11536
• Fedora 11 - https://admin.fedoraproject.org/updates/F11/FEDORA-2009-11547
• Fedora 10 - https://admin.fedoraproject.org/updates/F10/FEDORA-2009-11530

After installing the updated preupgrade package, if you are still unable to proceed with an update, please refer to these additional tips to free up space in /boot.

Preupgrade does not correctly detect and handle /boot on RAID in all cases

link to this item - Bugzilla: #533545

The preupgrade tool is intended to detect when the /boot partition is on a RAID array, warn that this is a potentially troublesome configuration to upgrade, and offer a workaround. In some cases, preupgrade may fail to detect this scenario, including when the RAID array in question is handled with dmraid rather than mdraid. If this happens it will continue operation without using the necessary workaround, which will result in a failed upgrade.

A preupgrade update is available that will properly detect the /boot on RAID situation in more cases. Users are advised to update to the following preupgrade package for their release before using preupgrade to upgrade to Fedora 12.

• Fedora 12 - https://admin.fedoraproject.org/updates/F12/FEDORA-2009-11536
• Fedora 11 - https://admin.fedoraproject.org/updates/F11/FEDORA-2009-11547
• Fedora 10 - https://admin.fedoraproject.org/updates/F10/FEDORA-2009-11530

Upgrade on PPC architecture does not offer boot loader configuration screen

link to this item - Bugzilla: #536705

When manually upgrading a PPC Fedora system using Fedora 12 installation media, the installer will not offer a choice to modify your boot loader configuration. Instead, the installer will default to Update boot loader configuration and proceed with the upgrade. No workaround has yet been identified for this issue.

Installation issues

/boot must be a minimum of 300 MB

link to this item - Bugzilla: #510970

If you use a separate /boot partition, it is highly recommended that it be at least 300MB in size.

Windows recovery partition available as boot option instead of Windows partition

link to this item - Bugzilla: #534066

When installing Fedora alongside Windows on a system whose manufacturer provides a special 'recovery partition' to allow the re-installation of a clean copy of Windows, the Fedora installer may incorrectly configure the system boot to the recovery partition - rather than the main Windows partition - when the Other boot menu choice is selected. To resolve this issue, edit the file /boot/grub/menu.lst - you will need root privileges to edit this file - and adjust the Other entry accordingly. In most cases, the recovery partition will be the first partition on the first hard disk, and the real Windows partition the second partition on the first hard disk. In this case, the incorrect entry will look like this:

title Other
	rootnoverify (hd0,0)
	chainloader +1

It should be corrected to look like this:

title Other
	rootnoverify (hd0,1)
	chainloader +1

If you are not sure about your partition layout, the output of the command fdisk -l can help. The restore partition and the real Windows partition should be shown with different types. The output of this command uses /dev/sda to denote the first hard disk, /dev/sdb the second, and so on; and appends the partition numbers starting at 1, rather than 0. So /dev/sda1 in the fdisk output is equivalent to (hd0,0) in grub's format, while /dev/sda2 would be equivalent to (hd0,1) and /dev/sdc5 would be equivalent to (hd2,4).

RAID /boot partition not marked bootable when bootloader is installed on it

link to this item - Bugzilla: #533533

If you install Fedora 12 with /boot on a RAID array - either as its own partition or as part of a root partition that is on a RAID array - and also install the bootloader to that partition rather than to the system MBR, the partition will not be marked as bootable, as it should be. This renders the installed Fedora unbootable. To work around this issue, you must manually mark the appropriate partition as bootable with a tool such as fdisk.

This bug should be fixed for Fedora 13 releases (anaconda-13.8-1 or greater).

Upgrading from F11 with / on an Intel BIOS RAID array results in an unbootable system

link to this item - Bugzilla: #540191 (CLOSED/WONTFIX - please use one of the workarounds below.)

If a system running Fedora-11 has its / partition on an Intel BIOS RAID array, then after upgrading to Fedora 12, the system will fail to boot because it can not find /. This is caused by F12 switching from dmraid to mdraid for Intel BIOS RAID arrays, see MDRaid Feature.

The new mdraid Intel BIOS RAID support needs /etc/mdadm.conf with info on the RAID sets to be present to find them, on a fresh F12 install this gets written by anaconda. But on an upgrade anaconda does not write configuration files (to leave the existing ones intact), causing this issue.

There are 2 possible workarounds for this:

1. Do a fresh Fedora 12 install (recommended)
2. During boot press a key to get the grub menu, then press A to append to the kernel commandline, and then add " noiswmd", this will make the system use dmraid for Intel BIOS RAID again. You can edit /etc/grub.conf to make this permanent.

Boot fails if system partition is on NFS or iSCSI on PPC architecture when installing from DVD or 6-CD media sets

link to this item - Bugzilla: #533392

The dracut-network package was mistakenly omitted from the DVD and 6-CD media sets for the PowerPC architecture. This causes boot to fail on the installed system if a crucial system partition (root or /usr for example) is accessed via NFS or iSCSI. To avoid this issue, either enable the supplementary internet repositories when doing such an installation from the DVD or 6-CD media set on the PPC architecture, or do a network install from a full tree (or at least a tree in which the dracut-network package is available).

This problem should be fixed in Fedora 13 releases.

Live installation crashes with a 'same file' error message

link to this item - Bugzilla: #533240

The Fedora 12 live installation process can crash with the following error message:

Error: `/usr/share/zoneinfo/America/New_York` and `/etc/localtime` are the same file

under certain circumstances. This is believed to happen when an operation run between the time of booting the live image and the time of running the installer turns the file /etc/localtime into a symlink to another file. It may be triggered by manually setting the system clock, and/or enabling NTP, after booting the live image but before attempting to install it.

This issue will be resolved for Fedora 13 and later releases. To work around it, either change the time zone during the installation process, or reboot and proceed straight to installation as soon as the live image boots.

Hardware-related issues

Miscellaneous problems with Intel graphics adapters

link to this item

If you are suffering from problems with an Intel graphics adapter such as failure of X to start at all, 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.

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-intel 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.

Miscellaneous problems with ATI / AMD graphics adapters

link to this item

If you are experiencing failure to start the graphical desktop, hanging or freezing, corruption, or slow performance with an ATI / AMD graphics adapter, you may try the following.

First, make sure you have applied all system updates; some known bugs have been fixed.

Some 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.

If this does not resolve your issue, one other potential workaround is to change to a different acceleration method. To do this, add a line:

Option "AccelMethod" "XAA"

to the Device section of /etc/X11/xorg.conf. If that file does not exist, see How_to_create_xorg.conf for instructions on how to create it. Again, if doing this works around the problem you are experiencing, please check whether a bug report on the problem has already been filed, and if not, please 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. These legacy acceleration methods will be removed in future, so any bugs in the new acceleration method (EXA) need to be fixed.

If this does not resolve your issue, there is another configuration option to try. Add a line:

Option "AccelDFS" "off"

to the Device section of /etc/X11/xorg.conf. If that file does not exist, see How_to_create_xorg.conf for instructions on how to create it. Again, if doing this works around the problem you are experiencing, please check whether a bug report on the problem has already been filed, and if not, please 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.

Finally, if this still does not resolve your issue, try adding this line:

Option "DRI" "off"

to the Device section of /etc/X11/xorg.conf. Again, if doing this works around the problem you are experiencing, please check whether a bug report on the problem has already been filed, and if not, please 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.

Display cannot be reactivated if it enters sleep mode with laptop lid closed

link to this item - Bugzilla: #489907 - X.org bug #21230

Due to a known bug, on some laptops with Intel video adapters, if the display goes into sleep mode with the laptop lid closed, it will not be reactivated when the laptop lid is opened. The display will stay blank unless you reboot or use the workaround below.

A fix for this issue has been committed to the upstream kernel and may be made available in a future Fedora 12 kernel update. Some users report this problem is fixed in kernel-2.6.31.12-174.2.3.fc12 or greater, but this may be hardware dependent.

To workaround this problem, create a file with the following contents:

#!/bin/bash
xrandr --output LVDS1 --off
xrandr --output LVDS1 --auto

and save it as ~/screenfix.sh. Make it executable, and assign it to a keyboard shortcut (the method for doing this depends on your desktop environment). Executing this script via the keyboard shortcut should bring the display back to life. Note that the output parameter may vary; you can see the appropriate value for your system by running xrandr at a console and examining the output.

Another approach for more advanced users is to use acpid to get the display reset automatically. This works at least on a Thinkpad X41. You need to install acpid for it and get it running.

Single user system only
The acpid workaround works as is only if there is a single user with uid 500 that is logged in in X. In other cases this may fail. Use this workaround only if you are pretty sure to know what the commands do.

• install acpid:

  su -c 'yum install acpid'

• create the file /etc/acpi/actions/reset-display.sh with the following contents:

#!/bin/bash
# workaround for https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=489907
PATH="/bin:/usr/bin:/sbin:/usr/sbin"
export DISPLAY=:0.0
if grep open /proc/acpi/button/lid/LID/state
then
su "$(getent passwd 500 | cut -d: -f1)" -c "xrandr --output LVDS1 --off"
su "$(getent passwd 500 | cut -d: -f1)" -c "xrandr --output LVDS1 --auto"
fi

• create the file /etc/acpi/events/reset-display.conf with the following contents:

# workaround for https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=489907
event=button/lid LID 00000080.*
action=/etc/acpi/actions/reset-display.sh

• stop hald:

  su -c 'service haldaemon stop'

• start acpid:

  su -c 'service acpid start'

• start hald:

  su -c 'service haldaemon start'

• enable acpid on startup:

  su -c 'chkconfig acpid on'

Poor performance (mainly 3D) with some AMD / ATI Radeon adapters

link to this item - Bugzilla: #526967

Some aspects of graphics performance - mainly 3D performance, but also some 2D cases such as OpenOffice.org Impress effects - are known to be very poor on some ATI / AMD Radeon graphics chipsets with kernel modesetting enabled. If you are experiencing poor performance on an AMD / ATI graphics adapter, you can attempt to work around this issue by disabling kernel mode setting, using the nomodeset kernel parameter as documented above. This issue is known and is being worked on for future Fedora releases and potentially for Fedora 12 updates.

Click noise problems with audio adapters

link to this item - Bugzilla: #527286

If you are suffering from problems with an audio adapter such as frequent click noises or crackles, the following advice may be of use.

Fedora 12 enabled a power save feature for HDA audio devices, and set the default power save timeout to 5 seconds. Each time the device goes into power save state, or wakes up from power save state when playing sound, it may produce a click sound.

This problem should be fixed in kernel versions 2.6.32.3 and greater, which should be available as an official update soon (currently available for testing). If you are still experiencing crackles after upgrading your kernel, please file a new bug. In the meantime, you can also try the following workaround to diagnose and solve this problem.

On systems using the snd_hda_intel kernel module (Intel HD Audio adapters) this can be disabled by executing the following command as root:

echo 0 > /sys/module/snd_hda_intel/parameters/power_save

If it fixes your problem, you may permanently configure this parameter by appending

snd_hda_intel.power_save=0

as a kernel parameter.

Boot pauses for a long time, with tpm_tis 00:0a: tpm_transmit: tpm_send: error -62 error displayed on console

link to this item - Bugzilla: #530393

Users of several systems, including Acer Travelmate 6465, 6592 and 6492 models, Zepto 6625WD and 6024W models, and Sony Vaio SZ7 series models (including, but likely not limited to, SZ71VN/X, SZ75MZ, SZ750N), have reported that their systems pause for several minutes during boot. If the boot process is set up so the console is visible at that point, the error message tpm_tis 00:0a: tpm_transmit: tpm_send: error -62 is shown on the console. Boot does eventually proceed, and the system works without side effects. There is no solution for this problem at present, but a workaround is available. Adding tpm_tis.interrupts=0 as a kernel parameter should avoid the problem in most cases.

Software issues

CD tray problems or slow boot after installation from live CD

link to this item - Bugzilla: #527781

When installing from a live CD, the anaconda package is installed on the system. It includes some custom udev rules in the file /lib/udev/rules.d/70-anaconda.rules. These rules have been reported to cause various problems, ranging from CD trays closing again right after ejecting a CD or boot hanging in udev for a long time.

If your system shows these symptoms, you can simply remove the anaconda package. It is not needed once you have completed installation of the system.

This problem is fixed in Fedora 13 (anaconda-13.5-1 or greater).

Intel BIOS RAID arrays created after installation not detected

link to this item - Bugzilla: #537329

Due to incomplete handling in the initialization scripts, Fedora 12 will not correctly recognize Intel BIOS-managed RAID sets created after Fedora has been installed. This type of RAID set will, however, be correctly handled if it exists at install time. This issue can be worked around by adding the parameter iswnomd to the kernel command line, which can be achieved by editing /boot/grub/menu.lst. You may also wish to consider creating the array as a Linux software RAID array rather than a BIOS-managed array; this will make it portable between different Linux systems, and avoid this issue.

An update may be made available to address this issue, however it is not a straightforward issue to fix so this may not be possible or may take some time.

Non-Fedora Mozilla/Firefox binaries may crash

link to this item

Third-party vendor issue
The root cause of this problem is not Fedora, but rather software provided by Mozilla. If you are interested in a fix for this issue, you must contact that vendor through their web site.

There is a conflict between binary software downloaded from Mozilla and software included in Fedora which may lead to a crash, often seen when using Flash. See this page for details and workarounds.

FUSE mounts may hang

link to this item - Bugzilla: #493565

When audit is enabled and FUSE file systems are being mounted, a deadlock may happen which causes the mount to block indefinitely. A common symptom of this bug is that the user's Home folder appears to be empty when opened with Nautilus. Running the

ls -la

command in the user's home directory will also hang. Some users have reported that a reboot will fix the problem, others have reported that they need to do a file system check. To have the system check its file systems during the next boot, create an empty file named forcefsck in the / directory:

su -c 'touch /forcefsck'

This will only be a temporary fix and the problem will most likely appear again. The developers are working on fixing this issue in the Linux kernel.

Changes in CCSM do not affect Compiz

link to this item - Bugzilla:#532229

In GNOME, changes in ccsm (CompizConfig Settings Manager) do not affect Compiz behavior. To work around this issue, install the compizconfig-backend-gconf package. Then, in CCSM, go to Preferences, and choose "GConf Configuration Backend" in the Backend section.

ABRT alert icon states that ABRT service did not start

link to this item - Bugzilla:#552869

After installing new or upgrading, the ABRT alert icon shows up on the desktop. The alert icon states that the ABRT service did not start. This issue is caused by ABRT's default configuration file trying to utilize ABRT plugins that are not installed by default. There are two workarounds to resolve this issue:

• Install all ABRT plugins:

yum install abrt-desktop

• Edit /etc/abrt/abrt.conf and remove references to ABRT plugins that are not installed.

You will need to restart the ABRT service after you complete the chosen workaround in order for the changes to take effect. Also, right click on the ABRT alert icon and click on quit. Or simply restart the system.

Fedora 12 32-bit installations cannot successfully host KVM virtual machines

link to this item - Bugzilla:#572215

Testing has indicated that trying to host KVM virtual machines (such as created through the virt-manager GUI) on a 32-bit Fedora 12 installation is unsuccessful. This bug affects only 32-bit installations; 64-bit installations have no problem hosting virtual machines.

An updated qemu package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, run this command:

su -c 'yum --enablerepo=updates-testing qemu'