View source for Common F18 bugs

{{autolang|base=yes}}

This page documents common bugs in Fedora 18 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.

== Release Notes ==
Read the [[F18_release_announcement]] and the [http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/index.html Fedora 18 release notes] for specific information about changes in Fedora 18 and other general information.

== My bug is not listed ==
Not every bug is listed in this page, but [http://bugzilla.redhat.com 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 [http://bugzilla.redhat.com 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:
* [http://bit.ly/fedora-commonbugs-proposed CommonBugs?] (bugs with CommonBugs keyword, but ''do not yet'' have a link to this page)
* [http://bit.ly/fedora-commonbugs-accepted CommonBugs+](bugs with CommonBugs keyword ''and'' contain a link to this page)

<!-- 
When adding issues to this page, ensure to add the CommonBugs keyword to the bug report, and add the anchor link to the entry on this page in the Whiteboard field on the bug report.
-->

<!-- *** FOLLOW THIS FORMAT FOR ALL ENTRIES PLEASE. ***
{{Anchor|Issue-Foo}}
=== Issue Foo (example) ===
<small>[[{{subst:PAGENAME}}#Issue-Foo|link to this item]] - [[rhbug:XXXXXX|Bugzilla: #XXXXXXX]]</small>

Words words words. Blah blah blah. Include a good explanation of the problem, and any available workarounds.

If a build which may fix the problem is made available via updates-testing, add this boilerplate paragraph (appropriately customized for the issue):

An updated [http://admin.fedoraproject.org/updates/(name)-(EVR) (name)] package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and [http://admin.fedoraproject.org/updates/(name)-EVR report to Bodhi] whether it solves the problem. To test the update, run this command:
<pre>su -c 'yum --enablerepo=updates-testing update (name)'</pre>

If a scratch build which may fix the problem is made available via Koji (rather than in updates-testing), add this boilerplate paragraph (appropriately customized for the issue):

A test build that should resolve this problem is available from Koji: [http://koji.fedoraproject.org/koji/taskinfo?taskID=XXXXXXX packagename-EVR]. If you are affected by this issue, please test this update and report your results to the [[rhbug:XXXXXX|bug report]].

If the page is in pre-release state and a documented problem has been fixed in Rawhide but no newer pre-release has yet come out, add this boilerplate paragraph (appropriately customized for the issue):

This issue was fixed in the updated ''(name)-(EVR)'' package. To solve the issue, update your (pre-release name, e.g. "Fedora 13 Beta") installation as usual. You should no longer encounter this issue after updating to that version or later of {{package|(name)}}.

When the page is in pre-release state and a new pre-release becomes available, simply remove any issues that are now fixed from the page entirely.
-->

== Installation issues ==

{{Anchor|solaris-zfs-freespace}}
=== Partitions on Solaris 10-formatted disks may appear as free space to installer ===
<small>[[#solaris-zfs-freespace|link to this item]] - [[rhbug:869482|Bugzilla: #869482]]</small>

It has been reported that the Fedora 18 installer may not correctly recognize disks formatted by the Solaris 10 installer: it may see partitions on these disks as free (unformatted) space. This may be due to the Solaris 10 installer using an unusual GPT format. If you have disks formatted by the Solaris installer that contain data of value to you, exercise caution in installing Fedora 18. See the bug report for more details.

{{Anchor|installer-docs-old}}
=== Installer boot options documentation is outdated ===
<small>[[#installer-docs-old|link to this item]] - [[rhbug:864468|Bugzilla: #864468]]</small>

There are currently two pages documenting the boot options of the installer of Fedora 18 Beta: [[Anaconda Boot Options]] and http://wwoods.fedorapeople.org/doc/boot-options.html. Both of them are at least partly outdated. We are hoping to update these pages soon, but in the mean time you can try to look at both and take a guess which of the boot options are current and which are obsolete, if you need to use them. Of course, if you are able to follow the source code, you can check out [http://git.fedorahosted.org/cgit/anaconda.git/log/?h=f18-beta2-branch the anaconda source] and derive the currently-valid options from that.

Some old anaconda options - notably, several of the network configuration options - have been replaced by Dracut options, which are documented at [[Dracut/Options]].

{{Anchor|keyboard-layout-testing}}
=== Keyboard layout testing and selection during installation does not work as expected ===
<small>[[#keyboard-layout-testing|link to this item]] - [[rhbug:854557|Bugzilla: #854557]]</small>

On the Keyboard screen during Fedora 18 installation there is a text entry box labelled 'Test the selected layout below:'. This label is confusing. The box does not let you test the layout currently highlighted in the list on the left hand side of the screen, but the layout that is active. There is no indicator for the active layout, so it is not easy to know which layout is active. The layout that was in the list when you first entered the screen will stay active until you do one of two things: remove it, or configure a layout switch key combination and use it. So if the English (U.S.) layout was in the list when you first entered the screen, if you add the French (French) layout, it will not be active. If you highlight it in the list, it will not be active. If you move it to the top of the list, it will still not be active. But if you remove the English (U.S.) layout, French (French) will become the active layout. Alternatively, if you add French (French), then click the 'Options' button, pick one or more keyboard layout switch combination(s), click 'OK', and then press a layout switch combination you just configured, French (French) will become active: press it again, and English (U.S.) will be active again. This should be reflected in the test box.

As there is no indication of the current active layout throughout installation, if you are configuring multiple layouts, we recommend you ensure the layout you wish to use for the rest of the install process is active using the test box before leaving the Keyboard screen, and then do not switch layouts until installation is complete.

{{Anchor|install-source-nothing}}
=== Installation source shows 'Nothing selected' for network installation ===
<small>[[#install-source-nothing|link to this item]] - [[rhbug:873468|Bugzilla: #873468]]</small>

It is possible that the Fedora 18 installer may fail to correctly set the default remote package source on occasion when booting the network installation image. Instead of showing 'Closest mirror' and 'GNOME Desktop', the 'Installation Source' and 'Software Selection' entries on the installer hub/home screen will show 'Nothing selected'. This will prevent installation from starting until it is rectified. Several possible causes of this bug were eliminated during development of Fedora 18, but it appears the bug may still occur in some rare cases.

If you are affected by this bug, to work around it, you can either just reboot (it will often succeed on a second try), or enter the 'Installation Source' spoke, change the remote source URL to any specific address at all (it does not have to be valid), return to the hub screen, return to the 'Installation Source' spoke, change the source back to 'Closest mirror', and return to the hub screen once again.

{{Anchor|invalid-install-source}}
=== Invalid installation source breaks many configuration screens ===
<small>[[#invalid-install-source|link to this item]] - [[rhbug:875003|Bugzilla: #875003]]</small>

If you happen to provide an invalid installation source (in the ''Installation Source'' screen) in the Fedora 18 installer, some installer screens might become corrupted even when you provide a correct installation repository (like ''Closest mirror'') afterwards. Most often the package selection screen gets corrupted, but other screens like partitioning or keyboard selection screen might be affected too. The only safe workaround is to reboot and start the installer again.

{{Anchor|luc-no-uefi}}
=== UEFI boot doesn't work with liveusb-creator ===
<small>[[#luc-no-uefi|link to this item]] - [[rhbug:810112|Bugzilla: #810112]]</small>

[https://fedorahosted.org/liveusb-creator/ liveusb-creator] is one of the recommended tools for converting optical media ISO images into a bootable USB images. However, this tool still hasn't implemented support for UEFI boot. If you want to install Fedora in native UEFI mode from a USB media, use either {{command|dd}} or {{command|livecd-iso-to-disk}} to create it. The full instructions are at [[How to create and use Live USB]].

== Hardware issues ==


== Software issues ==

{{Anchor|live-autologin}}
=== Automatic login does not work on Desktop Live image ===
<small>[[#live-autologin|link to this item]] - [[rhbug:854722|Bugzilla: #854722]]</small>

When you boot the Fedora 18 Desktop Live image, you will not be automatically logged in to the desktop, as was the case in previous releases and as is intended. The login screen will appear with 'Live System User' as the only available user account: clicking this user will log you into the live system, which will then work as usual. There are no further consequences of this bug beyond the minor inconvenience.

{{Anchor|encrypt-timeout-rescue}}
=== System will drop to rescue mode if encryption password not entered after some time ===
<small>[[#encrypt-timeout-rescue|link to this item]] - [[rhbug:868421|Bugzilla: #868421]]</small>

If you install Fedora 18 with all or some system partitions encrypted, then if you do not enter the encryption password for an encryption partition when prompted at boot, after several minutes the system will drop to rescue mode. It ought to wait indefinitely for password entry. If you encounter this problem, you can simply reboot from the rescue mode and enter the password in time on the next boot attempt. Your data will not be endangered.