From Fedora Project Wiki

(boxes-flickering|Display is flickering in GNOME Boxes|1266484)
(remove systemd-udev, the update to fix the issue is now stable in F25)
Line 69: Line 69:


== Core system issues ==
== Core system issues ==
{{Common bugs issue|xorg-udev-hybrid-crash|X crashes when systemd-udev package updated on systems with multiple graphics adapters (hybrid graphics)|1341327|1378974}}
If your system has multiple graphics adapters - the most common case being laptop 'hybrid graphics' (NVIDIA Optimus or AMD 'Dynamic Switchable Graphics') - and you update the {{code|systemd-udev}} package while X is running, it is highly likely that X will crash.
This may be a severe problem if you were running the update process inside of X (e.g. from a terminal app within your desktop). The X crash will kill the update process before the update has properly completed. This may leave you with inconsistencies in the package database, which can be difficult to recover from, and cause various other consequences (these will vary depending on which parts of the update process were not completed before the crash).
The crash is triggered when the {{code|systemd-udev-trigger.service}} service is restarted, so any other action which results in that happening may also cause X to crash on affected systems.
We strongly advise against running updates from a terminal window inside a graphical desktop. We advise against this in any case, but obviously there is a specific and severe reason to avoid it in this case. The safest way to apply updates on Fedora is using the 'offline updates' system, which applies updates by rebooting to a minimal environment, installing the updates, then rebooting to the usual environment.
If you update from the GNOME Software application on Fedora Workstation (GNOME), or by clicking on the 'reboot to install updates' notifications which are shown automatically from time to time on Workstation, you are using the 'offline updates' system and will not be affected by this bug.
On other desktops or non-graphical installs, you can use the offline updates system as follows:
sudo pkcon refresh force && \
sudo pkcon update --only-download && \
sudo pkcon offline-trigger && \
sudo systemctl reboot
If you do not want to use the offline update system, we strongly advise you at least update from a VT, instead of from a terminal app in a graphical desktop. That is, press ctrl-alt-f3 to get a console login prompt, log in, and run the update from the console. If you leave X running while the update runs on an affected system, it will still crash when the {{code|systemd-udev}} package is updated, but the update process will not crash (as it is not running in X) and will complete properly.
An update to resolve this particular issue will be available soon, but due to the technical details of exactly how the bug is triggered, the update process that applies the fix will still be vulnerable to the bug. The fix can only prevent '''subsequent''' updates involving the {{code|systemd-udev}} package from triggering the bug. We intend to include the fix in the Fedora 25 Beta release, so systems freshly installed from Fedora 25 Beta should not suffer from the issue.


== Wayland issues ==
== Wayland issues ==

Revision as of 12:37, 14 October 2016

This page documents common bugs in Fedora 25 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
Pre-release version
Fedora 25 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 25 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 F25 general release announcement for specific information about changes in Fedora 25 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. Common bugs instructions provides guidance on how to add an entry to the page correctly, but the most important thing is to make sure that the bug is listed - don't worry if you don't get the format quite right, we can clean it up later.
  • 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

Dual booting Windows fails with 'relocation failed' error on some UEFI systems

link to this item - Bugzilla: #1347291

On some hardware, it's not possible to start Windows (possibly even some other OSes) from GRUB boot menu when booting over UEFI (it does not happen in BIOS mode). The message says error: relocation failed. The problem is still being investigated.

As a workaround, you can use your UEFI boot menu (the one-time boot menu is usually reachable via some hotkey like Esc, F8, F11, F12, etc) to boot Windows, which should work fine.

Advanced users can download and install grub2-2.02-0.25.fc23 (grub2 from Fedora 23), which should immediately fix the problem. However, when using this solution, the broken version of grub2 from Fedora 24 will be offered to you with every new system update, and you'll need to manually exclude it every time.

Windows entry is missing in grub when systems are installed on firmware RAID on UEFI system

link to this item - Bugzilla: #1347273

When Fedora is installed beside Windows on the firmware RAID and on UEFI it could happen that there will be Windows entry missing in grub menu.

