Chapter 56. Desktop

Updating totem alone fails

Explicit dependency between the totem and gstreamer1-plugins-bad-free packages is missing. Consequently, when trying to update just the totem package, the operation fails. To work around this problem, do not update the totem package by itself and rely on the system update instead. (BZ#1451211)

The operating system always assumes Wacom Expresskeys Remote mode 1 when booting

The Wacom Expresskeys Remote (EKR) is a standalone device and thus can be switched to any operating mode when the operating system (OS) boots. Currently, however, the OS always assumes that the EKR is set to mode 1 upon boot. Consequently, the EKR is not synchronized with the OS when the EKR mode was not set to 1 prior to system boot. To work around this problem, set the EKR to mode 1 before starting the OS. (BZ#1458351)

Cannot install downloaded RPM files from Nautilus

When an RPM file is double clicked in the Nautilus file manger, the following error is returned instead of the file being installed:
Sorry, this did not work, File is not supported
This happens because the yum backend to PackageKit does not support getting details about local files.
This problem can be worked around by either installing gnome-packagekit to handle the double-click action or by manually installing the files using yum. (BZ#1434477)

Yelp does not correctly display HTML formatted files

In earlier versions of yelp, HTML formatted files could be displayed. With version 3.22, this functionality no longer works, returning an Unknown Error with the qualifying text URL cannot be shown.
There is no workaround at this time, as the problem may be related to architectural changes in yelp itself.
System administrators should note that yelp does not support this use case and expects Mallard or Docbook data as input.
Alternative methods for displaying HTML formatted content should be considered. (BZ#1443179)

Automatic modesetting fails when attaching monitors with some AMD hardware

With some configurations, adding an additional monitor to a system using AMD hardware can fail to activate the new hardware automatically.
The problem is currently under investigation.
To workaround the issue, system administrators should manually call xrandr(1) to enable the monitor. (BZ#1393951)

Gnome Documents can not display some documents when installed without LibreOffice due to a missing dependency

Gnome Documents uses libraries provided by the LibreOffice suite for rendering certain types of documents, such as OpenDocument Text or Open Office XML formats. However, the required libraries (libreoffice-filters) are missing from the dependency list of the gnome-documents package. Therefore, if you install Gnome Documents on a system that does not have LibreOffice, the aforementioned document types can not be rendered.
To work around this problem, install libreoffice-filters package manually, even if you do not plan to use LibreOffice itself. (BZ#1466164)

Application Installer displays packages even though they can not be installed on big endian architectures

When you use the Application Installer graphical package installer (the gnome-software package) on a big-endian system such as IBM Power Systems or IBM z Systems, some of the packages listed as available will not be possible to install, and an attempt to do so results in an installing not available error message. This is a known issue caused by package metadata currently being generated only for 64-bit AMD and Intel-compatible (little-endian) systems, and assuming all packages are also available on big-endian architectures, which is not the case.
There is no workaround to this problem; however, the error message has no consequences other than the package not being installable. (BZ#1464139)

The Add/Remove Software tool (gpk-application) does not use a newly imported key on the first try

When using the Add/Remove Software graphical interface in GNOME to install a package signed by a key that was not already imported, the tool displays a prompt allowing you to import the key. However, even if the key is imported, the installation is still unsuccessful due to a bug that prevents using the key immediately. To work around the problem, install the same package again; at that point the key is already imported from the previous attempt, and the installation succeeds. (BZ#1387181)

Resizing a display of a virtual machine with multiple displays using multiple PCI devices causes X to crash

A bug in the QXL driver (xorg-x11-drv-qxl) causes the X.Org display server on a virtual machine to crash upon display resize if the virtual machine has multiple displays configured to use multiple PCI devices. Make sure guest virtual machines running Red Hat Enterprise Linux with multiple monitors are configured to use a single PCI device. In Red Hat Virtualization, this setting is controlled by the Single PCI Device check box under Edit -> Console, and is enabled by default. (BZ#1428340)

Nautilus does not hide icons in the GNOME Classic Session

The GNOME Tweak Tool to show or hide icons in the gnome session, where the icons are hidden by default, is ignored in the GNOME Classic Session. As a result, it is not possible to hide icons in the GNOME Classic Session even though the GNOME Tweak Tool displays this option. (BZ#1474852)

Incorrect dependency in flatpak

Due to a wrong dependency in the flatpak package, the user can encounter the following error:
flatpak: error while loading shared libraries: libostree-1.so.1: cannot open shared object file: No such file or directory
To work around this problem, install the flatpak-libs package. Alternatively, instead of initially installing just flatpak, install both of the packages by running:
sudo yum -y install flatpak flatpak-libs
(BZ#1476905)

Firefox does not start after update

After the upgrade to firefox-52.1.2-.el7.x86_64 and further, the browser does not start in some cases. This is due to the nspr and nss packages not being updated from the Red Hat Enterprise Linux 7.4 batch. To work around this problem, update the nspr and nss packages from Red Hat Enterprise 7.4 release. Another possible workaround is to downgrade Firefox, but this option is not recommended. As a result, it is possible to start the Firefox web browser again. (BZ#1455798)

Limited support for visuals in Xorg

In the Xorg server, only TrueColor and DirectColor visuals at depth 16 or higher are supported for hardware drivers. Legacy applications that need a PseudoColor visual can be run against the Xephyr nested X server, which implements PseudoColor translation when displayed on a TrueColor screen. (BZ#1185690)