Common F29 bugs

Click here to set up this language box

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

Pre-release version
Fedora 29 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 29 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 F29 Beta release announcement for specific information about changes in Fedora 29 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

UEFI install in 'basic graphics mode' may fail to boot

link to this item - Bugzilla: #1628495

Several testers have reported that attempting to boot Fedora 29 installer images in native UEFI mode and using the Install Fedora 29 in basic graphics mode option from the Troubleshooting menu may fail to reach the graphical installer successfully.

So far, this bug has not been reported to affect any system which does not boot successfully using the regular boot option, so we suggest simply doing that instead. If you have a system which fails to boot either in "normal" or "basic" graphics mode, please report this to the bug.

Switching keyboard layout with key combo does not work in Wayland on Fedora Workstation Live image

link to this item - Bugzilla: #1389959

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 ⊞ Win+Space or Alt+⇧ Shift). 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).

no "install to hard drive" icon in soas, add to "get fedora" webpage to switch to sugar-terminal and enter "liveinst" to start installer

link to this item - Bugzilla: #1644388

Core system issues

Cron jobs in /etc/cron.d (including cron.hourly) do not run

link to this item - Bugzilla: #1625645 - Bugzilla: #1639381

Testing has shown that cron jobs in correct formats dropped into /etc/cron.d do not get run. This includes all scripts dropped into /etc/cron.hourly, as execution of those depends on a job in /etc/cron.d. This problem is due to SELinux blocking the operation.

To work around this problem until it is resolved, a comment on the bug report contains a suggested CIL-formatted policy that allows these jobs to run:

(allow unconfined_t system_cron_spool_t( file ( entrypoint)))

to use this, save that single line to a file with the extension .cil, e.g. crond.cil, and load it with semodule, e.g. sudo semodule -i crond.cil. After you do this, the jobs should execute successfully.

DNF operations performed with modular repositories offline are not aware of modules

link to this item - Bugzilla: #1616167

If you have any modules enabled on your Fedora 29 system, and you somehow perform a package management operation with the modular repositories disabled, any packages installed from the modules will be treated as if they were non-modular packages.

For instance, say you have a module enabled that provides version 2.0 of package foo, but the non-modular Fedora 29 repositories contain version 3.0 of the same package. Normally, when you run DNF, it will recognize that you are using the module, and not offer to upgrade to foo 3.0 from the non-modular repositories. If, however, you somehow run an update operation with the modular repositories disabled, DNF will incorrectly offer this "update".

It is not likely that you will run into this scenario in normal use of Fedora 29 Beta, but we do recommend you be careful with the use of the --disablerepo argument to DNF. It is also at least possible that you may hit it by temporarily enabling the updates-testing-modular repository to enable a new repository; until the module is present in the updates-modular repository, subsequent operations without the updates-testing-modular repository enabled may run into this issue, so, again, take care.

We are aiming to resolve at least the worst possible cases and consequences of this before Fedora 29 proper is released.

DNF doesn't resolve variables in mirrorlists

link to this item - Bugzilla: #1637148

When a yum/dnf repository uses a mirrorlist link, and the content of this link contains URLs with special dnf variables, such as $releasever or $basearch, DNF is unable to replace them with correct release values and fails to download metadata from those links.

Such behaviour did not happen in previous version of Fedora and there is no workaround for it. A fix has been submitted to solve it. When it is found helpful, this issues will be solved in one of the future updates.

System update fails when trying to remove rtkit-0.11-19.fc29

link to this item - Bugzilla: #1637496

This affects only Fedora 29 pre-release installations. If you have rtkit-0.11-19.fc29 in your system, an update to a later rtkit will fail, because the older version can't be removed. You can check what version of rtkit you have with this command:

$ rpm -q rtkit
rtkit-0.11-20.fc29.x86_64

If your base installation had at least rtkit-0.11-20.fc29, you should be fine. You can check whether you are affected by first fully updating your system, and then by running:

$ sudo dnf check
rtkit-0.11-19.fc29.x86_64 is a duplicate with rtkit-0.11-20.fc29.x86_64
Error: Check discovered 1 problem(s)

If you see a problem like the one above, you can force-remove the older rtkit by running:

$ sudo rpm -e --noscripts --allmatches rtkit-0.11-19.fc29.x86_64