This happens only with UEFI. User can use UEFI boot menu as a workaround (the one-time boot menu is usually reachable via some hotkey like Esc, F8, F11, F12, etc).

This bug appears just when UEFI and firmware RAID is used. So BIOS installations and normal disks (or with FW RAID turned off) shouldn't be affected.

Fedora fails to install on some RAID setups

link to this item - Bugzilla: #1333131 - Bugzilla: #1259953 - Bugzilla: #1381996

On some setups, installing Fedora over existing firmware or software RAID can cause anaconda to crash.

  • If you try to create a RAID array during setup on a system that has an existing RAID configuration using the drives from that previous RAID array, the newly-created one gets produced incorrectly and is unusable (and of course, the one you deleted is no longer there). User can restart and try again on the same selected drives (this time using free space) as workaround.
  • If you try to install to a RAID that is still being initialized (quite possible created shortly before installation), the installer might crash on start. Currently you need to wait until the initial RAID sync is complete, then you can run the installer.

OS X volumes using Apple Core Storage are not recognized by the installer and shrinking them destroys all data

link to this item - Bugzilla: #1033778

The installer appears to support volume shrink for OS X volumes (Apple Core Storage) by offering a Shrink button and sizing slider in Automatic partitioning; and likewise allow numeric resizing in Manual partitioning. However, setting the installer to resize these volumes and proceeding with installation will result in complete data loss of the volume. Resize the volume in OS X's Disk Utility to create free space before proceeding with the installation of Fedora.

Non-live install with KDE, or installing KDE post-install, also installs Cinnamon

link to this item - Bugzilla: #1349743

Due to some unfortunate interactions between the Fedora package group definitions and the Package-x-generic-16.pnglibsolv dependency solver, if you install the KDE package set from a traditional installer image (rather than the KDE live image), or try to install KDE after initial system install by running sudo dnf groupinstall kde-desktop-environment or something similar, you will get KDE...and also Cinnamon.

There is no way to work around this at system install time, besides installing from the KDE live image instead. You would just have to remove the unwanted packages manually. If you are trying to install KDE after initial system install and wish to avoid the unnecessary Cinnamon packages, running sudo dnf install @kde-desktop-environment imsettings-qt should avoid the problem.

Upgrade issues

DNF upgrade might remove essential system packages if you used PackageKit (GNOME Software, KDE Apper) in the past

link to this item - Bugzilla: #1259865

There was an unfortunate situation in the past few Fedora releases where PackageKit and DNF didn't work well together. If you installed something via PackageKit (used by GNOME Software or KDE Apper), it didn't mark such packages as "user installed" in the DNF database (which is used to differentiate user-requested packages from other packages installed purely as a dependency, but not explicitly requested by the user). Similarly, if you updated your system using PackageKit (GNOME offline updates, Apper), it erased such "user installed" flags from all updated packages. DNF then tries to remove any unnecessary packages during its next transaction (or when specifically asked using sudo dnf autoremove). This might lead to removing core system packages because DNF no longer sees them as "user installed" and considers them a no-longer-needed dependency. It is also possible that this might happen to you when performing a system upgrade to Fedora 25.

Fedora 25 hasn't been affected by this bug at all, and it was fixed in Fedora 23 and 24 since libhif-0.2.2-3. Current use of PackageKit (GNOME Software, Apper) should be safe. However, if you have ever used these tools in the past, you're strongly advised to fix your "user installed" database before you try to upgrade to Fedora 25:

  1. First, make sure your libhif package version is the same as described above or newer:
    rpm -q libhif

    If not, update it, and check again:

    sudo dnf --refresh update libhif
    Reboot after update.
  2. Then, mark all your current packages as "user installed" using this command:
    rpm -qa --qf '%{NAME}\n' | xargs sudo dnf mark install

Please note that this solution is slightly excessive, because you're going to end up with all your packages considered either system essential or user requested, and none of them is ever going to be removed as a no-longer-needed dependency. However, this is the only way how to be absolutely sure that you're not going to be affected by this issue, at a relatively small cost (some packages might stay on your disk unnecessarily). Power users can tweak this solution according to their needs.

