From Fedora Project Wiki

(Add bug#635821)
(clean up for Beta, remove a bunch of dead issues)
Line 68: Line 68:
  
 
Alternatively, you may boot the installer with the appropriate networking information as boot arguments.  For more information, see [[Anaconda/Options]].
 
Alternatively, you may boot the installer with the appropriate networking information as boot arguments.  For more information, see [[Anaconda/Options]].
 
{{Anchor|incomplete-previous-install}}
 
=== TypeError: sequence item 0: expected string, NoneType found ===
 
<small>[[Common F14 bugs#incomplete-previous-install|link to this item]] - [[rhbug:621685|Bugzilla: #621685]]</small>
 
 
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, {{filename|/etc/fedora-release}} may not exist, resulting in a traceback. 
 
 
The problem has been fixed in [http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=1cf0ab74176b8203ffb590c47c508716fb4a5727 anaconda.git] and is resolved in Fedora 14 Beta.  An [http://jlaska.fedorapeople.org/updates/621685.img updates.img] is available to resolve the issue for Fedora 14 Alpha.  For information on using an updates.img, see [[Anaconda/Updates]].
 
 
{{Anchor|radeon-anaconda}}
 
=== System appears to hang with a black screen when installing on systems with ATI/AMD Radeon graphics cards ===
 
<small>[[Common F14 bugs#radeon-anaconda|link to this item]] -  [[rhbug:596985|Bugzilla: #596985]]</small>
 
 
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 {{filename|/etc/X11/xorg.conf}}
 
# Remove all occurrences of the word ''nomodeset'' from the file {{filename|/boot/grub/grub.conf}}
 
# Reboot
 
 
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 {{command|system-config-display}} tool to select the vesa driver.
 
 
{{Anchor|f13-graphics}}
 
=== Fedora 13 graphics appear during installation ===
 
<small>[[Common F14 bugs#f13-graphics|link to this item]] - [[rhbug:621027|Bugzilla: #621027]]</small>
 
 
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.
 
  
 
== Hardware-related issues ==
 
== Hardware-related issues ==
Line 101: Line 73:
  
 
== Software issues ==
 
== Software issues ==
 
{{Anchor|net-auto-connect}}
 
=== Network not connected automatically for non-live installs ===
 
<small>[[Common F14 bugs#net-auto-connect|link to this item]] - [[rhbug:620823|Bugzilla: #620823]], [[rhbug:498207|Bugzilla: #498207]]</small>
 
 
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 - [[rhbug:498207|#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.
 
 
{{Anchor|systemd-update}}
 
=== systemd package update breaks default boot target ===
 
<small>[[Common F14 bugs#systemd-update|link to this item]]</small>
 
 
After installing Fedora 14 Alpha, and performing a system update to pull the latest packages for testing, an update to systemd may break the default boot target link.  If you have problems booting afterward, you may need to add <code>3</code> or <code>5</code> to the kernel line in GRUB to boot successfully to runlevel 3 or 5, respectively.  This is a known problem and the developers are working on a less fragile update for people who install the Alpha in the future.
 
 
To repair this problem, perform the following steps, as root:
 
<pre>cd /etc/systemd/system
 
# Then ONE of the following...
 
# * For runlevel 5:
 
ln -sf /lib/systemd/system/graphical.target default.target
 
# * For runlevel 3:
 
ln -sf /lib/systemd/system/multi-user.target default.target</pre>
 
 
{{Anchor|kde-printer-abrt}}
 
=== kdeutils-printer-applet crash notification on starting KDE ===
 
<small>[[Common F14 bugs#kde-printer-abrt|link to this item]] - [[rhbug:620823|Bugzilla: #615651]]</small>
 
 
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.
 
  
 
{{Anchor|Nautilus freezes}}
 
{{Anchor|Nautilus freezes}}
Line 133: Line 79:
  
 
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).
 
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).
 
{{Anchor|acpid-boot-pause}}
 
=== Boot pauses for up to 60 seconds, apparently doing nothing ===
 
<small>[[Common F14 bugs#acpid-boot-pause|link to this item]] - [[rhbug:629740|Bugzilla: #629740]]</small>
 
 
Due to a misconfiguration in the acpid service unit file, if acpid is installed and enabled on your system it may cause the boot process to pause for up to 60 seconds, with no obvious feedback. acpid will also fail to start. If you review the system logs you may notice failure messages from the acpid service during boot. To work around this issue you may remove the acpid package or disable the acpid service with the command {{command|systemctl disable acpid.service}}, which will cause no problems unless you have manually created scripts that depend on the events provided by the acpid service (these will not work in any case unless you start acpid manually). An update will be released to address this issue shortly.
 

Revision as of 00:31, 28 September 2010

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).

Release Notes

Read the F14 Alpha release announcement and the draft Fedora 14 release notes for specific information about changes in Fedora 14: 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
    1. a summary of the problem
    2. any known workarounds
    3. 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

Installation issues

Attempting to submit (scp or bugzilla) an exception report fails if networking not active

link to this item - Bugzilla: #635821

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 Package-x-generic-16.pngreport 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:

  1. Change to the debug console by pressing Control-Alt-F2
  2. 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.

Hardware-related issues

Software issues

Nautilus not responding

link to this item - Bugzilla: #626108

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).