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.
Fedora 13 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 13 pre-releases. Issues that are fixed will be removed from the page once a fix is available (for instance, an issue that affects the Beta but is fixed in the final release will be removed at the time of that release).
Release Summary, Announcement and Notes
Read the F13 Alpha release announcement and the draft Fedora 13 release notes for specific information about changes in Fedora 13: 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
- 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)
Installation issues
Failure to eject CD-ROM when prompting for next disc
link to this item - Bugzilla: #569377
During a Fedora 13 Alpha CD-ROM installation, the installer may fail to properly eject the media when prompting for a subsequent installation disc. Investigation appears to show that performing a media check on the ISO media may trigger this failure later during install.
If you encounter this issue while installing from CD-ROM media, you may work around the problem using the procedure detailed below.
- When prompted to insert the next disc, change to the debug shell on tty2 by pressing <Control><Alt>F2
- Eject the disc by typing:
eject /dev/cdrom - Insert the requested installation disc number
- Prepare the disc by typing:
mount -o ro /dev/cdrom /mnt/source - Return to the installer by pressing <Control><Alt>F6
The above procedure may be repeated for each installation disc needed to complete the install.
Installing on a system with previously encrypted block devices fails - LVMError: lvactivate failed for lv_root
link to this item - Bugzilla: #565848
When installing Fedora 13 Alpha on a system with an existing encrypted block device, you will encounter a failure if you attempt to reformat the system. Until resolved, whenever installing Fedora 13 Alpha on a system with encrypted block devices, it is recommended that you do not provide the passphrase to unlock the existing encrypted block devices. When prompted for a passphrase, press Cancel. Alternatively, you may choose to erase any partition information from disks affected by running a command similar to the following.
dd if=/dev/zero bs=512 count=1 of=/dev/sda
.png){kind=small}
Please backup any data before erasing the partition table. It is likely that you will be unable to recover the information on the disk after executing the
dd command.
Installation using LVM requires a large amount of RAM (over 512MB)
link to this item - Bugzilla: #559290
Due to a bug in 
lvm2
Software issues
PackageKit silently fails to update
link to this item - Bugzilla: #567346 Bugzilla: #569352
After installing Fedora 13 Alpha, some testers experienced a problem where the Software Update utility (provided by
It is believed that a yum plugin provided by yum. Testing also demonstrated that the problem was difficult to reproduce and depends on whether the yum-langpacks plugin is installed, and whether certain conditions exist in the package repositories used during the update.
If you are unable to update your system and the problem description above matches your symptoms, you may work around the issue by removing the
- Open a terminal and type:
su -c 'yum remove yum-langpacks' - Or, from the default Desktop environment
- Select the System -> Administration -> Add/Remove Software menu item
- Enter the text yum-langpacks in the text-box
- Deselect the check-box associated with
yum-langpacks
KDE graphical package management fails to run at all
link to this item - Bugzilla: #568931
There is unfortunately a version mismatch in Fedora 13 Alpha images between su -c 'yum update kpackagekit'. Enter your root password when prompted to do so. If the KDE package management tools still fail to launch even after this, try doing a full system update with yum: su -c 'yum update'. If that encounters dependency problems, try su -c 'yum update --skip-broken'.
GNOME cannot store new secrets (passwords)
link to this item - Bugzilla: #558678
There is a bug in the
Print operations cause Firefox to crash
link to this item - Bugzilla: #553834
Due to an underlying problem in
GNOME Shell fails to run at all
link to this item - Bugzilla: #567116
Fedora 13 Alpha includes version 1.2 of the Clutter toolkit, but