Common F13 bugs
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
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
Installer fails after upgrade with writeGrub() error
During a system upgrade using the Fedora 13 Alpha installer, a failure will present after the upgrade process has completed. A sample failure is available for comparison. The presence of this failure does not impact the upgraded system. In fact, you may reboot the installer and return to your upgraded Fedora 13 system. This bug has been fixed in
and will be available in Fedora 13 Beta. Until then, should you wish to workaround the bug, a updates.img is available. For help using an updates.img, see Anaconda/Updates.
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.
Black screen while attempting preupgrade or graphical kickstart install
preupgrade, or anyone performing a graphical kickstart install, may notice a black screen while attempting to install or upgrade the system. There is a possible race condition when starting X which may result in being unable to perform a graphical kickstart install or upgrade. Additional technical information on this problem is available on firstname.lastname@example.org. If you are impacted by this problem, an updates.img is available to workaround this problem. Information on how to create and use an updates.img is available at Anaconda/Updates.
Failure to eject CD-ROM when prompting for next disc
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, This problem has been resolved in Fedora 13 Beta or newer.
Adding additional network package repository fails
During installation, attempting to add a new network package repository may result in a failure. Using or modifying existing package repositories (e.g. Fedora 13 Updates Testing) will not result in a failure. Additional technical information on this problem is available on email@example.com. If you are impacted by this problem, an updates.img is available to workaround this problem. Information on how to create and use an updates.img is available at Anaconda/Updates.
Installation using LVM requires a large amount of RAM (over 512MB)
Due to a bug in
, installing Fedora 13 Alpha and Fedora 13 Beta with any partition layout that involves LVM (including the default configuration) requires a large amount of system memory. Often, 512MB is not enough. While 1GB usually is; extensive testing has not been done at levels between these two. If you are installing Fedora 13 Alpha or Fedora 13 Beta on a system with less than 1GB of physical memory, you may need to use a custom partition layout with no use of LVM. If you are installing into a virtual machine, please allocate 1GB or more of memory to the virtual machine for the installation phase. You may be able to reduce the memory allocated to the virtual machine after installation.
Kickstart install with firewall --disabled activates firewall
Installing a system with the kickstart parameter firewall --disabled will result in a system with a firewall enabled and
ssh access denied. Users experiencing this problem can manually open the ssh port using the utility
system-config-firewallfrom a Terminal, or by selecting the menu item System → Administration → Firewall
- When prompted, enter the root password
- Disable and re-enable the SSH service
- Click Apply
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.
PackageKit silently fails to update
After installing Fedora 13 Alpha, some testers experienced a problem where the Software Update utility (provided by
) fails to update the system software when requested. The Software Update utility will quickly report that the software update has completed without actually downloading and installing any updates. Running the Software Update utility again will show that no updates have been applied.
It is believed that a yum plugin provided by
may introduce package dependency conflicts, which will cause the update to silently fail. The problem may affect upgrades using both the Software Update utility and
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.
- Open a terminal and type:
su -c 'yum remove yum-langpacks'
- Or, from the default Desktop environment
GNOME Shell fails to run at all
Fedora 13 Beta includes version 1.2 of the Clutter toolkit, but
has not yet been ported to work with this version. As a consequence, in Fedora 13 Beta, any attempt to use GNOME Shell will fail. Work to port GNOME Shell to Clutter 1.2 is under way, and we hope to include a usable GNOME Shell in Fedora 13.