(add display blank issue (text copied from f11 page, also affects f11) (501601)) |
m (Add bug#510673) |
||
| Line 54: | Line 54: | ||
== Hardware-related issues == | == Hardware-related issues == | ||
=== ''nomodeset'' kernel option ignored === | |||
<small>[[Common F12 bugs#alpha-nomodeset-ignore|link to this item]] - [[rhbug:510673|Bugzilla: #510673]]</small> | |||
Due to a known kernel bug, the ''nomodeset'' argument may not correctly disable kernel modesetting. An additional driver-specific kernel option may be required to further disable modesetting. Depending on your display adapter, you may need to supply one of the following options to disable kernel modesetting: | |||
* If you have an ATI Radeon adapter: <code>radeon.modeset=0</code> | |||
* If you have an NVidia adapter: <code>nouveau.modeset=0</code> | |||
* If you have an Intel i915 adapter: <code>i915.modeset=0</code> | |||
To determine your display adapter, please refer to [[How_to_debug_Xorg_problems#What_driver_am_I_using.3F]]. | |||
== Software issues == | == Software issues == | ||
Revision as of 12:36, 21 August 2009
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 pre-release that fixes them is available (for instance, an issue that affects the Alpha but is fixed in the Beta will be removed when the Beta is released).
Release Summary, Announcement and Notes
Read the Fedora 12 Alpha 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.
RAID array creation fails, hanging the system
Due to a known kernel bug, RAID array creation is very likely to fail and cause the system to hang in Fedora 12 Alpha. This bug is fixed in 
kernel
nomodeset kernel option ignored
link to this item - Bugzilla: #510673
Due to a known kernel bug, the nomodeset argument may not correctly disable kernel modesetting. An additional driver-specific kernel option may be required to further disable modesetting. Depending on your display adapter, you may need to supply one of the following options to disable kernel modesetting:
- If you have an ATI Radeon adapter:
radeon.modeset=0 - If you have an NVidia adapter:
nouveau.modeset=0 - If you have an Intel i915 adapter:
i915.modeset=0
To determine your display adapter, please refer to How_to_debug_Xorg_problems#What_driver_am_I_using.3F.
Software issues
SELinux information tool (sealert) fails to run
link to this item - Bugzilla: #517261
Due to a missing dependency, the SELinux information tool that runs when you click on the link that offers more information when you are notified of an SELinux alert, or if you simply click on the SELinux icon in the system tray, or if you run sealert manually from the console, does not work out of the box on the Fedora 12 Alpha live CDs. If you run it from a console you will see that it fails to find a module named slip.dbus.service. To fix this problem, install the
Display goes blank briefly, apparently at random
link to this item - Bugzilla: #501601
Several users have reported that their display will sometimes suddenly go blank for a brief period - a second or two - before coming back. This is caused by problems in how X handles idle time counting.
An updated xorg-x11-server package is available from Koji (and will be available in Rawhide after the Alpha freeze ends). Users experiencing this problem are encouraged to test this update and report to Bugzilla whether it solves the problem. Please note that initial testing has indicated this test update fixes the problem, but causes other side effects (such as screensaver never activating at all, or display being blanked while playing a video in Totem).