|Line 292:||Line 292:|
# Next, add an exception by selecting ''Exceptions'' and add <code>http://www.youtube.com</code> then select ''Block''
# Next, add an exception by selecting ''Exceptions'' and add <code>http://www.youtube.com</code> then select ''Block''
# Finally, close the firefox preferences dialog.
# Finally, close the firefox preferences dialog.
Revision as of 18:19, 12 September 2010
This page documents common bugs in Fedora 13 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.
Read the Fedora 13 release notes for specific information about intentional changes in Fedora 13, 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
- 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)
Issues when upgrading from previous releases
Preupgrade doesn't work with default-sized /boot partition
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 12 (and earlier) who installed their systems using the recommended
/boot partition size of 200 MiB will 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. Its presence is required by several utilities including
Users that have
/boot partition size of at least 250 MiB should not have problems with using preupgrade. For others it is recommended to simply download Fedora 13 DVD/CD/netinst install medium and do a standard system upgrade. More experienced users that still want to use preupgrade may refer to these additional tips to free up space in /boot.
For Fedora 13 the default
/boot partition size was increased to 500 MiB to avoid these problems in the future.
Text-mode upgrade fails when installing new bootloader
Users upgrading to Fedora 13 using the text-mode installer are advised to not select Create a new bootloader configuration. Creating a new bootloader configuration is not an intended function for the text-mode installer. Instead, users are advised to choose the upgrade or skip bootloader configuration options during a text-mode upgrade.
This issue has been resolved in future versions of
Upgrade fails with fstab entry is malformed exception
Multiple users have reported a failure when trying to upgrade an existing Fedora installation. The installer gives an exception of the format:
fstab entry /dev/sda3 is malformed: scanned format (ext3) differs from fstab format (swap)
where the entry and both formats may be different. This happens because the installer is quite strict about the formats it will accept in the
/etc/fstab file: entries which are valid for actual mounting purposes are rejected by anaconda in some situations. Common cases where this issue is encountered include entries which specify the formats ntfs-3g or auto. It is usually possible to work around this issue by changing the format in the problematic
/etc/fstab entry. If the problematic format is ntfs-3g, change it to ntfs. If the problematic format is auto, then change it to the actual format of the affected partition.
You may also encounter this issue if mounting an ext3 partition as ext2, or an ext4 partition as ext3 or ext2. In this case, you can work around the issue by adjusting the configuration to mount the partition with its actual native type during the upgrade.
One other situation where you may encounter this issue is if the
/etc/fstab file lists devices in the /dev/sdXX format, and the Fedora installer enumerates your devices differently from the installed system (for instance, the F13 installer considers a disk to be /dev/sdc but the installed system considers the same disk to be /dev/sda). In this case, you should adjust
/etc/fstab to refer to devices by their UUIDs or labels.
64-bit DVD appears unbootable on some systems (especially Gigabyte motherboards)
Several users have reported that the 64-bit DVD Fedora 13 image cannot be booted on their systems. The system does not see the burned disc as a bootable disc at all, and proceeds to boot from the next listed boot device. The burned disc passes validation and can successfully boot on other systems. This bug appears to affect systems with Gigabyte motherboards in particular; almost all reporters have Gigabyte motherboards.
One known workaround is to use a different image for installation. The 64-bit live images and network installation image (netinst.iso) and the 32-bit DVD image are known to boot successfully on most affected systems. Obviously, installing from the 32-bit DVD image will give you a 32-bit Fedora installation.
Another workaround reported in the bug by Bob Weaver is to boot with the 32-bit DVD inserted until the first menu screen (where you can choose to Install, or various other options) appears, then eject the 32-bit DVD and insert the 64-bit DVD before selecting Install.
We are investigating this issue but have yet to identify the cause or any possible fixes.
Unable to activate some Intel gigabit network devices when booting some systems using PXE
When booting the installer from a network device using PXE, a problem has been identified where the network device does not reset after performing the PXE boot. The result is that the Fedora 13 installer to fails to activate the network for installation. Systems affected include those with Intel gigabit network adapters 82577 and 82578.
To confirm whether your system may be impacted by this issue, from a command-prompt, type:
# lspci -d 8086:10ea | grep -q Intel \ && echo "Sorry, your system may be impacted by bug#580563." \ || echo "Congratulations, you are not affected by bug#580563."
If your system contains Intel gigabit network adapters affected by RHBZ #580563, updated
pxeboot installation images are available for download at http://jlaska.fedorapeople.org/updates/580563. For more information on booting the Fedora 13 installer using PXE, refer to the installation guide.
Space, Enter, and arrow keys don't work in x86_64 VNC installs
Due to a bug in
, some keys may not be work as expected when installing Fedora 13 64-bit using
vnc. While some keys may not work as expected, users are still able to complete the install as directed using the mouse and keyboard. While this issue is resolved in future versions of Fedora, users may work around this problem by using an
updates.img when installing Fedora 13 64-bit using
vnc. For assistance on using an updates.img, refer to Anaconda/Updates.
Traceback when going back to modify Installation Repo
After customizing the install package set using the Customize Now option, users may encounter a failure when returning to the previous step and attempting to modify the Installation Repo. An
updates.img is available that works around the reported problem. For assistance on using an updates.img, refer to Anaconda/Updates.
AttributeError: 'Ext4FS' object has no attribute 'mapName'
While testing Fedora 13, some users encountered problems while partitioning their disks. The cause of the failure is not yet known. The exact failure message changes depending on the partition selections. For example, the following failure messages were observed:
- AttributeError: 'Ext3FS' object has no attribute 'mapName'
- AttributeError: 'Ext4FS' object has no attribute 'mapName'
- AttributeError: 'BTRFS' object has no attribute 'mapName'
Users experiencing this problem while installing Fedora 13, are advised to reboot the installer and retry. The reported problem does not occur on subsequent installs.
SystemError: (22, 'Invalid argument')
When installing Fedora 13 from a remote NFS share, you may encounter an exception referring to SystemError: (22, 'Invalid argument'). Investigation into the problem indicates the failure will occur when the Fedora installation boot media does not match the remote installation media available via NFS share. Users are directed to confirm that Fedora release used to boot the installer matches the Fedora available on remote NFS share. Users can confirm the boot media and remote installation media match by ensuring the contents of the
.buildstamp match. The
.buildstamp is available inside the
images/install.img file. See the example below for guidance on inspecting the
# mount -o loop /dev/sr0 /media # mkdir /tmp/squashfs # mount -o loop /media/images/install.img /tmp/squashfs # cat /tmp/squashfs/.buildstamp 201005130056.i386 Fedora 13 https://bugzilla.redhat.com
Booting from an mdraid mirror without a separate /boot fails
Installing a new system with / on an mdraid mirror without a separate /boot will fail as anaconda creates the / mdraid set with 1.1 metadata which makes it unsuitable to boot from. Workaround: use a separate mdraid mirror for /boot if you want to boot from an mdraid mirror. This issue will be fixed in Fedora 14.
ValueError: Cannot remove non-leaf device
While modifying an existing software RAID1 disk configuration, users may encounter a failure while attempting to re-use the existing software configuration for another software RAID installation. Installing a new software RAID configuration will not result in failures. Specifically to Bugzilla #569469, a failure occurs while attempting to create a new software RAID5 device using the existing RAID1 disk members where there are insufficient RAID members to needed for the desired RAID installation. Users can work around this problem by creating a software RAID setup from scratch, or by creating a sufficient number RAID members before reusing an existing RAID device.
iSCSI install will not boot
Users may encounter a boot failure after installing Fedora 13 to a remote iSCSI volume. The problem is caused by the
iscsistart command failing while attempting to find the root device on boot. An updated
package that resolves the reported problem is available. Users installing Fedora 13 to a remote iSCSI volume are advised to enable the Fedora 13 Updates package repository during installation to ensure that the latest
package is installed.
Network goes down due to clock jump during install process, resulting in problems if using network resources
If changing the system clock settings during install results in a sudden large jump in the system clock - which can often happen, usually when selecting a time zone substantially different from the default Eastern time and/or adjusting the system clock uses UTC setting - any active network connection may go down. Obviously, if you are performing a network-based install, this can lead to it being impossible to complete the installation. To work around this issue, try using the default time zone settings during installation, and adjusting for your time zone after installation.
Hard Drive install fails when improperly specifying remote package repository
Users who install Fedora 13 using installation media on an existing hard drive partition (see installation guide), may encounter a failure when specifying a remote package repository for additional software updates. The problem appears to be the result of specifying a mirrorlist URL for the remote package repository, while failing to select URL is a mirror list option.
To resolve this issue, users are advised to select the URL is a mirror list option when adding a remote package repository mirror. Kickstart users are advised to use the appropriate keyword argument:
repo --name=<name> [--baseurl=<url>|--mirrorlist=<url>] [options]
. For additional information on the kickstart
repo command, see kickstart documentation.
Installations fail in anaconda with an error relating to lvm, i.e. lvm create, resulting in the abort of the installation
To resolve the installation abort, allocate at least 512MB memory into a virtual machine, or even a physical machine. The installation should work then. See the bugzilla entry for more information on the cause of the bug. A test xen DomU instance was dropped back to 256MB after installation, result being, the system boots and runs fine in runlevel 3.
Security: sshd is running during kickstart installs, allowing remote access to the anaconda install system
sshd is running during kickstart installs and there is no root password by default, allowing unauthorized remote access to the installation system. To avoid running sshd during kickstart installs, add sshd= to anaconda's kernel command line.
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 13, 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 initial bootloader screen to allow configuration of the kernel parameters, and add the parameters xdriver=vesa nomodeset.
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 13 (Goddard)"', 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
Compiz fails to work on older Intel chipsets
Reports indicate that Compiz fails to run on older Intel graphical chipsets, including the i845 chipset and probably other i8xx-generation chipsets. Attempting to enable Compiz will result in a crash which is picked up by abrt (the automated bug reporting tool). We may be able to address this bug with an update, but until that time the only known workaround is not to use Compiz on such hardware.
Boot pauses for a long time, with tpm_tis 00:0a: tpm_transmit: tpm_send: error -62 error displayed on console
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.
Network doesn't connect
After installation from physical media (e.g. CD or DVD), users may notice that programs requiring the network can not connect to the network. If this is the case, the NetworkManager icon may show an X indicating that the machine is not currently connected. While all networking hardware is correctly wired, and device indicators show the network to be properly connected, a change in default install behaviour means that the network does not immediately connect.
The required procedure from this point is to click the NetworkManager icon, and activate the System eth0 or similar connection. If the X disappears from the NetworkManager icon, then this was the issue that was stopping the connection from being activated.
However, the above change is only for the current login. To make this change permanent, right click the NetworkManager icon, Edit connections, select the System eth0 or similar, click Edit, provide the root password, check the Connect automatically item at the top of the dialog box, Apply and Close.
Please also see the future release note describing this, and a graphical description of the steps to take to make this setting.
Gnome-panel crashes when opening workspace switcher preferences
A bug in the GNOME workspace-switcher applet may cause the
gnome-panel to crash. The problem appears to be triggered by right-clicking on the workspace-switcher applet, and selecting Preferences.
An updated gnome-panel 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.
Picasa fails to login to google
Google bundles a version of wine with their picasa package (bad google). This version of wine is linked against a different libssl library and therefore won't work with https addresses which is needed to login to google services.
This can be fixed by doing the following:
- Install wine via Yum:
yum install wine
- Copy the correct library to picasa:
cp /usr/lib/wine/wininet.dll.so /opt/google/picasa/3.0/wine/lib/wine/wininet.dll.so
Gnash fails to play youtube videos
The GNU flash movie player (
) fails to play youtube videos (with necessary codecs installed) after the first youtube visit with the message : "An error occured, please try again later." inside the player. The problem appears to be due to mishandling of browser cookies. To workaround the issue, delete youtube cookies, then block cookies from youtube.
- Open firefox preferences by selecting Edit → Preferences from the firefox menu
- In the preferences window, choose the Privacy tab
- Under History, set the value of Firefox will to Use custom settings for history
- Next, remove any youtube cookies by selecting Show Cookies. Enter
youtubein the search box, and click "Remove Cookies". Close the Cookies dialog when finished.
- Next, add an exception by selecting Exceptions and add
http://www.youtube.comthen select Block
- Finally, close the firefox preferences dialog.
Not receiving update notifications
Updates to Fedora introduced two unexpected bugs, either of which results in users no longer seeing notifications of or being able to apply new updates.
Updates to the relevant packages have been shipped to fix these issues, but users will not receive notifications for them unless they first apply the pending fixed updates using the "yum" tool. Packages fixing these issues were pushed to the Fedora software repositories around July 22, 2010. Users who have done a manual "yum update" since that push may have already received these fixes.
To fix the issue, please:
1. Open a Terminal (Applications > System Tools > Terminal)
2. Type either of the following commands and enter the password for the root user when prompted.
a. To choose to apply all pending updates now:
su -c "yum -y --skip-broken update"
b. To choose to apply updates fixing only the specific issues mentioned above:
su -c "yum -y --skip-broken update gnome-packagekit selinux-policy"
3. Log out and and then log back in, or reboot your computer. Note that logout/login will complete the fix for the notification issue. However, if you applied all updates in the previous step, you may need to reboot for other updates that require it.