(how to install f28 beta1.3cinnamon)
(add 1561816 (unexpected behaviour when installing multiple modules at once))
|Line 44:||Line 44:|
== Core system issues ==
== Core system issues ==
== GNOME issues ==
== GNOME issues ==
Revision as of 21:23, 4 April 2018
This page documents common bugs in Fedora 28 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.
- 1 Release Notes
- 2 My bug is not listed
- 3 Installation issues
- 4 Upgrade issues
- 5 Core system issues
- 6 GNOME issues
- 6.1 Wayland issues
- 6.2 Autosuspend kicks in unexpectedly in GNOME
- 6.3 System automatically suspends after 20 minutes when in GDM, even when autosuspend is disabled
- 6.4 Totem fails to play media on Wayland in virtual machines
- 6.5 Scroll events are not sent into virtual machines from touchpad/trackpoint under Wayland
- 6.6 Content of VPN entry in GNOME status menu sometimes does not appear
- 7 Plasma (KDE) issues
- 8 Network issues
- 9 Hardware issues
- 10 Application issues
- 11 ARM issues
- 12 Fedora Server issues
- 13 Fedora Cloud issues
- 14 Fedora Atomic issues
- 15 Cinnamon in QEMU/KVM
- 16 Soas issues
- 17 Other issues
Read the F28_Beta_release_announcement for specific information about changes in Fedora 28 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
- 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)
Switching keyboard layout with key combo does not work in Wayland
If you're running Workstation Live install media and configure multiple languages in the installer, you won't be able to switch between them using the standard system shortcut (typically+ or + ). However, you can still click on the language indicator in the installer with the mouse and that will switch the languages.
This does not affect other install media (KDE Live, DVD and netinst images).
Keyboard layout selected during installation of Fedora Workstation Live is not applied to the installed system
If you select a different keyboard layout during installation of Fedora Workstation Live image, the installed system will still use default English layout. A workaround is to install from a netinst image, or configure the layout once again in the installed system.
Installer on several live images does not offer iSCSI support
On many or all Fedora Live images, the installer will not offer iSCSI functionality (the "Add iSCSI target" button will not appear in the 'Specialized & Network Disks' screen). You can avoid the problem by running
sudo dnf install udisks2-iscsi from a console before starting the install process, or by installing from a dedicated installer image rather than a live image.
Upgrade from Fedora 26 might fail due to rich dependencies
When you upgrade from Fedora 26 to Fedora 27 or 28, the transaction might get aborted immediately due to target packages having rich dependencies. The list of such packages as of Mar 2018 is available in bug 1552547. Eventually, the intended solution is to send updated dnf+rpm into Fedora 26 to handle this transaction properly. In the meantime, the easiest workaround is to remove affected packages before doing the upgrade, and install them back in the upgraded system.
GRUB update might fail if /boot is on XFS
If you use XFS filesystem on
/boot and upgrade your system, you might end up in a GRUB minimal prompt (just a command prompt, no kernel to choose from interactively) after the upgrade is complete. The problem is in the system rebooting while XFS is in dirty state and not all changes being saved to the filesystem yet.
In order to prevent this issue, you might try to disable plymouth (by removing
rhgb kernel boot option) during the upgrade or uninstall it prior the upgrade (these workarounds were not tested).
If this already occurred to you, you should be able to fix the problem by booting a Live or rescue image, mounting the filesystem in question (which should replay the journal), perhaps running
xfs_repair to make sure there are no more issues. In the worst case, you'll also need to fully re-install grub.
Core system issues
Installing more than one module in the same transaction does not work correctly
When using the new Add-on Modularity function in Fedora 28, if you try to install more than one module in the same transaction - e.g. by running
dnf module install nodejs:9/default reviewboard:2.5/server - this will not work as expected. Only the last-named module will be installed immediately, but the other module(s) will be installed on the next
dnf update. This can be worked around by only installing one module per transaction.
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):
Autosuspend kicks in unexpectedly in GNOME
GNOME 3.28 now automatically suspends the system after 20 minutes of user inactivity. However, this idleness timer is currently broken and if some application suppresses suspend and then releases it, the timer doesn't reset, and instead suspends your system immediately. This is most frequently visible when watching a movie in a movie player or a web browser - if you watch a video longer than the configured autosuspend timeout (20 minutes by default) and not perform any keyboard/mouse actions in the meantime, the system will autosuspend immediately after the movie ends, without giving you any option to prevent that.
The easiest workaround is to disable autosuspend in GNOME settings.
System automatically suspends after 20 minutes when in GDM, even when autosuspend is disabled
GNOME 3.28 now automatically suspends the system after 20 minutes of user inactivity. Even if you disable/adjust this functionality in GNOME Settings, it only applies to your particular user session only, and does not affect the default system behavior, which is used when the local screen shows a GDM screen. This will affect you e.g. when you log out or switch between users, when you just start the machine without logging in and access it remotely (file sharing, ssh), etc. With some desktop environments, like Fluxbox, your system will also immediately suspend when you log out.
You can disable (or configure) auto-suspend system-wide by creating a file
/etc/dconf/db/local.d/00-autosuspend with this or similar contents:
[org/gnome/settings-daemon/plugins/power] # Do not autosuspend sleep-inactive-ac-type='nothing' sleep-inactive-battery-type='nothing'
sudo dconf update
Totem fails to play media on Wayland in virtual machines
Totem (Videos) will fail to play media when using a Wayland session in virtual machines (applies to default libvirt VMs, but not VirtualBox). The audio will play, but neither video nor a totem window will appear. If you need to play media in this environment, please either use X11 session, or a different media player.
Scroll events are not sent into virtual machines from touchpad/trackpoint under Wayland
Under Wayland, sending scroll events into a virtual machine works well when using the mouse, but doesn't work when using touchpad or trackpoint. As a workaround, switch to Xorg session on your host.
Some users have reported that, sometimes, the icon and text of the VPN entry in the GNOME status menu (the one that appears when you click the top-right of the screen) does not appear. Usually it will show a lock icon and the text 'VPN Off' (or information on any active VPN connection), but it appears that occasionally the icon and text do not appear; the menu just appears to contain an entirely empty row. The entry does function as intended.
No fix for this issue is yet known, but it has no functional impact - you can still use the 'empty' menu item.
Plasma (KDE) issues
Fedora Server issues
Fedora Cloud issues
Fedora Atomic issues
Cinnamon in QEMU/KVM
Cinnamon Beta 1.3 live.iso only runs openbox
How to install:
- liveuser login (no password)
- openbox-terminal (right click on blank screen for menu)
- su liveinst
- after install reboot in terminal
- su dnf update (349)
- reboot to cinnamon (defaults to fallback mode cinnamon)
Red Hat Bugzilla – Bug 1519042 soas starts in journal: This can be confusing for users
Fix by hitting f1 key then f3 key to get to main menu
Hibernation doesn't work from a standard install
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
- For BIOS systems:
- Via grubby:
sudo grubby --args=resume=/path/to/swap --update-kernel=$(grubby --default-kernel)