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.
Fedora 14 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 14 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).
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
Attempting to submit (scp or bugzilla) an exception report fails if networking not active
When installing Fedora 14 Beta using CD, DVD or hard drive ISO media, if an exception occurs, the installer will be unable to submit the exception report using the built-in
tool as networking has not yet been enabled. This means you will be unable to submit the exception report directly to http://bugzilla.redhat.com or to another system using the network. The problem will be resolved in time for Fedora 14 Final. However, until the issue is resolved, you will need to manually enable networking in order to report an installer exception directly to http://bugzilla.redhat.com. When installing Fedora 14 Beta using CD, DVD or hard drive ISO media, to report an exception you may enable networking using the following procedure:
- Change to the debug console by pressing
- Obtain a dynamically assigned IP address by typing:
dhclient -v eth0
Alternatively, you may boot the installer with the appropriate networking information as boot arguments. For more information, see Anaconda/Options.
Nautilus not responding
When viewing the content of large directories (>500 files and with medium CPU), the CPU gets 100% resources and Nautilus seems freezing, taking much time (~ minutes) to visualize its content. The same happens when viewing these huge directories with others applications (e.g. firefox).