From Fedora Project Wiki

(Add bug#678095)
(Add bug#679171)
Line 102: Line 102:
  
 
To work around this issue, you can specify the desired installation display mode in the kickstart file using the commands [[Anaconda/Kickstart#graphical|graphical]], [[Anaconda/Kickstart#text|text]] or [[Anaconda/Kickstart#vnc|vnc]].  The issue has been resolved and will be fixed with a new {{package|anaconda}} update.
 
To work around this issue, you can specify the desired installation display mode in the kickstart file using the commands [[Anaconda/Kickstart#graphical|graphical]], [[Anaconda/Kickstart#text|text]] or [[Anaconda/Kickstart#vnc|vnc]].  The issue has been resolved and will be fixed with a new {{package|anaconda}} update.
 +
 +
 +
{{Anchor|enter_kills_firstboot}}
 +
=== Firstboot graphical configuration crashes on startup ===
 +
<small>[[#enter_kills_firstboot|link to this item]] - [[rhbug:679171|Bugzilla: #679171]]</small>
 +
 +
Due to an [http://git.fedorahosted.org/git/?p=firstboot.git;a=commit;h=a908f1f877d58fe87b1e648fd555e24763137003 systemd-related interaction] between firstboot and plymouth, the firstboot graphical configuration utility may crash when a user presses <code>Enter</code> to proceed to the next screen.  The problem does not occur when using the <code>Space</code> key, or clicking <code>Next</code> with the mouse cursor. 
 +
 +
An [https://admin.fedoraproject.org/updates/firstboot-1.117-2.fc15 updated firstboot-1.117-2.fc15 package is available] that resolves the reported problem.  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 firstboot'
 +
 +
 +
 +
An update to firstboot is available for do firstboot-1.117-2.fc15 has been pushed to the Fedora 15 stable repository.

Revision as of 18:13, 7 March 2011

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.

Note.png
Fedora 15 pre-release
Fedora 15 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 15 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 F15 Alpha Announcement and the Fedora 15 release notes for specific information about changes in Fedora 15: 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)


Installation Issues

Failure while partitioning BIOS RAID - AttributeError: 'NoneType' object has no attribute 'addChild'

link to this item - Bugzilla: #678877

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 Package-x-generic-16.pnganaconda 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 enabled networking

link to this item - Bugzilla: #677773

When installing Fedora 15 Alpha using the 32b or 64b 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. For a sample screenshot of the problem, see http://jlaska.fedorapeople.org/screenshots/bug677773.png. The issue has been resolved and will be fixed in a future update of Package-x-generic-16.pnganaconda.

Kickstart installation prompts for update disk source

link to this item - Bugzilla: #677131

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

link to this item - Bugzilla: #678095

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 Package-x-generic-16.pnganaconda update.


Firstboot graphical configuration crashes on startup

link to this item - Bugzilla: #679171

Due to an systemd-related interaction between firstboot and plymouth, the firstboot graphical configuration utility may crash when a user presses Enter to proceed to the next screen. The problem does not occur when using the Space key, or clicking Next with the mouse cursor.

An updated firstboot-1.117-2.fc15 package is available that resolves the reported problem. 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 firstboot'


An update to firstboot is available for do firstboot-1.117-2.fc15 has been pushed to the Fedora 15 stable repository.