Common F9 bugs

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
 
(19 intermediate revisions by 12 users not shown)
Line 1: Line 1:
<!-- page was renamed from Bugs/F9Common
 
-->
 
= Fedora 9 - Common Bugs and Known Issues  =
 
 
 
This page documents common bugs in Fedora 9 and, if available, fixes or workarounds for these problems.  If you find your problem in this page, ''do not file a bug for it.''  Where appropriate, a reference to the current bug(s) in Bugzilla is included.
 
This page documents common bugs in Fedora 9 and, if available, fixes or workarounds for these problems.  If you find your problem in this page, ''do not file a bug for it.''  Where appropriate, a reference to the current bug(s) in Bugzilla is included.
  
<!-- UNCOMMENT FOR F10 ALPHA: With the alpha release of Fedora 10 comes the [[Bugs/F10Common| Bugs/F10Common]] page.
+
With the beta release of Fedora 10 comes the [[Common F10 bugs]] page.
-->
+
  
 
== Release Summary, Announcement and Notes ==
 
== Release Summary, Announcement and Notes ==
Line 18: Line 13:
 
== Common Issues ==
 
== Common Issues ==
  
<!-- {{Anchor|Issue-Foo}}
+
<!-- Example issue
-->
+
{{Anchor|Issue-Foo}}
<!-- === Issue Foo (example) ===
+
=== Issue Foo (example) ===
-->
+
<small>[[{{subst:PAGENAME}}#Issue-Foo|link to this item]] - [https://bugzilla.redhat.com/XXXXXX Bugzilla: #XXXXXXX]</small>
<!-- [#Issue-Foo link to this item] - [https://bugzilla.redhat.com/XXXXXX Bugzilla: #XXXXXXX]  
+
 
-->
+
Words words words. Blah blah blah.
<!--
+
-->
+
<!-- Words words words. Blah blah blah.
+
-->
+
<!--
+
 
-->
 
-->
  
 
=== Proprietary (third-party) video drivers===
 
=== Proprietary (third-party) video drivers===
 
{{Anchor|third-party-drivers}}
 
{{Anchor|third-party-drivers}}
[#third-party-drivers link to this item]  
+
<small>[[Bugs/F9Common#third-party-drivers|link to this item]]</small>
  
Fedora ships a new X.Org X11 server (1.4.99) which brings a large number of benefits to users and a new ABI. All drivers contained within Fedora have been ported to use this ABI and mostly work as expected. Third-party drivers from some vendors (AMD (fglrx) and nVidia) have taken time to be compatible with this new X.Org ABI. This is not a bug in Fedora, nor even something Fedora can fix, only the third-party vendors can update the drivers due to their choice of licensing. Refer LWN for more details at
+
Fedora ships a new X.Org X11 server (1.4.99) which brings a large number of benefits to users and a new ABI as described in the [[Releases/9/FeatureList | feature list]].
 +
 
 +
All drivers contained within Fedora have been ported to use this ABI and mostly work as expected. Third-party drivers from some vendors (AMD (fglrx)) are not yet compatible with this new X.Org ABI. (nVidia has also taken their time, but as of May 28, 2008, an updated driver is available from them and from third-party repositories.) This is not a bug in Fedora, nor even something Fedora can fix, only the third-party vendors can update the drivers due to their choice of licensing. Refer LWN for more details at
  
 
http://lwn.net/Articles/283291/
 
http://lwn.net/Articles/283291/
  
The latest proprietary nvidia drivers can be found from the discussion at  
+
You can usually find proprietary drivers in third party repositories such as Livna at http://rpm.livna.org
  
https://www.redhat.com/archives/fedora-devel-list/2008-May/msg02370.html
 
  
Note that Fedora Project does not recommend or support proprietary software.  
+
Note that Fedora Project does not recommend or support proprietary software.
  
 
=== Touchpad doesn't work ===
 
=== Touchpad doesn't work ===
  
 
{{Anchor|touchpad-issues}}
 
{{Anchor|touchpad-issues}}
[#touchpad-issues link to this item] - [http://bugzilla.redhat.com/439386 #439386]  along with 232630, 172797, 436641.
+
<small>[[Bugs/F9Common#touchpad-issues|link to this item]] - [http://bugzilla.redhat.com/439386 Bugzilla: #439386]  along with 232630, 172797, 436641.</small>
  
 
Touchpad doesn't work on a number of systems.
 
Touchpad doesn't work on a number of systems.
  
 
{{Anchor|samsung-hdds}}
 
{{Anchor|samsung-hdds}}
 +
 
=== Some Samsung hard disks crash the installer ===
 
=== Some Samsung hard disks crash the installer ===
[#samsung-hdds link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=442457 Bugzilla: #442457]  
+
<small>[[Bugs/F9Common#samsung-hdds|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=442457 Bugzilla: #442457] </small>
  
 
Some Samsung hard disks respond to certain queries with a model string that ends in a slash ("/").  This confuses HAL and produces an error that prevents normal installation, although the Live installer is unaffected.
 
Some Samsung hard disks respond to certain queries with a model string that ends in a slash ("/").  This confuses HAL and produces an error that prevents normal installation, although the Live installer is unaffected.
Line 62: Line 54:
 
{{Anchor|emacs-upgrade}}
 
{{Anchor|emacs-upgrade}}
 
=== Emacs not upgrading cleanly ===
 
=== Emacs not upgrading cleanly ===
[#emacs-upgrade link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=394131 Bugzilla: #394131]  
+
<small>[[Bugs/F9Common#emacs-upgrade|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=394131 Bugzilla: #394131] </small>
  
 
If you are upgrading to Fedora 9 and use <code>emacs</code>, you must upgrade to the latest version of <code>emacs</code> for your prior release to ensure a clean upgrade. Fedora 8 users must have <code>emacs-22.1-10.fc8</code> or later, while Fedora 7 users must have <code>emacs-22.1-7.fc7</code>.
 
If you are upgrading to Fedora 9 and use <code>emacs</code>, you must upgrade to the latest version of <code>emacs</code> for your prior release to ensure a clean upgrade. Fedora 8 users must have <code>emacs-22.1-10.fc8</code> or later, while Fedora 7 users must have <code>emacs-22.1-7.fc7</code>.
  
 
=== Emacs flyspell-mode produces "Enabling Flyspell mode gave an error" ===
 
=== Emacs flyspell-mode produces "Enabling Flyspell mode gave an error" ===
[#emacs-flyspell link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=448414 Bugzilla: #448414]  
+
<small>[[Bugs/F9Common#emacs-flyspell|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=448414 Bugzilla: #448414]</small>
  
 
As a result of the
 
As a result of the
Line 88: Line 80:
 
{{Anchor|readme-burning-isos}}
 
{{Anchor|readme-burning-isos}}
 
=== README-BURNING-ISOS document is ugly ===
 
=== README-BURNING-ISOS document is ugly ===
[#readme-burning-isos link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=446092 Bugzilla: #446092]  
+
<small>[[Bugs/F9Common#readme-burning-isos|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=446092 Bugzilla: #446092]</small>
  
 
Due to a problem with the XML conversion package <code>xmlto</code>, the <code>README-BURNING-ISOS-en_US.txt</code> file on the Fedora 9 ISO images is hard to read.  You can find a current readable version at: http://docs.fedoraproject.org/readme-burning-isos/
 
Due to a problem with the XML conversion package <code>xmlto</code>, the <code>README-BURNING-ISOS-en_US.txt</code> file on the Fedora 9 ISO images is hard to read.  You can find a current readable version at: http://docs.fedoraproject.org/readme-burning-isos/
Line 94: Line 86:
 
{{Anchor|Xfce-media-installs}}
 
{{Anchor|Xfce-media-installs}}
 
=== Xfce-media-installs ===
 
=== Xfce-media-installs ===
[#Xfce-media-installs link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=446621 Bugzilla: #446621]  
+
<small>[[Bugs/F9Common#Xfce-media-installs|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=446621 Bugzilla: #446621]</small>
  
 
The Xfce group may show as available for install on media installed (cd/dvd), when the Xfce packages are not available on the media. The install will complete, but no Xfce desktop will
 
The Xfce group may show as available for install on media installed (cd/dvd), when the Xfce packages are not available on the media. The install will complete, but no Xfce desktop will
 
be available. After the install, run a 'yum groupinstall XFCE' or install the Xfce group from the add/remove software GUI. This will install the Xfce desktop.
 
be available. After the install, run a 'yum groupinstall XFCE' or install the Xfce group from the add/remove software GUI. This will install the Xfce desktop.
 +
 +
{{Anchor|no-sound-adobe-flash}}
 +
=== No Sound with Adobe Flash ===
 +
<small>[[Bugs/F9Common#no-sound-adobe-flash|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=447108 Bugzilla: #447108]</small>
 +
 +
If there is no sound after installing adobe flash plugin, install package libflashsupport.
 +
<pre>
 +
yum install libflashsupport
 +
</pre>
 +
 +
{{Anchor|Xen-Dom0}}
 +
=== Xen Dom0 (host) support ===
 +
<small>[[Bugs/F9Common#Xen-Dom0-support|link to this item]] - [https://bugzilla.redhat.com/437930 Bugzilla: #437930]</small>
 +
 +
Fedora 9 does not provide support for running Xen Dom0 (hosts). The provided Xen kernel is for Guest (DomU) installs running under another
 +
operating systems Dom0. You can continue to run Fedora 8 Dom0's until Fedora 10 is released.
  
 
== Less Common Issues ==
 
== Less Common Issues ==
Line 103: Line 111:
 
{{Anchor|s-c-printer-smb}}
 
{{Anchor|s-c-printer-smb}}
 
=== system-config-printer won't start ===
 
=== system-config-printer won't start ===
[#s-c-printer-smb link to this item]  - [https://bugzilla.redhat.com/show_bug.cgi?id=443205 Bugzilla: #443205]  
+
<small>[[Bugs/F9Common#s-c-printer-smb|link to this item]]  - [https://bugzilla.redhat.com/show_bug.cgi?id=443205 Bugzilla: #443205]</small>
  
 
If there is a print server on the local network that advertises a Windows shared printer (anything with a <code>smb://</code> URL), the printer administration tool <code>system-config-printer</code> may fail to start.
 
If there is a print server on the local network that advertises a Windows shared printer (anything with a <code>smb://</code> URL), the printer administration tool <code>system-config-printer</code> may fail to start.
Line 111: Line 119:
 
{{Anchor|gdm-language-issue}}
 
{{Anchor|gdm-language-issue}}
 
=== GDM language selector isn't available initially ===
 
=== GDM language selector isn't available initially ===
[#gdm-language-issue link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=445631 Bugzilla: #445631]  
+
<small>[[Bugs/F9Common#gdm-language-issue|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=445631 Bugzilla: #445631]</small>
  
 
The very first time GDM starts up the language selector will not appear when a user is selected.  Subsequent runs of GDM work okay.  This is going to be addressed in an F9 update.
 
The very first time GDM starts up the language selector will not appear when a user is selected.  Subsequent runs of GDM work okay.  This is going to be addressed in an F9 update.
Line 118: Line 126:
  
 
=== Installer crashes when customizing packages, if using Russian ===
 
=== Installer crashes when customizing packages, if using Russian ===
[#russian link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=445517 Bugzilla: #445517]  
+
<small>[[Bugs/F9Common#russian|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=445517 Bugzilla: #445517]</small>
  
 
Due to a problem with the Russian translation for the installer, if you attempt to customize your packages the installer may crash when you click a checkbox in the customization screen.
 
Due to a problem with the Russian translation for the installer, if you attempt to customize your packages the installer may crash when you click a checkbox in the customization screen.
Line 124: Line 132:
 
You can work around this problem by either choosing to customize packages ''after'' installation, or by installing in a different language, and changing the system language to Russian after installation.
 
You can work around this problem by either choosing to customize packages ''after'' installation, or by installing in a different language, and changing the system language to Russian after installation.
  
<!-- {{Anchor|Issue-Foo-the-Lesser}}
+
{{Anchor|USB}}
-->
+
 
<!-- === Foo the Lesser ===
+
=== USB Drives Cause Install to Fail ===
-->
+
<small>[[Bugs/F9Common#USB|link to this item]] - [https://bugzilla.redhat.com/show_bug.cgi?id=466106 Bugzilla: #466106]</small>
<!-- [#Issue-Foo-the-Lesser link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=XXXXXX Bugzilla: #XXXXXX]  
+
 
-->
+
USB drives that are attached to the system and powered up may cause the install to fail. If possible power down the device, remove it and restart the installation. Once the system is updated the device(s) will work properly.  
<!--
+
 
-->
+
<!-- Description goes here.
+
-->
+
 
<!--
 
<!--
 +
{{Anchor|Issue-Foo-the-Lesser}}
 +
=== Foo the Lesser ===
 +
<small>[[{{subst:PAGENAME}}#Issue-Foo-the-Lesser|link to this item] - [https://bugzilla.redhat.com/show_bug.cgi?id=XXXXXX Bugzilla: #XXXXXX]</small>
 +
 +
Description goes here.
 
-->
 
-->
  
 
== Behavior Changes ==
 
== Behavior Changes ==
  
<!-- {{Anchor|new-behavior-foo}}
 
-->
 
<!-- === New Behavior Foo ===
 
-->
 
<!-- [#new-behavior-foo link to this item]
 
-->
 
 
<!--
 
<!--
-->
+
{{Anchor|new-behavior-foo}}
<!-- Description goes here.
+
=== New Behavior Foo ===
 +
<small>[[{{subst:PAGENAME}}#new-behavior-foo|link to this item]]</small>
 +
 
 +
Description goes here.
 
-->
 
-->
  
 
{{Anchor|networkmanager-static}}
 
{{Anchor|networkmanager-static}}
 
=== NetworkManager now handles static configuration files ===
 
=== NetworkManager now handles static configuration files ===
[#networkmanager-static link to this item]  
+
<small>[[Bugs/F9Common#networkmanager-static|link to this item]]</small>
  
!NetworkManager can now handle the static network configuration files written by Anaconda and <code>system-config-network</code>, which reside in <code>/etc/sysconfig/network-scripts</code>.
+
NetworkManager can now handle the static network configuration files written by Anaconda and <code>system-config-network</code>, which reside in <code>/etc/sysconfig/network-scripts</code>.
  
 
This may cause problems if you enable both the <code>network</code> service and the <code>NetworkManager</code> service.
 
This may cause problems if you enable both the <code>network</code> service and the <code>NetworkManager</code> service.
  
 
{{Anchor|packagekit}}
 
{{Anchor|packagekit}}
 +
 
=== New Package Manager (PackageKit) ===
 
=== New Package Manager (PackageKit) ===
[#packagekit link to this item]  
+
<small>[[Bugs/F9Common#packagekit|link to this item]]</small>
  
Fedora 9 includes [http://packagekit.org/ PackageKit] , a new distribution-neutral package management system. It has some important differences from the older system - read the PackageKitFaq for details.
+
Fedora 9 includes [http://packagekit.org/ PackageKit] , a new distribution-neutral package management system. It has some important differences from the older system - read the [[PackageKitFaq]] for details.
  
 
== References ==
 
== References ==
Line 168: Line 176:
 
* [[KernelCommonProblems]]
 
* [[KernelCommonProblems]]
  
----
+
[[Category:Bugs|Common F09 bugs]]
[[Category:Bugs]]
+

Latest revision as of 04:46, 13 May 2010

This page documents common bugs in Fedora 9 and, if available, fixes or workarounds for these problems. If you find your problem in this page, do not file a bug for it. Where appropriate, a reference to the current bug(s) in Bugzilla is included.

With the beta release of Fedora 10 comes the Common F10 bugs page.

Contents

[edit] Release Summary, Announcement and Notes

[edit] My Bug Is Not Listed

Not every bug is listed in this page. You can use bugzilla queries in the bottom of this page for that. We have collected this based on commonly discussed issues in our mailing lists and forums. If you believe any particular bug report is missed out here and if you have wiki access, add it this page or contact RahulSundaram with the bugzilla report number explaining why you believe that particular report qualifies as a common issue.

[edit] Common Issues

[edit] Proprietary (third-party) video drivers

link to this item

Fedora ships a new X.Org X11 server (1.4.99) which brings a large number of benefits to users and a new ABI as described in the feature list.

All drivers contained within Fedora have been ported to use this ABI and mostly work as expected. Third-party drivers from some vendors (AMD (fglrx)) are not yet compatible with this new X.Org ABI. (nVidia has also taken their time, but as of May 28, 2008, an updated driver is available from them and from third-party repositories.) This is not a bug in Fedora, nor even something Fedora can fix, only the third-party vendors can update the drivers due to their choice of licensing. Refer LWN for more details at

http://lwn.net/Articles/283291/

You can usually find proprietary drivers in third party repositories such as Livna at http://rpm.livna.org


Note that Fedora Project does not recommend or support proprietary software.

[edit] Touchpad doesn't work

link to this item - Bugzilla: #439386 along with 232630, 172797, 436641.

Touchpad doesn't work on a number of systems.

[edit] Some Samsung hard disks crash the installer

link to this item - Bugzilla: #442457

Some Samsung hard disks respond to certain queries with a model string that ends in a slash ("/"). This confuses HAL and produces an error that prevents normal installation, although the Live installer is unaffected.

We are working on an patch to fix the problem. For now, users are advised to install from Live or use a different hard disk model if possible.

[edit] Emacs not upgrading cleanly

link to this item - Bugzilla: #394131

If you are upgrading to Fedora 9 and use emacs, you must upgrade to the latest version of emacs for your prior release to ensure a clean upgrade. Fedora 8 users must have emacs-22.1-10.fc8 or later, while Fedora 7 users must have emacs-22.1-7.fc7.

[edit] Emacs flyspell-mode produces "Enabling Flyspell mode gave an error"

link to this item - Bugzilla: #448414

As a result of the dictionary consolidation work , attempts to use M-x flyspell-mode, or to automatically enable it via lines in your .emacs file such as:

(add-hook 'text-mode-hook
'(lambda () (flyspell-mode t)))
(add-hook 'prog-mode-hook
'(lambda () (flyspell-prog-mode t)))

fail with the error message quoted above. One circumvention is to (also) add to your .emacs file the following:

;; for Fedora 9 where ispell dictionaries are gone ...
(setq ispell-program-name "hunspell")

[edit] README-BURNING-ISOS document is ugly

link to this item - Bugzilla: #446092

Due to a problem with the XML conversion package xmlto, the README-BURNING-ISOS-en_US.txt file on the Fedora 9 ISO images is hard to read. You can find a current readable version at: http://docs.fedoraproject.org/readme-burning-isos/

[edit] Xfce-media-installs

link to this item - Bugzilla: #446621

The Xfce group may show as available for install on media installed (cd/dvd), when the Xfce packages are not available on the media. The install will complete, but no Xfce desktop will be available. After the install, run a 'yum groupinstall XFCE' or install the Xfce group from the add/remove software GUI. This will install the Xfce desktop.

[edit] No Sound with Adobe Flash

link to this item - Bugzilla: #447108

If there is no sound after installing adobe flash plugin, install package libflashsupport.

yum install libflashsupport

[edit] Xen Dom0 (host) support

link to this item - Bugzilla: #437930

Fedora 9 does not provide support for running Xen Dom0 (hosts). The provided Xen kernel is for Guest (DomU) installs running under another operating systems Dom0. You can continue to run Fedora 8 Dom0's until Fedora 10 is released.

[edit] Less Common Issues

[edit] system-config-printer won't start

link to this item - Bugzilla: #443205

If there is a print server on the local network that advertises a Windows shared printer (anything with a smb:// URL), the printer administration tool system-config-printer may fail to start.

This will be fixed with a soon-to-be-released update.

[edit] GDM language selector isn't available initially

link to this item - Bugzilla: #445631

The very first time GDM starts up the language selector will not appear when a user is selected. Subsequent runs of GDM work okay. This is going to be addressed in an F9 update.

[edit] Installer crashes when customizing packages, if using Russian

link to this item - Bugzilla: #445517

Due to a problem with the Russian translation for the installer, if you attempt to customize your packages the installer may crash when you click a checkbox in the customization screen.

You can work around this problem by either choosing to customize packages after installation, or by installing in a different language, and changing the system language to Russian after installation.

[edit] USB Drives Cause Install to Fail

link to this item - Bugzilla: #466106

USB drives that are attached to the system and powered up may cause the install to fail. If possible power down the device, remove it and restart the installation. Once the system is updated the device(s) will work properly.


[edit] Behavior Changes

[edit] NetworkManager now handles static configuration files

link to this item

NetworkManager can now handle the static network configuration files written by Anaconda and system-config-network, which reside in /etc/sysconfig/network-scripts.

This may cause problems if you enable both the network service and the NetworkManager service.

[edit] New Package Manager (PackageKit)

link to this item

Fedora 9 includes PackageKit , a new distribution-neutral package management system. It has some important differences from the older system - read the PackageKitFaq for details.

[edit] References