From Fedora Project Wiki

Revision as of 12:55, 20 October 2009 by Pfrields (talk | contribs) (Update for F12 Beta)

This page documents common bugs in Fedora 12 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 12 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 12 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 Summary, Announcement and Notes

Read the F12 Beta Announcement and the draft Fedora 12 release notes for specific information about changes in Fedora 12: 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 enountered, you can:

  • Add it yourself, if you have wiki access. Remember to try and follow the style and guidelines explained in the comments in the page source.
  • Add the CommonBugs keyword to the bug report, and contact the Fedora QA team with the Bugzilla report number explaining why you believe that particular report qualifies as a common issue. You can contact Fedora QA through any of the methods listed here.

Issues when upgrading from previous releases

As usual, the supported methods for upgrading from previous Fedora releases are to do an 'upgrade install' from the regular installation media, or to use preupgrade (see How_to_use_PreUpgrade). Upgrading by using yum directly is not supported, but may in practice work. For known issues when upgrading via yum, see the page on this upgrade method.

Installation issues

/boot must be a minimum of 500 MB

link to this item - Bugzilla: #510970

If you use a separate /boot partition, it is highly recommended that it be at least 500MB in size.

First boot wizard unusable (buttons invisible) on some multiple display configurations

link to this item - Bugzilla: #526836

The first boot wizard - which runs on the first boot of a newly-installed system to display license information, handle user creation and offer to submit hardware information to the Smolt database - does not display consistently on multiple display configurations in Fedora 12 Beta. On some configurations, the wizard may be usable but stretched across all connected monitors. On others, it may be restricted to one monitor only. In the worst case, the wizard will display in such a way that the buttons needed to progress through the steps (which should be shown at the bottom-right hand corner) are invisible, being rendered outside the boundaries of all connected monitors.

This issue has been fixed in a later version of the firstboot package, but the fix was too late to be included in the Beta. It will be included in the final release. If you encounter this bug in the Beta, there are two main possible workarounds. You can either use the tab and enter keys to activate the buttons without seeing them, or reboot the system with only one monitor connected to work through the first boot wizard, then reboot again with all monitors connected once you have made it through the wizard.

In rare cases, you may encounter this bug on a system with only one display, when it intersects with an X.org driver bug which causes your system to believe extra displays are connected when in fact they aren't. In this case, you can use the tab/enter workaround described above, or boot to runlevel 3 by adding the number 3 as a kernel parameter. This will cause a text configuration wizard to be displayed instead of the graphical firstboot wizard. If you have not yet created a user account, you should do so from this wizard. Then you can reboot as normal. If you find yourself in this situation, please file a bug on the phantom extra display problem, following these instructions.

First boot after installation fails on Apple Mac PowerPC systems

link to this item - Bugzilla: #529035

After a standard installation on an Apple Mac PowerPC system, booting the system fails with the message Unknown or corrupt filesystem. This is due to the installer (Anaconda) failing to ensure the hfsutils package is installed on such systems.

To workaround this issue, use the manual package selection option during installation and ensure that the hfsutils package is selected for installation. This issue should be resolved in the final release of Fedora 12.

Hardware-related issues

Software issues

ALSA sequencer unavailable by default

link to this item - Bugzilla: #505421

Due to a misconfiguration, in Fedora 12 Beta, the snd-seq module - which provides the ALSA sequencer interface - is not loaded by default. This affects applications which use the sequencer, such as qjackctl - "Could not open ALSA sequencer as a client", "ALSA MIDI patchbay will not be available" - and tuxguitar.

To work around this problem, create a file with the following contents:

install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-seq

and save it as /etc/modprobe.d/dist-alsa.conf. This issue should be resolved in the final release of Fedora 12.

Unable to login to GDM using network authentication

link to this item - Bugzilla: #527920

Fedora 12 Beta systems configured for a network authentication system (e.g. kerberos or lpap) may be unable to login using the GNOME Display Manager (GDM). Systems exhibiting this problem will not permit login for remote user accounts and may not offer a dialog to manually enter the remote username. A suggested workaround involves adding a temporary entry in /etc/passwd for affected users. One method to accomplish this is demonstrated below.

# getent passwd <username> >> /etc/passwd

Adobe Reader fails to run

link to this item

Third-party vendor issue
The root cause of this problem is not Fedora, but rather software provided by Adobe. If you are interested in a fix for this issue, you must contact that vendor through their web site.

We encourage Fedora users to use a free alternative to Adobe reader, such as Evince, whenever possible.

Current releases of Adobe Reader do not run by default on Fedora 12. To work around this problem, launch Adobe Reader with the following command:

GDK_NATIVE_WINDOWS=1 acroread