(drop fixed Alpha issues, a few other cleanups) |
|||
| Line 51: | Line 51: | ||
--> | --> | ||
== Installation issues == | == Installation issues == | ||
{{Anchor|keyboard-console}} | {{Anchor|keyboard-console}} | ||
=== Non-US keyboard layouts don't work at console === | === Non-US keyboard layouts don't work at console === | ||
| Line 102: | Line 63: | ||
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. | 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: | BIOS: {{command|grub2-mkconfig -o /boot/grub2/grub.cfg}} | ||
UEFI: | UEFI: {{command|grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg}} | ||
Then reboot your machine. | Then reboot your machine. | ||
== Hardware issues == | == Hardware issues == | ||
{{Anchor|arm-beagle-bone}} | |||
=== ARM: Beagle Bone Black HDMI issues === | === ARM: Beagle Bone Black HDMI issues === | ||
<small>[[Common F20 bugs#arm-beagle-bone|link to this item]] - [[rhbug:1012025|Bugzilla: #1012025]]</small> | <small>[[Common F20 bugs#arm-beagle-bone|link to this item]] - [[rhbug:1012025|Bugzilla: #1012025]]</small> | ||
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 | 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 == | == Software issues == | ||
{{Anchor|missing-mouse}} | {{Anchor|missing-mouse}} | ||
=== Disappearing mouse cursor === | === Disappearing mouse cursor === | ||
<small>[[Common F20 bugs#missing-mouse|link to this item]] - [[rhbug:1008965|Bugzilla: #1008965]]</small> | <small>[[Common F20 bugs#missing-mouse|link to this item]] - [[rhbug:1008965|Bugzilla: #1008965]]</small> | ||
| Line 138: | Line 84: | ||
Moving to another tty and back typically resolves the issue. | Moving to another tty and back typically resolves the issue. | ||
{{Anchor|php-zip}} | {{Anchor|php-zip}} | ||
| Line 159: | Line 97: | ||
<small>[[Common F20 bugs#kde-vm|link to this item]] - [[rhbug:1027831| Bugzilla: #1027831]]</small> | <small>[[Common F20 bugs#kde-vm|link to this item]] - [[rhbug:1027831| Bugzilla: #1027831]]</small> | ||
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 [http://admin.fedoraproject.org/updates/xorg-x11-drv-qxl-0.1.1-2.fc20 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 [http://admin.fedoraproject.org/updates/xorg-x11-drv-qxl-0.1.1-2.fc20 report to Bodhi] whether it solves the problem. To test the update, run this command: | |||
<pre>su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-qxl'</pre> | |||
{{Anchor| | {{Anchor|kde-live-wireless}} | ||
=== KDE live networking doesn't work === | === KDE live wireless networking doesn't work === | ||
<small>[[Common F20 bugs# | <small>[[Common F20 bugs#kde-live-wireless|link to this item]] - [[rhbug:1004621|Bugzilla: #1004621]]</small> | ||
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. | 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. | ||
| Line 171: | Line 112: | ||
<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 | 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. | ||
Revision as of 23:55, 12 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.
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).
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
- 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:
- 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
Non-US keyboard layouts don't work at console
link to this item - Bugzilla: #1028207
Fedora 20 Beta installation won't honor the keymap picked during installation in virtual terminals or when decrypting the filesystem. X, however, will retain the keymap picked during installation. The current workaround is to simply defer picking a keymap until after installation.
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.
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
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.