and then verify:

$ sudo dnf check
$ 

Package management tools (dnf, GNOME Software etc.) can crash when more than one runs at once

link to this item - Bugzilla: #1631533

Note: We hope this problem has been fixed in the final Fedora 29 release and should no longer happen. In case you can still see it with a fully up-to-date system, see the description below and please provide your feedback in RHBZ #1631533.

The version of libdnf included in Fedora 29 introduces a database called 'swdb' which is intended to replace old, tool-specific databases like the yum/DNF history database, with the intention that all package management tools will share a common view of the transaction history and so on. However, it seems that multiple processes attempting to access this database simultaneously may not queue in an orderly fashion, or exit cleanly, but crash with an error message like Exec failed: database is locked. So far, this issue has been reproduced with one dnf process and one pkcon process, and also with two dnf processes.

To the best of our current knowledge, this problem cannot result in partially-completed transactions or inconsistent databases, as the process that crashes should not have actually made any changes to anything yet. However, as any crash in a package manager is undesirable and worrying, we are working to resolve this as soon as possible.

To "work around" it for now, simply retry the transaction that failed. Once the other transaction has completed, it should succeed. If the other process is one you ran yourself, it should be easy to identify, but it may be harder if it is an automatically-scheduled update or something along those lines.

DNF crashes on upgraded systems

link to this item - Bugzilla: #1600917

The dnf utility can crash when encountering history database created on previous release (F28, F27, etc.), which is common on system-upgraded installations.

Workaround for now is to remove /var/lib/dnf/history/ directory. Be aware that this will remove all entries from dnf history!

Workstation (GNOME) Issues

Download progress is often invisible if GNOME Software

link to this item - Bugzilla: #1643446

When you update your system with Gnome Software, sometimes the progress bar showing the percentage of downloaded packages is not correctly visible on the lower part of the Cancel button. This problem does not affect the functionality of the application and updating the system still works fine.

Note, that downloading the package set may take several minutes and the application may look unresponsive. If you see such behaviour, do not cancel the download process and wait until it is finished and you are offered to Reboot and Install.

Download button in GNOME Software performs the download, but then changes back to Download

link to this item - Bugzilla: #1643059

Some testers experienced a situation, when, during system update via Gnome Software, they pushed the Download button and after the packages were downloaded, the button returned to a Download button again and the application did not proceed to Reboot and Update button. As a consequence, the system could not be updated.

If you arrive in that situation, the workaround is log out and back in again, or reboot the machine. After that, the application shows the Reboot and update button and lets you update the system.

Refresh button in GNOME Software doesn't refresh the repos

link to this item - Bugzilla: #1643444

The Refresh button does not refresh the repository metadata in GNOME Software. A fix has already been submitted to upstream and once it is stable, the issue will be solved in a future update.

You don't need to work around this problem, because automatic refresh of repositories works fine, so you'll be offered updated packages regularly without issues. However, if you want to force GNOME Software to show you the latest updates immediately, execute this command:

$ pkcon refresh force

Previous update info is leaking into current update info in GNOME Software

link to this item - Bugzilla: #1642878

When you update packages with Gnome Software, some of the previously updated packages are still shown in the update queue. This problem does not affect the functionality of the application and updating packages still works fine.

If you happen to see such behaviour, you can safely ignore it.

GNOME may crash on switch back from virtual terminal under X.org with multiple displays

link to this item - Bugzilla: #1630367

Some testers have reported that GNOME may crash on a system with multiple displays, running GNOME under X.org (rather than Wayland), if the user switches to a VT (console) and then switches back again. So far this bug has been reported to affect Lenovo Thinkpad T460s, T470s and T480s laptops, and a desktop with a Radeon R7-based graphics card, with various display configurations.

If you are affected by a problem like this, the most obvious workaround is to run on Wayland instead of X.org, if you can. If you must use X.org, we can only advise that you avoid using virtual terminals until this can be investigated and resolved.

Switch user option missing from user menu until lock screen appears

link to this item - Bugzilla: #1576903

Update available for testing
A candidate fix for this issue 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: sudo dnf --enablerepo=updates-testing update --advisory=FEDORA-2018-646c51188f

