From Fedora Project Wiki

(Add bug#591776)
(Add bug#590640)
Line 76: Line 76:


Due to a bug in {{package|tigervnc}}, some keys may not be work as expected when installing Fedora 13 64-bit using {{command|vnc}}.  While some keys may not work as expected, users are still able to complete the install as directed using the mouse and keyboard.  While this issue is resolved in future versions of Fedora, users may work around this problem by using an [http://jlaska.fedorapeople.org/updates-591776.img {{filename|updates.img}}] when installing Fedora 13 64-bit using {{command|vnc}}.  For assistance on using an updates.img, refer to [[Anaconda/Updates]].
Due to a bug in {{package|tigervnc}}, some keys may not be work as expected when installing Fedora 13 64-bit using {{command|vnc}}.  While some keys may not work as expected, users are still able to complete the install as directed using the mouse and keyboard.  While this issue is resolved in future versions of Fedora, users may work around this problem by using an [http://jlaska.fedorapeople.org/updates-591776.img {{filename|updates.img}}] when installing Fedora 13 64-bit using {{command|vnc}}.  For assistance on using an updates.img, refer to [[Anaconda/Updates]].
{{anchor|system-error-22}}
=== SystemError: (22, 'Invalid argument') ===
<small>[[#system-error-22|link to this item]] - [[rhbug:590640|Bugzilla: #590640]]</small>
When installing Fedora 13 from a remote NFS share, you may encounter an exception referring to ''SystemError: (22, 'Invalid argument')''.  Investigation into the problem indicates the failure will occur when the Fedora installation boot media does not match the remote installation media available via NFS share.  Users are directed to confirm that Fedora release used to boot the installer matches the Fedora available on remote NFS share.  Users can confirm the boot media and remote installation media match by ensuring the contents of the {{filename|.buildstamp}} match.  The {{filename|.buildstamp}} is available inside the {{filename|images/install.img}} file.  See the example below for guidance on inspecting the {{filename|.buildstamp}} file.
<pre>
# mount -o loop /dev/sr0 /media
# mkdir /tmp/squashfs
# mount -o loop /media/images/install.img /tmp/squashfs
# cat /tmp/squashfs/.buildstamp
201005130056.i386
Fedora
13
https://bugzilla.redhat.com</pre>


{{anchor|bootfrommdraid}}
{{anchor|bootfrommdraid}}

Revision as of 19:19, 24 May 2010

This page documents common bugs in Fedora 13 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 13 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 13 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 F13 Alpha release announcement and the draft Fedora 13 release notes for specific information about changes in Fedora 13: 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 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)


Issues when upgrading from previous releases

Installer fails after upgrade with writeGrub() error

link to this item - Bugzilla: #568567

During a system upgrade using the Fedora 13 Alpha installer, a failure will present after the upgrade process has completed. A sample failure is available for comparison. The presence of this failure does not impact the upgraded system. In fact, you may reboot the installer and return to your upgraded Fedora 13 system. This bug has been fixed in anaconda-13.33-1 and will be available in Fedora 13 Beta. Until then, should you wish to workaround the bug, a updates.img is available. For help using an updates.img, see Anaconda/Updates.

Preupgrade doesn't work with default-sized /boot partition

link to this item

Preupgrade is intended to provide a hassle-free method for upgrading a system to the current release of Fedora. Testing identified that users of Fedora 12 (and earlier) who installed their systems using the recommended /boot partition size of 200 MiB will not be able to upgrade their systems using preupgrade. The /boot filesystem is used to store the kernel and initial ramdisk images that form the core of the Fedora operating system. Its presence is required by several utilities including grub, kernel and preupgrade.

Users that have /boot partition size of at least 250 MiB should not have problems with using preupgrade. For others it is recommended to simply download Fedora 13 DVD/CD/netinst install medium and do a standard system upgrade. More experienced users that still want to use preupgrade may refer to these additional tips to free up space in /boot.

For Fedora 13 the default /boot partition size was increased to 500 MiB to avoid these problems in the future.

Installation issues

SpaceEnter, and arrow keys don't work in x86_64 VNC installs

link to this item - Bugzilla: #591776

Due to a bug in tigervnc, some keys may not be work as expected when installing Fedora 13 64-bit using vnc. While some keys may not work as expected, users are still able to complete the install as directed using the mouse and keyboard. While this issue is resolved in future versions of Fedora, users may work around this problem by using an updates.img when installing Fedora 13 64-bit using vnc. For assistance on using an updates.img, refer to Anaconda/Updates.

SystemError: (22, 'Invalid argument')

link to this item - Bugzilla: #590640

When installing Fedora 13 from a remote NFS share, you may encounter an exception referring to SystemError: (22, 'Invalid argument'). Investigation into the problem indicates the failure will occur when the Fedora installation boot media does not match the remote installation media available via NFS share. Users are directed to confirm that Fedora release used to boot the installer matches the Fedora available on remote NFS share. Users can confirm the boot media and remote installation media match by ensuring the contents of the .buildstamp match. The .buildstamp is available inside the images/install.img file. See the example below for guidance on inspecting the .buildstamp file.

# mount -o loop /dev/sr0 /media
# mkdir /tmp/squashfs
# mount -o loop /media/images/install.img /tmp/squashfs
# cat /tmp/squashfs/.buildstamp
201005130056.i386
Fedora
13
https://bugzilla.redhat.com

Booting from an mdraid mirror without a separate /boot fails

link to this item - Bugzilla: #584596

Installing a new system with / on an mdraid mirror without a separate /boot will fail as anaconda creates the / mdraid set with 1.1 metadata which makes it unsuitable to boot from. Workaround: use a separate mdraid mirror for /boot if you want to boot from an mdraid mirror. This issue will be fixed in Fedora 14.

Software issues

PackageKit silently fails to update

should be already fixed now

link to this item - Bugzilla: #567346 Bugzilla: #569352

After installing Fedora 13 Alpha, some testers experienced a problem where the Software Update utility (provided by gnome-packagekit) fails to update the system software when requested. The Software Update utility will quickly report that the software update has completed without actually downloading and installing any updates. Running the Software Update utility again will show that no updates have been applied.

It is believed that a yum plugin provided by yum-langpacks may introduce package dependency conflicts, which will cause the update to silently fail. The problem may affect upgrades using both the Software Update utility and yum. Testing also demonstrated that the problem was difficult to reproduce and depends on whether the yum-langpacks plugin is installed, and whether certain conditions exist in the package repositories used during the update.

If you are unable to update your system and the problem description above matches your symptoms, you may work around the issue by removing the yum-langpacks package. To remove the package you may either:

  1. Open a terminal and type: su -c 'yum remove yum-langpacks'
  2. Or, from the default Desktop environment
    1. Select the System -> Administration -> Add/Remove Software menu item
    2. Enter the text yum-langpacks in the text-box
    3. Deselect the check-box associated with yum-langpacks and select, Apply

GNOME Shell fails to run at all

link to this item - Bugzilla: #567116

Fedora 13 Beta includes version 1.2 of the Clutter toolkit, but gnome-shell has not yet been ported to work with this version. As a consequence, in Fedora 13 Beta, any attempt to use GNOME Shell will fail. Work to port GNOME Shell to Clutter 1.2 is under way, and we hope to include a usable GNOME Shell in Fedora 13.