Common F15 bugs

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Unable to connect to Cisco AnyConnect VPN)
m (Reverted edits by Alberto783 (talk) to last revision by Adamwill)
 
(43 intermediate revisions by 13 users not shown)
Line 2: Line 2:
  
 
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.
 
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.
 
{{admon/note|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 ==
 
== Release Notes ==
  
Read the [[F15_Beta_announcement|F15 Beta Announcement]] and the [http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Notes/ Fedora 15 release notes] for specific information about changes in Fedora 15: known issues, and other general information.
+
Read the [[Fedora_15_announcement |Fedora 15 announcement]] and the [http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Notes/ Fedora 15 release notes] for specific information about changes in Fedora 15: known issues, and other general information.
  
 
== My bug is not listed ==
 
== My bug is not listed ==
Line 23: Line 21:
  
 
For reference, you can query Bugzilla for bugs tagged CommonBugs:
 
For reference, you can query Bugzilla for bugs tagged CommonBugs:
* [https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=CommonBugs%3F&sharer_id=141215 CommonBugs?] (bugs with CommonBugs keyword, but ''do not yet'' have a link to this page)
+
* [http://bit.ly/fedora-commonbugs-proposed CommonBugs?] (bugs with CommonBugs keyword, but ''do not yet'' have a link to this page)
* [https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=CommonBugs%2B&sharer_id=141215 CommonBugs+ ](bugs with CommonBugs keyword ''and'' contain a link to this page)
+
* [http://bit.ly/fedora-commonbugs-accepted CommonBugs+] (bugs with CommonBugs keyword ''and'' contain a link to this page)
  
 
<!--  
 
<!--  
Line 53: Line 51:
 
-->
 
-->
  
== Installation Issues ==
+
== Resolved issues ==
 +
 
 +
{{Anchor|intel_ips_load}}
 +
=== System fan runs constantly on laptops with Intel integrated graphics ===
 +
<small>[[#intel_ips_load|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=703511 Bugzilla: #703511]</small>
 +
 
 +
On some laptops with Intel integrated graphics, a bug in the ''intel_ips'' kernel module may cause the system load to appear permanently high, resulting in the system fan running constantly at high speed. The system load reading is in error, so the system is not in any danger of temperature-related damage, but the constant fan noise may be annoying.
 +
 
 +
This issue was fixed in the updated ''kernel-2.6.38.6-27.fc15'' package. To solve the issue, update your Fedora 15 installation as usual and reboot. You should no longer encounter this issue after updating to that version or later of {{package|kernel}}.
 +
 
 +
== Installation issues ==
 +
 
 +
{{Anchor|ftp-repository-fail}}
 +
=== Unable to retrieve FTP repodata ===
 +
<small>[[#ftp-repository-fail|link to this item]] - [[rhbug:679709|Bugzilla: #679709]]</small>
 +
 
 +
Due to a bug in the installer, when adding FTP-based package repositories during installation, the installer may report a failure while attempting to access FTP-based repository.  No fix is available at this time.  To workaround the problem, users are advised to first add an HTTP-based package repository URL (such as http://download.fedoraproject.org/pub/fedora/linux/releases/15/Fedora/x86_64/os).  Once added, you may edit the newly created package repository, and change the repository URL to the desired FTP-based repository URL.
 +
 
 +
For additional guidance on installation package repositories, consult the [http://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Guide/s1-pkgselection-x86.html#sn-additional-repos installation guide].
 +
 
 +
{{Anchor|attributeerror-nonetype}}
 +
=== AttributeError: 'NoneType' object has no attribute 'rfind ===
 +
<small>[[#attributeerror-nonetype|link to this item]] - [[rhbug:706542|Bugzilla: #706542]]</small>
 +
 
 +
There is a known failure that may occur while  partitioning your system during installation.  A manual workaround may be required if you encounter a failure similar to <pre>AttributeError: 'NoneType' object has no attribute 'rfind'</pre>
 +
 
 +
The problem will be fixed in future releases of Fedora, and an {{filename|[http://jlaska.fedorapeople.org/updates/706542.img updates.img]}} is available to resolve this issue for Fedora 15.  For additional guidance on using an {{filename|updates.img}}, consult [[Anaconda/Updates]].
 +
 
 +
{{Anchor|missing-bootif-fail}}
 +
 
 +
=== Installation failure when using ''ksdevice=bootif'' without ''bootif='' ===
 +
<small>[[#missing-bootif-fail|link to this item]] - [[rhbug:704188|Bugzilla: #704188]]</small>
 +
 
 +
When installing Fedora 15 while using the boot argument <code>ksdevice=bootif</code>, the installer will fail abnormally if no <code>BOOTIF=</code> value is provided by the PXE server.  Future versions of Fedora will not exhibit this failure.  In the meantime, ensure your PXE server is making proper use of the <code>IPAPPEND</code> configuration variable.  This variable controls what networking arguments are passed to the kernel, and is typically responsible for providing a <code>BOOTIF=</code> value.
 +
 
 +
For additional guidance, consult the [http://syslinux.zytor.com/wiki/index.php/SYSLINUX#IPAPPEND_flag_val_.5BPXELINUX_only.5D syslinux <code>IPAPPEND</code> documentation].
 +
 
 +
{{Anchor|installer-requires-more-memory}}
 +
=== Installation requires more memory'' ===
 +
<small>[[#installer-requires-more-memory link to this item]] - [[rhbug:682555|Bugzilla: #682555]]</small>
 +
 
 +
The installer in Fedora 15 has undergone some changes in Fedora 15, a side effect of which it may require more than 512 MB and upto 768 MB may be required to finish the installation. 1 GB is recommended. A number of changes are being done in the installer to reduce this requirement but the amount of changes are too intrusive and hence won't be done in the Fedora 15 branch. Installer team is [http://www.redhat.com/archives/anaconda-devel-list/2011-March/msg00263.html working] on lowering memory requirements again for Fedora 16.
 +
 
 +
{{Anchor|pxe_fail}}
 +
=== repomd.xml file reported missing or broken ===
 +
<small>[[#pxe_fail|link to this item]] - [[rhbug:703025|Bugzilla: #703025]]</small>
 +
 
 +
When adding Fedora 15 to a PXE server and using a PXE boot menu to upgrade, the installer will complain about a bad or missing repomd.xml file. This happens when the PXE upgraded machine has no internet connectivity (for example because it is crosscabled to a PXE server). You can hit the "edit" button, and then fix the url to your local http server (usually running on the PXE server). Then you will hit the same issue again, as the installer also searches for the "updates testing" repo. Just point it with url to the same "base" f15 repo on your PXE/http server. Don't forget to unselect the "is mirror URL" tickbox.
 +
 
 +
{{Anchor|live_reboot}}
 +
=== Unclear how to reboot after installing from desktop live image ===
 +
<small>[[#live_reboot|link to this item]] - [[rhbug:705189|Bugzilla: #705189]]</small>
 +
 
 +
If you install Fedora 15 from the 'desktop' - GNOME 3 - live image, when the final screen of the installer prompts you to reboot your system, you may find yourself asking 'yes, but how?' The GNOME 3 interface does not offer shutdown or reboot options at first glance. To shut down or reboot, you can either log out from the ''User'' menu (top right hand corner of the screen) and then shut down or reboot from the login screen, or open the ''User'' menu and then hold down the 'alt' key: the ''Suspend'' entry will turn into a ''Power off...'' entry as long as the 'alt' key is held down, which when clicked will give you the option to shut down or reboot.
 +
 
 +
{{Anchor|EFI_unsupported}}
 +
=== Systems using EFI BIOS are unsupported ===
 +
<small>[[#EFI_unsupported|link to this item]] - [[rhbug:717605|Bugzilla: #717605]]</small>
 +
 
 +
Many systems using EFI (Extended Firmware Interface) do not work with Fedora 15 due to bugs in their EFI implementations. Either disable EFI in the system BIOS settings or boot the system with the "noefi" option. Note that some systems may simply hang at boot time without any error message.
 +
 
 +
== Issues when upgrading from previous releases ==
 +
 
 +
{{anchor|upgrade-disabled-services}}
 +
=== Service not enabled after upgrading from Fedora 14 ===
 +
<small>[[#upgrade-disabled-services|link to this item]] -
 +
[[rhbug:703234|Bugzilla: #703234]],
 +
[[rhbug:703221|#703221]],
 +
[[rhbug:703227|#703227]],
 +
[[rhbug:703230|#703230]],
 +
[[rhbug:703236|#703236]],
 +
[[rhbug:703235|#703235]],
 +
[[rhbug:703233|#703233]],
 +
[[rhbug:703232|#703232]]
 +
</small>
 +
 
 +
In Fedora 15, upstart has been replaced by a service called [[Features/systemd|systemd]].  Due to improper rpm package upgrade scripts, some system services previously enabled in Fedora 14, may not be enabled after upgrading to Fedora 15.  To determine if a service is impacted, run the {{command|systemctl status}} command as shown below.
 +
<pre>
 +
# systemctl is-enabled foo.service && echo "Enabled on boot" || echo "Disabled on boot"
 +
</pre>
 +
 
 +
To enable a service on boot, run the following {{command|systemctl}} command (where <code>foo</code> is replaced with the name of the service):
 +
<pre>
 +
# systemctl enable foo.service
 +
</pre>
 +
 
 +
Corrected packages may be available in the Fedora 15 ''updates'' repository.  Depending on how you upgrade your Fedora 14 system (DVD-upgrade, or network upgrade), if the ''updates'' repository is included, packages with corrected upgrade scripts will be included and properly transfer your Fedora 14 service configuration to Fedora 15.
 +
 
 +
{{anchor|upgrade-runlevel}}
 +
=== Graphical login does not start after upgrade ===
 +
<small>[[#upgrade-runlevel|link to this item]] - [[rhbug:698654|Bugzilla: #698654]]</small>
 +
 
 +
Depending on how Fedora 14 was initially installed, your system may not select the appropriate systemd boot target after upgrading to Fedora 15.  The problem is caused by the <code>%postinstall</code> rpm script from the Fedora 14 package {{package|systemd-units}}.  Since {{package|systemd}} isn't the default in Fedora 14, the problem will not manifest until you upgrade to Fedora 15. 
 +
 
 +
If you change the Fedora 14 default runlevel at any time by modifying the file {{filename|/etc/inittab}}, those changes will not affect the configured systemd default target.  After upgrade, you may need to manually adjust the configured systemd default target links using the following procedure. 
 +
 
 +
To configure systemd to start a graphical login menu on boot (similar to runlevel 5 in Fedora 14):
 +
<pre>
 +
# ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
 +
# ln -sf graphical.target /lib/systemd/system/default.target
 +
</pre>
 +
 
 +
To configure systemd to start a text login prompt on boot (similar to runlevel 3 in Fedora 14):
 +
<pre>
 +
# ln -sf /lib/systemd/system/runlevel3.target /etc/systemd/system/default.target
 +
# ln -sf runlevel3.target /lib/systemd/system/default.target
 +
</pre>
 +
 
 +
{{anchor|usb3-ports-not-working-after-f14}}
 +
=== USB 3.0 ports not working anymore after upgrade from F14 ===
 +
<small>[[#usb3-ports-not-working-after-f14|link to this item]]</small>
 +
 
 +
If The USB 3.0 ports have been enabled in F14 using the guide in [[Common_F14_bugs#USB_3.0_ports_not_working|Common F14 bugs]], USB 3.0 may not be working anymore after the upgrade to F15.
 +
 
 +
To enable the ports again, revert the changes made for F14: Remove the kernel parameter ''xhci.enable=1'' (or ''xhci_hcd.enable=1'') and remove the file {{filename|/etc/pm/config.d/xhci}}, if existing.
 +
 
 +
== Hardware issues ==
 +
 
 +
{{Anchor|ath9k_performance}}
 +
=== Poor transfer speeds with Atheros-based wireless chipsets ===
 +
<small>[[#ath9k_performance|link to this item]] - [[rhbug:702722|Bugzilla: #702722]]</small>
 +
 
 +
Several users have reported very slow transfers with Atheros-based wireless network adapters using the ''ath9k'' driver. It seems to be possible in many cases to work around this issue by creating a file named {{filename|/etc/modprobe.d/ath9k.conf}} with the contents:
 +
<pre>
 +
options ath9k nohwcrypt=1
 +
</pre>
 +
This disables the use of hardware encryption; it will result in slightly higher CPU usage as the system CPU will be used to handle encryption of the wireless connection.
 +
 
 +
== Software issues ==
 +
 
 +
{{Anchor|firefox-disappearing-addons}}
 +
=== Add-ons (extensions) disappear after update to Firefox 7.0 ===
 +
<small>[[#firefox-disappearing-addons|link to this item]] - [https://bugzilla.mozilla.org/show_bug.cgi?id=680802 Mozilla: #680802]</small>
 +
 
 +
Firefox 7.0 contains a bug which means that any add-on (extension) that has a pending update (automatically downloaded, but not yet installed) when Firefox is updated to 7.0 will apparently disappear from Firefox.
 +
 
 +
This issue will be resolved in Firefox 7.0.1, which should arrive as an update shortly. In the meantime, you can try installing [https://people.mozilla.com/%7Edtownsend/shared/bug680802/hotfix.xpi this extension] as a workaround: it should cause the 'missing' add-ons to return.
 +
 
 +
{{Anchor|live-overlay}}
 +
 
 +
=== Live USB overlay (persistent storage) not mounted on boot ===
 +
<small>[[#live-overlay|link to this item]] - [[rhbug:706122|Bugzilla: #706122]]</small>
 +
 
 +
Due to a defect in {{package|dracut}}, overlay (persistent storage) is not properly mounted on boot.  An updated [https://admin.fedoraproject.org/updates/dracut-009-11.fc15 dracut-009-11.fc15] is available to resolve the issue, however this update will not correct existing Fedora 15 live images. 
 +
 
 +
To temporarily workaround this problem with Fedora 15 live media...
 +
# When booting live media, press <code>[Tab]</code> at the bootloader screen
 +
# Add the following boot arguments <pre>rd.break=pre-trigger</pre>
 +
# When the boot process stops and presents a shell prompt, type the following commands <pre> mkdir /overlayfs ; exit </pre>
 +
# When the boot process stops again and presents a shell prompt, type the following command <pre>exit </pre>
 +
 
 +
 
 +
For a permanent fix, you may rebuild the Fedora 15 live media to include the updated {{package|dracut}} package following instructions at [[How_to_create_and_use_a_Live_CD]].
 +
 
 +
{{Anchor|networkmanager_shell}}
 +
 
 +
=== General buggy or missing functions in GNOME Shell network applet ===
 +
<small>[[#networkmanager_shell|link to this item]]</small>
 +
 
 +
GNOME Shell features an integrated NetworkManager configuration interface, provided by an applet in the top panel and a configuration interface in System Settings. However, as of Fedora 15 Beta, these tools have not yet achieved feature parity with the configuration interface from GNOME 2, provided by the old ''nm-applet''. Some features are still missing and there are known bugs with others. Major ones will be listed individually here, but as a general principle, if you encounter problems or missing features trying to configure your network using the GNOME 3 applet and System Settings interface, you can run the standalone {{command|nm-connection-editor}} tool, which makes all the operations not yet implemented in the GNOME 3 interface available. You can launch {{command|nm-connection-editor}} from a console, from the alt-f2 Run dialog, or from the overview (type ''nm-connection-editor'' or search for an entry named ''Network Connections'').
  
{{Anchor|turkish-partition}}
+
GNOME 3's fallback mode uses the old ''nm-applet'', and is not subject to this issue.
=== Installation in Turkish language crashes at custom partitioning screen ===
+
<small>[[#turkish-partition|link to this item]] - [[rhbug:694928|Bugzilla: #694928]]</small>
+
  
Due to a bug in Python, when installing Fedora 15 Beta in Turkish, if you access the custom partitioning screen by selecting either the 'Create a custom partition layout' radio button or the 'Review and modify partitions prior to installing' checkbox at the partition options screen, the installer will crash. You can work around this issue by installing in another language (if you must use the custom partitioning screen) or by installing in Turkish but not selecting either of the options that causes the custom partitioning screen to display.
+
{{Anchor|gnome_lcd_brightness}}
 +
=== Laptop screen dims when switching to battery power or idle mode but never brightens again ===
 +
<small>[[#gnome_lcd_brightness|link to this item]] - [https://bugzilla.gnome.org/show_bug.cgi?id=650405 GNOME Bugzilla: #650405]</small>
  
This issue will be resolved in the final Fedora 15 release.
+
Due to a bug in the screen brightness control logic in gnome-power-manager, laptop screens will dim as expected when switching from mains to battery power and dim further when the system is idle in battery mode, but will never brighten again when the system is no longer idle, or when you connect back to the mains. Eventually the screen will end up at its lowest possible brightness and be stuck there.
  
{{Anchor|mediacheck_32bit}}
+
The only workaround is to disable screen dimming via the control center, or to manually reset the brightness to 100% via the keyboard (if you have brightness keys) or the control center every so often.
=== Installer media check always fails in 32-bit Fedora 15 Beta ===
+
<small>[[#mediacheck_32bit|link to this item]] - [[rhbug:692135|Bugzilla: #692135]]</small>
+
  
Due to a bug in the image checking library, the media check function of the Fedora 15 Beta installer will always fail on 32-bit images, even if the medium is in fact correct. The 64-bit images are unaffected. To work around this issue, simply do not use the media check function of the installer; you can verify the integrity of the image outside of the installer.
+
An updated [http://admin.fedoraproject.org/updates/gnome-power-manager-3.0.0-3.fc15 gnome-power-manager] 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/gnome-power-manager-3.0.0-3.fc15 report to Bodhi] whether it solves the problem. To test the update, run this command: <pre>su -c 'yum --enablerepo=updates-testing update gnome-power-manager'</pre>
  
This issue will be resolved in the final Fedora 15 release.
+
{{Anchor|clutter_leaks}}
 +
===System memory in use rises constantly (memory leak) when using GNOME Shell ===
 +
<small>[[#clutter_leaks|link to this item]] - [[rhbug:672117|Bugzilla: #672117]]</small>
  
== Software Issues ==
+
Some users have noticed memory leaks in GNOME Shell; that is, when Shell is running, the system memory in use by the ''gnome-shell'' process rises constantly. The severity of the leak can vary from system to system, but it usually starts out using around 60-70MB of system memory, and rises to over 200MB after a day or two. To work around the problem, simply restart the Shell when its memory usage gets too high: run {{command|killall gnome-shell}}, or from the ''Run'' dialog - triggered by the key combination alt-f2 - simply type the single letter ''r'' and hit enter.
  
{{Anchor|hidden_wireless}}
+
{{Anchor|gnome3_iranian_login}}
=== Unable to connect to hidden wireless networks ===
+
=== Cannot log in to GNOME 3 with Iranian (fa_IR) locale selected ===
<small>[[#hidden_wireless|link to this item]] - [[rhbug:691139|Bugzilla: #691139]]</small>
+
<small>[[#gnome3_iranian_login|link to this item]] - [[rhbug:703060|Bugzilla: #703060]]</small>
  
The GNOME 3 NetworkManager configuration interface in Fedora 15 Beta (the applet by the user menu, and the control center Network entry) contain a bug which causes them to hang if you try to configure a hidden wireless network by typing in its SSID. To work around this bug, you can run the standalone configuration tool {{command|nm-connection-editor}}, either by running it from a console, from the alt-f2 dialog, or by finding it in the Overview (it has the name ''Network Connections''). This tool is able to configure hidden networks correctly. This tool is a useful fallback for any situation where the GNOME 3 configuration interface is problematic or incomplete.
+
A bug in GNOME Shell makes log in to that environment fail if the fa_IR (Iranian) locale is selected as the system locale. Various errors related to ''Argument 'text' (type utf8) may not be null'' will be present in the {{filename|~/.xsession-errors}} file.
  
This issue was fixed in the updated ''control-center-3.0.0.1-3.fc15'' package. To solve the issue, update your Fedora 15 Beta installation as usual. You should no longer encounter this issue after updating to that version or later of {{package|control-center}}.
+
You can work around the issue by using a different locale, or by removing these lines from the file {{filename|/usr/share/gnome-shell/js/ui/environment.js}}:
 +
<pre>
 +
    Date.prototype.toLocaleFormat = function(format) {
 +
        return Shell.util_format_date(format, this.getTime());
 +
    };
 +
</pre>
  
{{Anchor|nm_openconnect}}
+
{{Anchor|gdm_locale}}
=== Unable to connect to Cisco AnyConnect VPN ===
+
=== Cannot select language or keyboard layout at login screen ===
 +
<small>[[#gdm_locale|link to this item]] - [[rhbug:681750|Bugzilla: #681750]]</small>
  
<small>[[#nm_openconnect|link to this item]] - [[rhbug:696107|Bugzilla: #696107]]</small>
+
In previous Fedora releases, the login screen (when using the gdm login manager, as is the default from a network, DVD or ''desktop'' live image install) had menus for selecting the language and keyboard layout to be used in the session. In Fedora 15, these menus are removed from gdm. To set the system language and keyboard layout you will need to open the ''User'' menu (at the top right hand corner of the screen), click on ''System Settings'', and then click on ''Region and Language'' in the window that opens up.
  
The NetworkManager-openconnect package in Fedora 15 Beta has not been updated to work with NetworkManager 0.9, and connecting to a Cisco AnyConnect VPN is only possible using the command-line ''openconnect'' tool.
+
{{Anchor|fedora-release-15-3_update}}
 +
==="could not add package update for fedora-release-rawhide-15-3(noarch)updates: fedora-release-rawhide-15-3.noarch"===
 +
<small>[[#fedora-release-15-3_update|link to this item]] - [[rhbug:716752|Bugzilla: #716752]]</small>
  
This issue was fixed in the updated ''[https://admin.fedoraproject.org/updates/NetworkManager-openconnect-0.8.1-9.git20110419.fc15 NetworkManager-openconnect-0.8.1-9.git20110419.fc15]'' package. You should no longer encounter this issue after updating to that version of later of {{package|NetworkManager-openconnect}}.
+
A bug in PackageKit (which does not affect updating via yum on the command line) prevents easily updating to fedora-release-15-3. Other updates can still be applied using PackageKit if the update for fedora-release-15-3 is unchecked first. To update fedora-release-15-3 itself using PackageKit, first click on the + sign next to "fedora-release-15-3 (noarch)" to see both of the associated package updates (fedora-release-15-3 and fedora-release-rawhide-15-3), then uncheck fedora-release-rawhide-15-3, then click "Install Updates". It asks to confirm removing "Rawhide repo definitions". Click "Continue" and it will then work. (Note that the fedora-release-rawhide package is only needed in order to upgrade to Rawhide, and can still be installed manually for this purpose.)

Latest revision as of 14:32, 11 April 2012

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.

Contents

[edit] Release Notes

Read the Fedora 15 announcement and the Fedora 15 release notes for specific information about changes in Fedora 15: known issues, and other general information.

[edit] 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)


[edit] Resolved issues

[edit] System fan runs constantly on laptops with Intel integrated graphics

link to this item - Bugzilla: #703511

On some laptops with Intel integrated graphics, a bug in the intel_ips kernel module may cause the system load to appear permanently high, resulting in the system fan running constantly at high speed. The system load reading is in error, so the system is not in any danger of temperature-related damage, but the constant fan noise may be annoying.

This issue was fixed in the updated kernel-2.6.38.6-27.fc15 package. To solve the issue, update your Fedora 15 installation as usual and reboot. You should no longer encounter this issue after updating to that version or later of Package-x-generic-16.pngkernel.

[edit] Installation issues

[edit] Unable to retrieve FTP repodata

link to this item - Bugzilla: #679709

Due to a bug in the installer, when adding FTP-based package repositories during installation, the installer may report a failure while attempting to access FTP-based repository. No fix is available at this time. To workaround the problem, users are advised to first add an HTTP-based package repository URL (such as http://download.fedoraproject.org/pub/fedora/linux/releases/15/Fedora/x86_64/os). Once added, you may edit the newly created package repository, and change the repository URL to the desired FTP-based repository URL.

For additional guidance on installation package repositories, consult the installation guide.

[edit] AttributeError: 'NoneType' object has no attribute 'rfind

link to this item - Bugzilla: #706542

There is a known failure that may occur while partitioning your system during installation. A manual workaround may be required if you encounter a failure similar to
AttributeError: 'NoneType' object has no attribute 'rfind'

The problem will be fixed in future releases of Fedora, and an updates.img is available to resolve this issue for Fedora 15. For additional guidance on using an updates.img, consult Anaconda/Updates.

[edit] Installation failure when using ksdevice=bootif without bootif=

link to this item - Bugzilla: #704188

When installing Fedora 15 while using the boot argument ksdevice=bootif, the installer will fail abnormally if no BOOTIF= value is provided by the PXE server. Future versions of Fedora will not exhibit this failure. In the meantime, ensure your PXE server is making proper use of the IPAPPEND configuration variable. This variable controls what networking arguments are passed to the kernel, and is typically responsible for providing a BOOTIF= value.

For additional guidance, consult the syslinux IPAPPEND documentation.

[edit] Installation requires more memory

#installer-requires-more-memory link to this item - Bugzilla: #682555

The installer in Fedora 15 has undergone some changes in Fedora 15, a side effect of which it may require more than 512 MB and upto 768 MB may be required to finish the installation. 1 GB is recommended. A number of changes are being done in the installer to reduce this requirement but the amount of changes are too intrusive and hence won't be done in the Fedora 15 branch. Installer team is working on lowering memory requirements again for Fedora 16.

[edit] repomd.xml file reported missing or broken

link to this item - Bugzilla: #703025

When adding Fedora 15 to a PXE server and using a PXE boot menu to upgrade, the installer will complain about a bad or missing repomd.xml file. This happens when the PXE upgraded machine has no internet connectivity (for example because it is crosscabled to a PXE server). You can hit the "edit" button, and then fix the url to your local http server (usually running on the PXE server). Then you will hit the same issue again, as the installer also searches for the "updates testing" repo. Just point it with url to the same "base" f15 repo on your PXE/http server. Don't forget to unselect the "is mirror URL" tickbox.

[edit] Unclear how to reboot after installing from desktop live image

link to this item - Bugzilla: #705189

If you install Fedora 15 from the 'desktop' - GNOME 3 - live image, when the final screen of the installer prompts you to reboot your system, you may find yourself asking 'yes, but how?' The GNOME 3 interface does not offer shutdown or reboot options at first glance. To shut down or reboot, you can either log out from the User menu (top right hand corner of the screen) and then shut down or reboot from the login screen, or open the User menu and then hold down the 'alt' key: the Suspend entry will turn into a Power off... entry as long as the 'alt' key is held down, which when clicked will give you the option to shut down or reboot.

[edit] Systems using EFI BIOS are unsupported

link to this item - Bugzilla: #717605

Many systems using EFI (Extended Firmware Interface) do not work with Fedora 15 due to bugs in their EFI implementations. Either disable EFI in the system BIOS settings or boot the system with the "noefi" option. Note that some systems may simply hang at boot time without any error message.

[edit] Issues when upgrading from previous releases

[edit] Service not enabled after upgrading from Fedora 14

link to this item - Bugzilla: #703234, #703221, #703227, #703230, #703236, #703235, #703233, #703232

In Fedora 15, upstart has been replaced by a service called systemd. Due to improper rpm package upgrade scripts, some system services previously enabled in Fedora 14, may not be enabled after upgrading to Fedora 15. To determine if a service is impacted, run the systemctl status command as shown below.

# systemctl is-enabled foo.service && echo "Enabled on boot" || echo "Disabled on boot"

To enable a service on boot, run the following systemctl command (where foo is replaced with the name of the service):

# systemctl enable foo.service

Corrected packages may be available in the Fedora 15 updates repository. Depending on how you upgrade your Fedora 14 system (DVD-upgrade, or network upgrade), if the updates repository is included, packages with corrected upgrade scripts will be included and properly transfer your Fedora 14 service configuration to Fedora 15.

[edit] Graphical login does not start after upgrade

link to this item - Bugzilla: #698654

Depending on how Fedora 14 was initially installed, your system may not select the appropriate systemd boot target after upgrading to Fedora 15. The problem is caused by the %postinstall rpm script from the Fedora 14 package Package-x-generic-16.pngsystemd-units. Since Package-x-generic-16.pngsystemd isn't the default in Fedora 14, the problem will not manifest until you upgrade to Fedora 15.

If you change the Fedora 14 default runlevel at any time by modifying the file /etc/inittab, those changes will not affect the configured systemd default target. After upgrade, you may need to manually adjust the configured systemd default target links using the following procedure.

To configure systemd to start a graphical login menu on boot (similar to runlevel 5 in Fedora 14):

# ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
# ln -sf graphical.target /lib/systemd/system/default.target

To configure systemd to start a text login prompt on boot (similar to runlevel 3 in Fedora 14):

# ln -sf /lib/systemd/system/runlevel3.target /etc/systemd/system/default.target
# ln -sf runlevel3.target /lib/systemd/system/default.target

[edit] USB 3.0 ports not working anymore after upgrade from F14

link to this item

If The USB 3.0 ports have been enabled in F14 using the guide in Common F14 bugs, USB 3.0 may not be working anymore after the upgrade to F15.

To enable the ports again, revert the changes made for F14: Remove the kernel parameter xhci.enable=1 (or xhci_hcd.enable=1) and remove the file /etc/pm/config.d/xhci, if existing.

[edit] Hardware issues

[edit] Poor transfer speeds with Atheros-based wireless chipsets

link to this item - Bugzilla: #702722

Several users have reported very slow transfers with Atheros-based wireless network adapters using the ath9k driver. It seems to be possible in many cases to work around this issue by creating a file named /etc/modprobe.d/ath9k.conf with the contents:

options ath9k nohwcrypt=1

This disables the use of hardware encryption; it will result in slightly higher CPU usage as the system CPU will be used to handle encryption of the wireless connection.

[edit] Software issues

[edit] Add-ons (extensions) disappear after update to Firefox 7.0

link to this item - Mozilla: #680802

Firefox 7.0 contains a bug which means that any add-on (extension) that has a pending update (automatically downloaded, but not yet installed) when Firefox is updated to 7.0 will apparently disappear from Firefox.

This issue will be resolved in Firefox 7.0.1, which should arrive as an update shortly. In the meantime, you can try installing this extension as a workaround: it should cause the 'missing' add-ons to return.

[edit] Live USB overlay (persistent storage) not mounted on boot

link to this item - Bugzilla: #706122

Due to a defect in Package-x-generic-16.pngdracut, overlay (persistent storage) is not properly mounted on boot. An updated dracut-009-11.fc15 is available to resolve the issue, however this update will not correct existing Fedora 15 live images.

To temporarily workaround this problem with Fedora 15 live media...

  1. When booting live media, press [Tab] at the bootloader screen
  2. Add the following boot arguments
    rd.break=pre-trigger
  3. When the boot process stops and presents a shell prompt, type the following commands
     mkdir /overlayfs ; exit 
  4. When the boot process stops again and presents a shell prompt, type the following command
    exit 


For a permanent fix, you may rebuild the Fedora 15 live media to include the updated Package-x-generic-16.pngdracut package following instructions at How_to_create_and_use_a_Live_CD.

[edit] General buggy or missing functions in GNOME Shell network applet

link to this item

GNOME Shell features an integrated NetworkManager configuration interface, provided by an applet in the top panel and a configuration interface in System Settings. However, as of Fedora 15 Beta, these tools have not yet achieved feature parity with the configuration interface from GNOME 2, provided by the old nm-applet. Some features are still missing and there are known bugs with others. Major ones will be listed individually here, but as a general principle, if you encounter problems or missing features trying to configure your network using the GNOME 3 applet and System Settings interface, you can run the standalone nm-connection-editor tool, which makes all the operations not yet implemented in the GNOME 3 interface available. You can launch nm-connection-editor from a console, from the alt-f2 Run dialog, or from the overview (type nm-connection-editor or search for an entry named Network Connections).

GNOME 3's fallback mode uses the old nm-applet, and is not subject to this issue.

[edit] Laptop screen dims when switching to battery power or idle mode but never brightens again

link to this item - GNOME Bugzilla: #650405

Due to a bug in the screen brightness control logic in gnome-power-manager, laptop screens will dim as expected when switching from mains to battery power and dim further when the system is idle in battery mode, but will never brighten again when the system is no longer idle, or when you connect back to the mains. Eventually the screen will end up at its lowest possible brightness and be stuck there.

The only workaround is to disable screen dimming via the control center, or to manually reset the brightness to 100% via the keyboard (if you have brightness keys) or the control center every so often.

An updated gnome-power-manager package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, run this command:
su -c 'yum --enablerepo=updates-testing update gnome-power-manager'

[edit] System memory in use rises constantly (memory leak) when using GNOME Shell

link to this item - Bugzilla: #672117

Some users have noticed memory leaks in GNOME Shell; that is, when Shell is running, the system memory in use by the gnome-shell process rises constantly. The severity of the leak can vary from system to system, but it usually starts out using around 60-70MB of system memory, and rises to over 200MB after a day or two. To work around the problem, simply restart the Shell when its memory usage gets too high: run killall gnome-shell, or from the Run dialog - triggered by the key combination alt-f2 - simply type the single letter r and hit enter.

[edit] Cannot log in to GNOME 3 with Iranian (fa_IR) locale selected

link to this item - Bugzilla: #703060

A bug in GNOME Shell makes log in to that environment fail if the fa_IR (Iranian) locale is selected as the system locale. Various errors related to Argument 'text' (type utf8) may not be null will be present in the ~/.xsession-errors file.

You can work around the issue by using a different locale, or by removing these lines from the file /usr/share/gnome-shell/js/ui/environment.js:

    Date.prototype.toLocaleFormat = function(format) {
        return Shell.util_format_date(format, this.getTime());
    };

[edit] Cannot select language or keyboard layout at login screen

link to this item - Bugzilla: #681750

In previous Fedora releases, the login screen (when using the gdm login manager, as is the default from a network, DVD or desktop live image install) had menus for selecting the language and keyboard layout to be used in the session. In Fedora 15, these menus are removed from gdm. To set the system language and keyboard layout you will need to open the User menu (at the top right hand corner of the screen), click on System Settings, and then click on Region and Language in the window that opens up.

[edit] "could not add package update for fedora-release-rawhide-15-3(noarch)updates: fedora-release-rawhide-15-3.noarch"

link to this item - Bugzilla: #716752

A bug in PackageKit (which does not affect updating via yum on the command line) prevents easily updating to fedora-release-15-3. Other updates can still be applied using PackageKit if the update for fedora-release-15-3 is unchecked first. To update fedora-release-15-3 itself using PackageKit, first click on the + sign next to "fedora-release-15-3 (noarch)" to see both of the associated package updates (fedora-release-15-3 and fedora-release-rawhide-15-3), then uncheck fedora-release-rawhide-15-3, then click "Install Updates". It asks to confirm removing "Rawhide repo definitions". Click "Continue" and it will then work. (Note that the fedora-release-rawhide package is only needed in order to upgrade to Rawhide, and can still be installed manually for this purpose.)