Due to a bug, the Switch user option on the user menu (top-right menu, then expand the user name) in GNOME may be missing in any given session until the lock screen has appeared at least once. To work around this issue, you can trigger the lock screen manually.

Display gets messed up when routing panel is active in Gnome Maps

link to this item - Bugzilla: #1637751

On some systems, when planning a route, Gnome Maps failed to render correctly. The routing panel on the right side of the map opens, but its content is incorrectly displayed and hidden behind a white unresponsive panel. Trying to resize the panel can only help occasionally, and sometimes it might lead to even a worse situation.

As a workaround for this behaviour, you can use an Xorg session instead of a Wayland session. To do so, click on the settings wheel in the login screen and from the list of options, choose GNOME on Xorg. This bug will be fixed in one of the future updates.

Running applications can lose data on log out from GNOME

link to this item - Bugzilla: #1394937

If you log out from a GNOME session and have some GNOME applications running, these applications will not be terminated correctly which results in loss of data or settings, if those have not been saved before. In order to avoid any possible problems caused by this, you should definitely save any unsaved work and ideally close running applications manually before logging out.

There have been some less clear reports of applications not shutting down cleanly on log out from GNOME Xorg sessions, which is under discussion in bug #1394937, but we are not yet entirely sure about the details of that possible case.

Offline updates get stuck towards the end due to a libdnf crash when any multilib package is installed

link to this item - Bugzilla: #1642796

When you perform offline updates in GNOME (reboot to perform updates), the process might crash at the very end of the process, seemingly hanging on a screen showing 97% or more percent done. We believe this most commonly occurs if you have any multilib package installed - i.e. packages of the same name for different arches installed together. This will often be the case if you run wine or some popular 32-bit third-party games and applications. If you see the percentage at 97 or higher and it does not update for half an hour or longer, force reboot using Ctrl+Alt+Del, the system should not be negatively affected in any way. The DNF team is currently working on a fix for this issue.

Totem and Cheese fail on Wayland in virtual machines

link to this item - Bugzilla: #1467368

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.

Cheese fails to start in a similar fashion. Because VMs usually don't have a webcam, this doesn't limit users in any way.

Hardware issues

Bluetooth connection to some devices doesn't work out of the box

link to this item - Bugzilla: #1389347

On some machines, the bluez-obex service starts with erroneous settings which prevents bluetooth communication with other devices, such as mobile phones.

If you experience this problem, you can workaround it by running the following commands on the console:

sudo dnf install bluez-obexd
systemctl --user start obex
sudo systemctl --global enable obex

After that, the communication should be possible.

1Gb/s ethernet port is configured as 10Mb/s port on Thinkpad T480s

link to this item - Bugzilla: #1627816

With kernel version greater than 4.15.0, some testers have experienced a significant drop in ethernet speed after unplugging and plugging again the ethernet cable on Thinkpad T480s laptops. Originally, the were connected with a speed of 1Gb per second, which then dropped down to 10 Mb/s. Apparently, this only happen to affect the download speed and leaves the upload speed at its original value.

If you hit this problem, there are several ways to resolve this:

• restart your system with your cable already plugged in (don't plug it in when your system is running)
• run ethtool -r ETHNAME, where ETHNAME is the name of your ethernet device, possible to see e.g. in ip address output

iSCSI Reverse CHAP authentication not working

link to this item - Bugzilla: #1637927

In Fedora 29, the reverse (target) CHAP authentication does not work for either a discover or a login. The initiator authentication works without problems.

As a workaround, do not use reverse CHAP authentication for your iSCSI communication.

As soon as there will be a fix, this issue will be solved in future updates.

ARM & AArch64 Issues

Raspberry Pi config.txt is replaced during an upgrade from a previous release

link to this item

When upgrading from a previous release on the Raspberry Pi 2/3/3+ the config.txt is replaced in the update process. To ensure any user defined settings are saved, please create a backup before upgrading. After the upgrade you will also need to re-enable the UART in config.txt if you intend to use the serial console.

XFCE, LXQT and Astronomy Spins

Some Fedora Spins are missing from final Compose

link to this item

When building Fedora 29 final ISOs, some spins (XFCE, LXQT, Astronomy) have failed to build. This issue is being addressed by Fedora Release Engineering.