Common F14 bugs
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 configure the network with the Configure Network button that appears at the hostname selection stage of installation, if your bug occurs after this point. You can also boot the installer with the appropriate networking information as boot arguments. For more information, see Anaconda/Options.
Error setting up repository - 16, Device busy
When installing Fedora 14 Beta by using either
livecd-iso-to-disk to write a F-14 Beta
boot.iso to USB flash drive or performing a hard drive ISO or NFS ISO install using a directory containing multiple ISO images, one may encounter a failure dialog indicating Error setting up repository - 16, Device busy. This problem will be resolved in Fedora 14 Final. For users hitting this problem in F-14-Beta, there is an updates.img available to work around this problem. For guidance using an updates.img, see Anaconda/Updates.
Exception occurred when going back to the first step of installation
For the ones who wants to install F14 Beta on the disk which a preivous *Fedora* system was already installed on, after you begin the installation and see the partitioning layout, clicking back to the first welcome screen may cause Exception occurred: 'IndexError: list index out of range' where "upgrade screen" should be displayed.
This bug has been marked as F14Blocker. Install through VNC could also trigger this issue. So before it's been fixed, when you have proceeded to partitioning layout step, don't try to go back to the first screen of anaconda.
'ImportError: No module named product' occurred during EFI install with netinst.iso
Exception would occur saying 'ImportError: No module named product' when using boot.iso for EFI install. The problem is that it needs to import from pyanaconda.product instead of product. The recommended workaround is to use images other than netinst.iso for EFI installs before it's been resolved.
AttributeError: 'NoneType' object has no attribute 'name'
One may encounter this bug when installing a F-14 live image on BIOS RAID device. This is caused by biosraid devices that were mapped via device-mapper but not assigned a UUID by the same. For most instances, using the non-live installer will prevent this bug from appearing. This bug has been marked as F14Blocker.
VESA driver fails in qemu/kvm machines, system hangs at X init
In qemu/kvm, if you install F-14 Beta images by selecting the grub option Install system with basic video driver or by adding kernel parameter xdriver=vesa, system will hang and show a black screen at the beginning of stage 2 where graphical anaconda is supposed to be displayed. No input works and other ttys are all black. This is due to VESA driver is not compatible with virtual cirrus card and will be fixed in Final cycle.
F-12 to F-14 upgrade results in unusable package manager due to broken EVR
the yum version in F-12 is higher then the yum version shipped with F-14beta1, resulting in yum not being upgraded. However, its dependancy with python is updated, so no functional yum is left after system upgrade. A manual rpm -Uhv --force using the install media is required to fix this. This was an upgrade attempt via DVD medium.
Bluetooth disabled on system start
Due to a bug in the
package, Bluetooth will show as disabled on each system start with Fedora 14 Beta. This can be worked around in the GNOME desktop by right-clicking the bluetooth icon in the panel and selecting Turn Off Bluetooth, then right-clicking the icon again and selecting Turn On Bluetooth. It can also be worked around from the console by running the command
su -c 'service bluetooth restart'.
An updated bluez package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, run this command:
su -c 'yum --enablerepo=updates-testing update bluez'
Nautilus and file dialogs appear to hang when viewing large directories
Some users have reported that when viewing the content of large directories (>500 files) in Nautilus (the file manager of the GNOME desktop), CPU utilization can reach 100% and Nautilus may seem to have hung, before finally showing the directory contents several minutes later. This can also affect the file open and file save dialogs in GTK+-based applications.
Brasero crashes when asked to burn a disc
Brasero, the GNOME disc burning application, crashes whenever you try to burn a disc in Fedora 14 Beta. A fix for this has been identified and a fixed package should be made available soon. No known workaround is available to make Brasero work, but various alternative disc burning applications are available in the Fedora repositories.
SELinux prevents Empathy from connecting
The SELinux security framework erroneously prevents Empathy from connecting to Yahoo! (and probably other) instant messaging accounts in Fedora 14 Beta.
An updated selinux-policy package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, run this command:
su -c 'yum --enablerepo=updates-testing update selinux-policy selinux-policy-targeted'
Crash of gmixer application reported each time LXDE starts
At each start of the LXDE desktop environment, a crash in the
application occurs (and is reported by the automated crash report tool ABRT). Consequently, no mixer (volume control) applet appears in the LXDE panel. This is a known issue in gmixer; it is not necessary to submit the ABRT report. There is no known workaround for this issue, but it has no consequences beyond the lack of a volume control applet. This issue will be resolved in the final Fedora 14 release by fixing the gmixer bug or switching to a different volume control applet.