Core system issues

Wayland issues

Wayland is the replacement for the legacy X11 display stack. Although development has been rapid and Wayland is usable in most situations, some bugs remain. Please see the following link to learn the details:

Please check the list for your issue before you file a new bug, although if you're not sure, filing a new bug is the right thing to do.

Wayland is currently enabled by default only in GNOME. If you want to disable it, select GNOME on Xorg as session type when logging in (you only see this screen if your user has a password defined):

Gdm-pick-x11.png


GNOME issues

Many apps crash when logging out of GNOME

link to this item - Bugzilla: #1366897

If you log out from GNOME and have some apps started, you might see a notification on your next login that those apps crashed (at the time of your last logout). The bug is being investigated. In the mean time, be sure to save your work and close apps sensitive to incorrect termination before you log out.


Installing a local RPM is not always possible with gnome-software

link to this item - Bugzilla: #1367780

If you click on a locally downloaded RPM, it opens up in gnome-software, but quite often its Install button might not do anything. If this happens, you can try to run

$ killall gnome-software

then start gnome-software manually (from terminal or app laucher) and then click on the RPM file again. That should work around the bug.


Plasma (KDE) issues

KDE Live image might not boot into graphics (a race condition)

link to this item - Bugzilla: #1370222

We have identified a (possibly rare) race condition that make KDE Live image not boot into the graphics session. Since it is a race condition, just repeating the boots might get you into a functional KDE session (or might not). If you encounter this, please tell us in RHBZ #1370222. A workaround is to switch to VT2 using Ctrl+Alt+F2, log in as root and restart sddm using:

# systemctl restart sddm

Live user switching doesn't seem to work well on KDE

link to this item - Bugzilla: #1382001

Live user switching doesn't currently seem to work well in KDE. The existing "workaround" is to log out from the current user account, if you want to switch to a different user account. (That of course is no longer live user switching).

Network issues

Hardware issues

Application issues

Display is flickering in GNOME Boxes

link to this item - Bugzilla: #1266484

If you try to boot Fedora 25 in GNOME Boxes, you'll see the display flicker every second. Also, GNOME overview will be canceled every time, which makes it really hard to run any applications. The easiest workaround seems to be using virt-manager instead.

ARM issues

Fedora Server issues

Fedora Cloud issues

Other issues

Hibernation doesn't work from a standard install

link to this item - Bugzilla: #1206936

The systemd-hibernate generator used to handle resume from hibernate functionality expects a resume=/path/to/swap in the kernel args. Anaconda does not add this into /etc/default/grub and the dracut cmdline generator doesn't act in a way the systemd hibernate generator can locate the swap with the resume image.

To work around this, check the devmapper path to the swap via swapon -s command and add it to the GRUB_CMDLINE_LINUX entry in /etc/default/grub, then regenerate the grub.cfg file used:

  • Via grub2-mkconfig:
    • For BIOS systems:
      sudo grub2-mkconfig -o /boot/grub2/grub.cfg
    • For EFI systems:
      sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
  • Via grubby:
    sudo grubby --args=resume=/path/to/swap --update-kernel=$(grubby --default-kernel)


Booting other UEFI Linux distributions might not work from Fedora bootloader

link to this item - Bugzilla: #1353026

Certain people who have multiple Linux distributions installed (in UEFI mode on GPT disks) report they're not able to boot non-Fedora systems from Fedora bootloader. If this happens to you, please tell us in RHBZ #1353026. The workaround should be to use your UEFI firmware to display a one-time boot menu (often displayed with F8, F10, F11, F12 or Esc) and pick the system you want to boot. That will boot the system directly, without going through Fedora bootloader. If this is not available for you, you can try to select the OS you want to boot in the Fedora bootloader, hit e to edit the boot menu, and replace linux and initrd keywords with linuxefi and initrdefi, then press Ctrl+x or F10 to boot it.