This page documents common bugs in Fedora 15 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.
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)
Due to changes between GNOME 2 and GNOME 3, there is no obvious link to the live installer in the GNOME live desktop environment in Fedora 15 Alpha. The installer can in fact be run, it is only the desktop link which is not present. You can find the installer by going to the Overview screen and searching for 'install', or simply running the command
liveinst. The desktop team is currently considering the best way to expose the installer in the GNOME 3 environment. The discussion can be found in the bug report.
Alpha installer includes Fedora 14 artwork
The Alpha installer uses older Fedora 14 themed artwork. As a result, the graphical installer will show a Fedora 14 logo during installation. A screenshot demonstrating the problem is shown below.
Failure while partitioning BIOS RAID - AttributeError: 'NoneType' object has no attribute 'addChild'
When installing Fedora 15 Alpha to a system with BIOS RAID enabled, you may encounter the following failure during disk partitioning.
AttributeError: 'NoneType' object has no attribute 'addChild'
The failure is a known issue and will be resolved in a future
update. For Fedora 15 Alpha users, an installation updates image is a available to work around this problem. For guidance on using an updates image, refer to Anaconda/Updates.
DVD installation attempts to enable networking
When installing Fedora 15 Alpha using the 32-bit or 64-bit DVD ISO, the installer will prompt the user to enable networking. When installing from DVD ISO media, network is not intended to be enabled by default. If desired, the user can safely cancel any prompts to ensure that networking is disabled during the DVD installation. Here is a screenshot of the issue. The issue has been resolved and will be fixed in a future update of
Kickstart installation prompts for update disk source
When performing an unattended kickstart installation of Fedora 15 Alpha, the installer incorrectly prompts the user to select a drive for an updates image.
┌────────┤ Update Disk Source ├─────────┐ │ │ │ You have multiple devices which could │ │ serve as sources for an update disk. │ │ Which would you like to use? │ │ │ │ sda │ │ sdb │ │ │ │ ┌────┐ ┌────────┐ │ │ │ OK │ │ Cancel │ │ │ └────┘ └────────┘ │ │ │ │ │ └───────────────────────────────────────┘
The user can safely select
Cancel to ignore this request. This issue has been resolved and will be fixed in a future
update. In the meantime, an updates image is available to work around this problem. For guidance on using an updates image, refer to Anaconda/Updates.
Kickstart installation defaults to command-line interface
Due to a defect in the installer, when performing an unattended kickstart installation using the Fedora 15 Alpha installer, unless a display mode is specified, the installer will use the non-interactive command-line display method. Previously, if no display mode was specified, the installer would default to graphical or prompt the user if a graphical installation was not possible.
To work around this issue, you can specify the desired installation display mode in the kickstart file using the commands graphical, text or vnc. The issue has been resolved and will be fixed with a new
Cannot get translation file
After selecting some languages (such as German) during installation, the Fedora 15 Alpha installer may emit the following error indicating it was unable to locate the appropriate translation file.
┌─────────────┤ Error ├──────────────┐ │ │ │ Cannot get translation file de.tr. │ │ │ │ ┌────┐ │ │ │ OK │ │ │ └────┘ │ │ │ │ │ └────────────────────────────────────┘
The error appears to only affect the display language used during the text-based initial
loader program. The correct language will be displayed during the graphical installation. A fix has been identified, and an updated
will resolve the reported issue.
Live installer fails to run: xhost: unable to open display ":0"
Under some circumstances, the live installer may fail to run in Fedora 15 Alpha. If run from a console with the
liveinst command, the error message xhost: unable to open display ":0" will be displayed. This failure occurs if the system hostname is set via DHCP after the system successfully boots to a desktop environment. For more details, please see the bug report. To work around this problem, run
su -c 'xhost +' from a console and then re-run the live installer.
Cobbler kickstart installs fail to enable networking
The Fedora 15 Alpha installer processes kickstart
%include statements before running any scripts defined in
%pre is run. The provisioning tool
, relies generates kickstart statements from inside
%pre and later references generated content using
%include. As a result, cobbler installations using the
pre_install_network_config snippet will fail to properly enable networking. To work around this limitation, manual intervention may be required to successfully perform a cobbler-based kickstart installation using the
pre_install_network_config snippet. Alternatively, users may workaround the problem by using alternative network configuration means (e.g. dhcp).
An fix is available and a future update of
will resolve the reported issue.
Unable to login using serial console
Due to a bug in the
package, users may be unable to login to their system when using a serial console to login. Affected users can work around the problem by adding the boot option
plymouth.debug. An updated plymouth-0.8.4-0.20110304.1.fc15 package is available that resolves the reported issue. To apply the update, enable the Fedora 15-Alpha package repository during installation, or apply the update manually after installation using the following command:
su -c 'yum update plymouth'
Unable to unlock encrypted filesystem using non-ascii letters
When unlocking an encrypted disk partition on boot, passphrases containing special characters not present on a standard US English keymap cause the boot process to hang. Characters known to cause problems include, but are not limited to,
An updated dracut-008-7.fc15 package is available that resolves the reported issue. To apply the update, enable the Fedora 15-Alpha package repository during installation, or apply the update manually after installation using the following command:
su -c 'yum update dracut'
su -c 'dracut -f'