Common F20 bugs

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(add a generic entry for resize bugs)
(copy and paste of the partial kickstart section from Common F19 bugs)
(2 intermediate revisions by one user not shown)
Line 70: Line 70:
  
 
Then reboot your machine.
 
Then reboot your machine.
 +
 +
{{Anchor|partial-kickstart-problems}}
 +
=== Problems with Installation Source and Installation Destination spokes when installing from a partially complete kickstart ===
 +
<small>[[#partial-kickstart-problems|link to this item]] - [[rhbug:972265|Bugzilla: #972265]] - [[rhbug:972266|Bugzilla: #972266]]</small>
 +
 +
If you attempt to install Fedora 20 using a partially-complete kickstart - in particular, a kickstart which specifies a package set but no installation source or destination - you will find that the interactive process for setting those options behaves strangely. On the Installation Source spoke, you may not be able to use the default ''Closest mirror'' option. If you are affected by this problem, you can manually enter the URL of the Fedora 20 mirror list, and check the ''This URL refers to a mirror list.'' box. The URLs for the 64-bit and 32-bit mirror lists are <code>https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=x86_64</code> and <code>https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=i386</code> respectively.
 +
 +
The Installation Destination spoke appears to require you to complete it multiple times to complete configuration: each time it will set another element of the configuration. Even after doing this, you may find a bootloader target disk is not selected. To set one, first enter the ''Full disk summary and bootloader...'' screen and select not to install a bootloader, and complete the spoke once again. Then complete the spoke one more time, this time selecting the correct target disk for the bootloader, and the configuration should now be complete.
 +
 +
As these issues take some effort to work around, it may be a better idea simply to use a complete kickstart, or at least one which specifies an installation source and destination. The [[Anaconda/Kickstart]] page should help you with the required syntax.
  
 
== Hardware issues ==
 
== Hardware issues ==
Line 119: Line 129:
  
 
{{Anchor|seahorse-keyring}}
 
{{Anchor|seahorse-keyring}}
=== Gnome-shell crashes after creating a keyring without a password ===
+
=== GNOME Shell crashes after creating a keyring without a password ===
 
<small>[[Common F20 bugs#seahorse-keyring|link to this item]] - [[rhbug:1012844|Bugzilla: #1012844]]</small>
 
<small>[[Common F20 bugs#seahorse-keyring|link to this item]] - [[rhbug:1012844|Bugzilla: #1012844]]</small>
  
 
In Fedora 20 Beta with the GNOME desktop, if you attempt to create a new keyring without a password or change the password of your keyring to an empty string (you may do this from the "Passwords and Keys" application, or you may be prompted to create a keyring password the first time GNOME attempts to store some kind of key), the GNOME shell will crash. The workaround for this is to always use a password on your keyring. A patch is currently pending from upstream to fix this issue.
 
In Fedora 20 Beta with the GNOME desktop, if you attempt to create a new keyring without a password or change the password of your keyring to an empty string (you may do this from the "Passwords and Keys" application, or you may be prompted to create a keyring password the first time GNOME attempts to store some kind of key), the GNOME shell will crash. The workaround for this is to always use a password on your keyring. A patch is currently pending from upstream to fix this issue.
 +
 +
{{Anchor|gis-account-crash}}
 +
=== GNOME initial setup tool crashes if you cancel online account creation ===
 +
<small>[[Common F20 bugs#gis-account-crash|link to this item]] - [[rhbug:1027507|Bugzilla: #1027507]]</small>
 +
 +
If, during the 'initial setup' wizard that appears on first boot after a Fedora 20 Beta GNOME install, you enter the module for creating an 'online account' then change your mind and cancel the account creation, the tool may crash. This may result in the tool running again on your next boot, which may force you to create a second user account. If this happens to you, you can safely delete one or other account once you have successfully completed the wizard, and it will not run again.
 +
 +
Other than this there should be no significant consequences of the bug: the crash occurs quite late in the process, and no actions from earlier in the process should be lost.
 +
 +
{{Anchor|scs-startup-crash}}
 +
=== Fedora services configuration tool (system-config-services) crashes on startup ===
 +
<small>[[Common F20 bugs#scs-startup-crash|link to this item]] - [[rhbug:1007121|Bugzilla: #1007121]]</small>
 +
 +
Several testers have reported that the Fedora tool for configuring system services, {{command|system-config-services}}, crashes on startup in Fedora 20 Beta. There is no known direct workaround that makes it possible to use the tool, but you can use the {{command|systemctl}} command to manipulate services from the command line: see {{command|man systemctl}} for more details.

Revision as of 20:02, 14 November 2013

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

Note.png
Fedora 20 pre-release
Fedora 20 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 20 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).

Contents

Release Notes

Read the F20_Alpha_release_announcement for specific information about changes in Fedora 20 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)


Installation issues

Multiple issues with resizing existing volumes during installation

link to this item - Bugzilla: #1027714 Bugzilla: #1028110 Bugzilla: #1027682 Bugzilla: #1013586 Bugzilla: #1027947 Bugzilla: #1027965

Multiple bugs have been reported in Fedora 20 Beta which are related to resizing existing storage volumes as a part of the installation process. Problematic scenarios include specifying a size for a partition which is larger than it could possibly be, attempting to resize partitions at the end of the disk that leave no padding space after the partition, choosing a new size for a volume and then changing your mind and returning it to the previous size, and others.

So far as we are aware, all the bugs manifest as crashes - either immediately on trying the problematic operation, or during the first stage of installation - and none of them result in a dangerous or incorrect resize operation actually being run, so there is no known risk of data loss. Nevertheless, we particularly stress the standard advice not to install Fedora 20 Beta to a system that contains existing data of value to you, and strongly advise you not to attempt to resize storage volumes that contain data of value to you using the Fedora 20 Beta installer.

Btrfs /boot partition results in a kernel panic after kernel update

link to this item - Bugzilla: #864198

Placing /boot on a btrfs volume results in a kernel panic on reboot. Running either of the below commands (based on your setup) after a kernel update will fix this issue.

BIOS: grub2-mkconfig -o /boot/grub2/grub.cfg

UEFI: grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Then reboot your machine.

Problems with Installation Source and Installation Destination spokes when installing from a partially complete kickstart

link to this item - Bugzilla: #972265 - Bugzilla: #972266

If you attempt to install Fedora 20 using a partially-complete kickstart - in particular, a kickstart which specifies a package set but no installation source or destination - you will find that the interactive process for setting those options behaves strangely. On the Installation Source spoke, you may not be able to use the default Closest mirror option. If you are affected by this problem, you can manually enter the URL of the Fedora 20 mirror list, and check the This URL refers to a mirror list. box. The URLs for the 64-bit and 32-bit mirror lists are https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=x86_64 and https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=i386 respectively.

The Installation Destination spoke appears to require you to complete it multiple times to complete configuration: each time it will set another element of the configuration. Even after doing this, you may find a bootloader target disk is not selected. To set one, first enter the Full disk summary and bootloader... screen and select not to install a bootloader, and complete the spoke once again. Then complete the spoke one more time, this time selecting the correct target disk for the bootloader, and the configuration should now be complete.

As these issues take some effort to work around, it may be a better idea simply to use a complete kickstart, or at least one which specifies an installation source and destination. The Anaconda/Kickstart page should help you with the required syntax.

Hardware issues

ARM: Beagle Bone Black HDMI issues

link to this item - Bugzilla: #1012025

Some testers have reported that attempting to run the Beagle Bone Black over HDMI doesn't currently work. At the moment to use the Beagle Bone Black you need a serial console. As on Fedora 20 Beta TC4 the Network/MMC/Serial console currently works and the BBone Black successfully boots. Further kernel updates to resolve the other outstanding issues will be forthcoming.

Software issues

Non-US keyboard layouts not used at console

link to this item - Bugzilla: #1028207

If you pick a non-US keyboard layout as the default or only layout during Fedora 20 Beta installation, that choice won't be honored after installation in virtual terminals or when decrypting filesystems during the boot process. Graphical sessions, however, will use the keyboard layout picked during installation.

Re-doing keyboard layout selection after installation may help to work around this issue, but we are still investigating the precise cause, workarounds, and solution.

Disappearing mouse cursor

link to this item - Bugzilla: #1008965

After logging in to a desktop in Fedora 20 Alpha, the mouse cursor can become invisible. The mouse still functions, but can't be seen. This has been seen occasionally in testing on bare metal and more often in testing on virtual machines. It definitely affects GNOME and may affect other desktop environments.

Moving to another tty and back typically resolves the issue.

ZIP support in PHP

link to this item - Bugzilla: #999313

In Fedora 20, support from ZIP have been dropped from main php package and is now provided in a separate php-pecl-zip package.

If you need zip support, as for any other extension, run su -c 'yum install php-zip'

KDE crashes when in a VM

link to this item - Bugzilla: #1027831

When installing Fedora 20 Beta with the KDE desktop to a KVM-based virtual machine using the qxl virtual graphics adapter and driver, KDE will likely crash shortly after login. This can be worked around by disabling Desktop Effects. (Alt+Shift+F12) toggles desktop effects, and you can set them not to be enabled by default in the KDE Control Center.

An updated xorg-x11-drv-qxl 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 xorg-x11-drv-qxl'

KDE live wireless networking doesn't work

link to this item - Bugzilla: #1004621

When using a Fedora 20 Beta KDE live image, the plasma-nm applet doesn't connect to available networks. The workaround is to logout and then log back in and connect.

GNOME Shell crashes after creating a keyring without a password

link to this item - Bugzilla: #1012844

In Fedora 20 Beta with the GNOME desktop, if you attempt to create a new keyring without a password or change the password of your keyring to an empty string (you may do this from the "Passwords and Keys" application, or you may be prompted to create a keyring password the first time GNOME attempts to store some kind of key), the GNOME shell will crash. The workaround for this is to always use a password on your keyring. A patch is currently pending from upstream to fix this issue.

GNOME initial setup tool crashes if you cancel online account creation

link to this item - Bugzilla: #1027507

If, during the 'initial setup' wizard that appears on first boot after a Fedora 20 Beta GNOME install, you enter the module for creating an 'online account' then change your mind and cancel the account creation, the tool may crash. This may result in the tool running again on your next boot, which may force you to create a second user account. If this happens to you, you can safely delete one or other account once you have successfully completed the wizard, and it will not run again.

Other than this there should be no significant consequences of the bug: the crash occurs quite late in the process, and no actions from earlier in the process should be lost.

Fedora services configuration tool (system-config-services) crashes on startup

link to this item - Bugzilla: #1007121

Several testers have reported that the Fedora tool for configuring system services, system-config-services, crashes on startup in Fedora 20 Beta. There is no known direct workaround that makes it possible to use the tool, but you can use the systemctl command to manipulate services from the command line: see man systemctl for more details.