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).
- 1 Release Notes
- 2 My bug is not listed
- 3 Issues when upgrading from previous releases
- 4 Installation issues
- 5 Hardware-related issues
- 6 Software issues
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
TypeError: sequence item 0: expected string, NoneType found
When installing Fedora 14 Alpha on a system with a previously attempted, but incomplete installation, the installer will fail while scanning the disk partitions. The problem is caused by attempting to determine which Fedora release is already installed. If the previously installed system was incomplete,
/etc/fedora-release may not exist, resulting in a traceback.
System appears to hang with a black screen when installing on systems with ATI/AMD Radeon graphics cards
Due to a bug in X.org, many testers indicated that, when installing Fedora 14 Alpha using the traditional installer (i.e. installing from the DVD or split CD media, not a live image), the system apparently hangs at a black screen when switching from text to graphical mode early in the installation process. The system is not in fact hung, but the display will remain blank until the system is rebooted. The bug that causes this problem could theoretically manifest with any hardware, depending on the contents of memory, but in practice it appears to occur consistently on many systems with ATI/AMD Radeon graphics cards, and - as far as we are aware - not on other systems.
To work around this issue, when the installer first boots, select the option labelled Install system with basic video driver at the initial boot menu. Now proceed with installation as usual. After installation, your system will still use the 'basic video driver' (vesa), which will lead to sub-optimal performance. If you would prefer to switch to the native driver - which most testers indicated works perfectly well once installation is complete - follow this procedure:
- Delete or rename the file
- Remove all occurrences of the word nomodeset from the file
Some testers with cards in the Radeon 5xxx series encounter a bug with similar initial symptoms, but which actually affects all ability to use X.org with the native driver, not just the traditional Fedora installer. Installing using the basic video driver option is also a workaround for this case, but you should not revert to the native driver after installation in this case. If you attempt to revert to the native driver and find the system now fails to boot correctly, either reinstall and do not follow the procedure to revert to the native driver after installation, or boot the system with the kernel parameter '3' or in rescue mode, and use the
system-config-display tool to select the vesa driver.
Fedora 13 graphics appear during installation
When installing Fedora 14 Alpha - whether from DVD, live image, network install or any other method - you will probably notice the background to the installer window is a Fedora 13 graphic. This is simply a cosmetic bug; an updated image for Fedora 14 was not ready in time for the Alpha release. You are really installing Fedora 14 Alpha, not Fedora 13, and there are no practical consequences of this cosmetic issue. Some live spins may use Fedora 13 desktop backgrounds rather than the Fedora 14 backgrounds; again, this is a purely cosmetic issue with no further consequences.
Network not connected automatically for non-live installs
When installing Fedora 14 Alpha in any way other than from a live image, available network connections will not be enabled at boot time - even if they were used during installation. This is a long-standing known issue - #498207 - for installs which do not use the network, but new for For network installs. Available network connections can be activated and configured to start at boot time in future by using the NetworkManager applet in the system tray.
kdeutils-printer-applet crash notification on starting KDE
When loading a KDE desktop in Fedora 14 Alpha - whether booting from the KDE live image, or booting an installed KDE desktop - you will see an abrt crash notification for the kdeutils-printer-applet utility. This crash was reported and fixed prior to Fedora 14 Alpha's release, but the fix did not make it into the release images. This issue should be resolved after the first update to the installed system. As the crash has already been reported and resolved, there is no need to file a bug report for the crash, as abrt offers.