Menu Close

Administering the system using the GNOME desktop environment

Red Hat Enterprise Linux 9

Administering Red Hat Enterprise Linux 9 using the GNOME desktop environment

Red Hat Customer Content Services


This document describes how to perform selected system administration tasks using GNOME, which is the only available desktop environment in RHEL 9.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Providing feedback on Red Hat documentation

We appreciate your input on our documentation. Please let us know how we could make it better.

  • For simple comments on specific passages:

    1. Make sure you are viewing the documentation in the Multi-page HTML format. In addition, ensure you see the Feedback button in the upper right corner of the document.
    2. Use your mouse cursor to highlight the part of text that you want to comment on.
    3. Click the Add Feedback pop-up that appears below the highlighted text.
    4. Follow the displayed instructions.
  • For submitting feedback via Bugzilla, create a new ticket:

    1. Go to the Bugzilla website.
    2. As the Component, use Documentation.
    3. Fill in the Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation.
    4. Click Submit Bug.

Chapter 1. Installing software in GNOME

You can install applications and other software packages using several methods in GNOME.

1.1. Prerequisites

  • You have administrator permissions on the system.

1.2. The GNOME Software application

GNOME Software is an utility that enables you to install and update applications and software components in a graphical interface.

GNOME Software provides a catalog of graphical applications, which are the applications that include a *.desktop file. The available applications are grouped into multiple categories according to their purpose.

GNOME Software uses the PackageKit and Flatpak technologies as its back ends.

1.3. Installing an application using GNOME Software

This procedure installs a graphical application using the GNOME Software utility.


  1. Launch the GNOME Software application.
  2. Find the application that you want to install using any of the following methods:

    • Click the search button (🔍) in the upper-left corner of the window and type the name of the application.

      Application search in GNOME Software

    • Browse the application categories in the Explore tab.

      Explore screen in GNOME Software

  3. Click the selected application.
  4. Click Install.

    Install LibreOffice Writer

1.4. Installing an application to open a file type

This procedure installs an application that can open a given file type.


  • You can access a file of the required file type in your file system.


  1. Try opening a file that is associated with an application that is currently not installed on your system.
  2. GNOME automatically identifies the suitable application that can open the file, and offers to download the application.

1.5. Installing an RPM package file in GNOME

This procedure installs an RPM software package that you manually downloaded as a file.


  • You have downloaded the required RPM package.


  1. In the Files application, open the directory that stores the downloaded RPM package.


    By default, downloaded files are stored in the /home/user/Downloads/ directory.

  2. Double-click the RPM package file to install it.

1.6. Installing an application from the Activities Overview search

This procedure installs a graphical application from search results on the GNOME Activities Overview screen.


  1. Open the Activities Overview screen.
  2. Type the name of the required application in the search entry.

    LibreOffice Writer in the search results

    The search results display the application’s icon, name, and description.

  3. Click the application’s icon to open the Software application.

    LibreOffice Writer in Software

  4. Click Install to finish the installation in Software.


  • Click Open to launch the installed application.

1.7. Additional resources (or Next steps)

Chapter 2. Installing applications using Flatpak

You can install certain applications using the Flatpak package manager. The following sections describe how to search for, install, launch, and update Flatpak applications on the command line and in the graphical interface.


Red Hat provides Flatpak applications only as a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see

The Flatpak package manager itself is fully supported.

2.1. The Flatpak technology

Flatpak provides a sandbox environment for application building, deployment, distribution, and installation.

Applications that you launch using Flatpak have minimum access to the host system, which protects the system installation against third-party applications. Flatpak provides application stability regardless of the versions of libraries installed on the host system.

Flatpak applications are distributed from repositories called remotes. Red Hat provides a remote with RHEL applications. Additionally, third-party remotes are available as well. Red Hat does not support applications from third-party remotes.

2.2. Setting up Flatpak

This procedure installs the Flatpak package manager.


  • Install the flatpak package:

    # dnf install flatpak

2.3. Enabling the Red Hat Flatpak remote

This procedure configures the Red Hat Container Catalog as a Flatpak remote on your system.


  • You have an account on the Red Hat Customer Portal.


    For large-scale deployments where the users do not have Customer Portal accounts, Red Hat recommends using registry service accounts. For details, see Registry Service Accounts.


  1. Enable the rhel Flatpak remote:

    $ flatpak remote-add \
              --if-not-exists \
              rhel \
  2. Log into the Red Hat Container Catalog:

    $ podman login
    Username: your-user-name
    Password: your-password

    Provide the credentials to your Red Hat Customer Portal account or your registry service account tokens.

    By default, Podman saves the credentials only until you log out.

  3. Optional: Save your credentials permanently. Use one of the following options:

    • Save the credentials for the current user:

      $ cp $XDG_RUNTIME_DIR/containers/auth.json \
    • Save the credentials system-wide:

      # cp $XDG_RUNTIME_DIR/containers/auth.json \

      For best practices, Red Hat recommends that you log into the Red Hat Container Catalog using registry account tokens when installing credentials system-wide.


  • List the enabled Flatpak remotes:

    $ flatpak remotes
    Name    Options
    rhel    system,oci,no-gpg-verify

2.4. Searching for Flatpak applications

This procedure searches for an application in the enabled Flatpak remotes on the command line. The search uses the application name and description.


  • Flatpak is installed.
  • The Red Hat Flatpak repository is enabled.


  • Search for an application by name:

    $ flatpak search application-name

    For example, to search for the LibreOffice application, use:

    $ flatpak search LibreOffice

    The search results include the ID of the application:

    Application ID               Version  Branch  Remotes  Description
    org.libreoffice.LibreOffice           stable  rhel     The LibreOffice productivity suite

2.5. Installing Flatpak applications

This procedure installs a selected application from the enabled Flatpak remotes on the command line.


  • Flatpak is installed.
  • The Red Hat Flatpak remote is enabled.


  • Install an application from the rhel remote:

    $ flatpak install rhel application-id

    Replace application-id with the ID of the application. For example:

    $ flatpak install rhel org.libreoffice.LibreOffice

2.6. Launching Flatpak applications

This procedure launches an installed Flatpak application from the command line.


  • Flatpak is installed.
  • The selected Flatpak application is installed.


  • Launch the application:

    $ flatpak run application-id

    Replace application-id with the ID of the application. For example:

    $ flatpak run org.libreoffice.LibreOffice

2.7. Updating Flatpak applications

This procedure updates one or more installed Flatpak applications to the most recent version in the corresponding Flatpak remote.


  • Flatpak is installed.
  • A Flatpak remote is enabled.


  • Update one or more Flatpak applications:

    • To update a specific Flatpak application, specify the application ID:

      $ flatpak update application-id
    • To update all Flatpak applications, specify no application ID:

      $ flatpak update

2.8. Installing Flatpak applications in the graphical interface

This procedure searches for Flatpak applications using the Software application.


  • Flatpak is installed.
  • The Red Hat Flatpak remote is enabled.


  1. Open the Software application.
  2. Make sure that the Explore tab is active.
  3. Click the search button in the upper-left corner of the window.
  4. In the input box, type the name of the application that you want to install, such as LibreOffice.
  5. Select the correct application in the search results.

    If the application is listed several times, select the version where the Source field in the Details section reports

  6. Click the Install button.
  7. If Software asks you to log in, enter your Customer Portal credentials or your registry service account tokens.
  8. Wait for the installation process to complete.
  9. Optional: Click the Launch button to launch the application.

2.9. Updating Flatpak applications in the graphical interface

This procedure updates one or more installed Flatpak applications using the Software application.


  • Flatpak is installed.
  • A Flatpak remote is enabled.


  1. Open the Software application.
  2. Select the Updates tab.
  3. In the Application Updates section, you can find all available updates to Flatpak applications.
  4. Update one or more applications:

    • To apply all available updates, click the Update All button.
    • To update only a specific application, click the Update button next to the application item.
  5. Optional: Enable automatic application updates.

    1. Click the menu button in the upper-right corner of the window.
    2. Select Update Preferences.
    3. Enable Automatic Updates.

      Flatpak applications now update automatically.

Chapter 3. Displaying the system security classification

As an administrator of deployments where the user must be aware of the security classification of the system, you can create either a login screen heads-up banner or a classification banner.

3.1. Displaying the system security classification at login

You can now configure the GNOME Display Manager (GDM) login screen to display an overlay banner that contains a predefined message. This is useful for deployments where the user is required to read the security classification of the system before logging in.


  1. Install the gnome-shell-extension-heads-up-display package:

    # yum install gnome-shell-extension-heads-up-display
  2. Create the /etc/dconf/db/gdm.d/99-hud-message file with the following content:

    message-heading="Security classification title"
    message-body="Security classification description"

    Replace the following values with text that describes the security classification of your system:

    Security classification title
    A short heading that identifies the security classification.
    Security classification description
    A longer message that provides additional details, such as references to various guidelines.
  3. Update the dconf database:

    # dconf update
  4. Reboot the system.

3.2. Enabling system security classification banners

You can now create a classification banner to state the overall security classification level of the system. This is useful for deployments where the user must be aware of the security classification level of the system that they are logged into.

You can create a classification banner within the running session, the lock screen, and login screen, and customize its background color, its font, and its position within the screen.

This procedure creates a red banner with a white text placed on both the top and bottom of the login screen.


  1. Install gnome-shell-extension-classification-banner package.

    # yum install gnome-shell-extension-classification-banner
  2. Create the /etc/dconf/db/gdm.d/99-class-banner file with the following content:

    message='TOP SECRET'
  3. Update the dconf database:

    # dconf update
  4. Reboot the system.

Chapter 4. Setting a default desktop session for all users

You can configure a default desktop session that is preselected for all users that have not logged in yet.

If a user logs in using a different session than the default, their selection persists to their next login.


  1. Copy the configuration file template:

    # cp /usr/share/accountsservice/user-templates/standard \
  2. Edit the new /etc/accountsservice/user-templates/standard file. On the Session=gnome line, replace gnome with the session that you want to set as the default.
  3. Optional: To configure an exception to the default session for a certain user, follow these steps:

    1. Copy the template file to /var/lib/AccountsService/users/user-name:

      # cp /usr/share/accountsservice/user-templates/standard \
    2. In the new file, replace variables such as ${USER} and ${ID} with the user values.
    3. Edit the Session value.

Chapter 5. Setting up a printer

In GNOME, you can set up printing using the Settings application.

5.1. Accessing printer settings in GNOME


  1. Use one of the approaches described in Launching applications to start the Settings application.

    Moreover, you can also start the Settings application from the system menu in the top right corner by clicking on the "Settings" icon.

    system menu gcc 9
  2. When the the Settings application GUI appears, go to Printers.

    Figure 5.1. GNOME Control center configuration tool

    gnome control center add printer 9

5.2. Adding a new printer in Settings

This section describes how to add a new printer using the Settings application.


  • Click the Unlock button, which appears near the upper-right corner of the Printers screen, and authenticate as one of the following users:

    • Superuser
    • Any user with the administrative access provided by sudo (users listed within /etc/sudoers)
    • Any user belonging to the printadmin group in /etc/group


  1. Open the Printers dialog.

    gnome control center add printer 9
  2. Click on Unlock and authenticate.

    add printer gcc unlock authenticate 9
  3. Select one of the available printers (including also network printers), or enter printer IP address or the host name of a printer server.

    gnome control center select printer 9
    gnome control center add network printer 9
  4. Confirm your selection by clicking Add in the top right corner.

    gnome control center add network printer confirm 9

5.3. Printing a test page in Settings

This section describes how to print a test page to make sure that the printer functions properly.


  • A printer has been set up.


  1. Click the settings (⚙️) button on the right to display a settings menu for the selected printer:

    gnome control center printer settings 9
  2. Click Printing OptionsTest Page.

Chapter 6. Modifying printer settings

In GNOME, you can modify printer settings using the Settings application.


6.1. Displaying and modifying printer’s details

This section describes how to maintain a configuration of a printer using the Settings application.


  1. Click the settings (⚙️) button on the right to display a settings menu for the selected printer:

    gnome control center printer settings 9
  2. Click Printer Details to display and modify selected printer’s settings:

    gnome control center printer details 9

    In this menu, you can select the following actions:

    Search for Drivers
    GNOME Control Center communicates with PackageKit that searches for a suitable driver suitable in available repositories.
    Select from Database
    This option enables you to select a suitable driver from databases that have already been installed on the system.
    Install PPD File
    This option enables you to select from a list of available postscript printer description (PPD) files that can be used as a driver for your printer.
gnome control center printer details more 9

6.2. Setting the default printer

This section describes how to determine which printer should be used as default.


  1. Click the settings (⚙️) button on the right to display a settings menu for the selected printer:

    gnome control center printer settings 9
  2. Click Use Printer by Default to set the selected printer as the default printer:

    gnome control center default printer 9

6.3. Setting printing options


  1. Click the settings (⚙️) button on the right to display a settings menu for the selected printer:

    gnome control center printer settings 9
  2. Click Printing Options.

6.4. Removing a printer

This section describes how to remove a printer using the Settings application.


  1. Click the settings (⚙️) button on the right to display a settings menu for the selected printer:

    gnome control center printer settings 9
  2. Click Remove Printer to remove the selected printer:

    gnome control center remove printer 9

Chapter 7. Managing storage volumes in GNOME

This section describes how you can manage storage volumes in GNOME with a virtual file system. GNOME Virtual File System (GVFS) is an extension of the virtual file system interface provided by the libraries the GNOME desktop is built on.

7.1. The GVFS system

This section introduces GVFS and explains how GVFS works.

GVFS provides complete virtual file system infrastructure and handles storage in the GNOME desktop. It uses addresses for full identification based on the Uniform Resource Identifier (URI) standard, syntactically similar to URL addresses in web browsers. These addresses in the form of schema://user@server/path are the key information determining the kind of service.

GVFS helps to mount the resources. These mounts are shared between multiple applications. Resources are tracked globally within the running desktop session, which means that even if you quit an application that triggered the mount, the mount continues to be available for any other application. Multiple applications can access the mount at the same time unless it is limited by a back end. Some protocols by design permit only a single channel.

GVFS mounts removable media in the /run/media/ directory.

7.2. The format of the GVFS URI string

This section explains what the GVFS URI string is and demonstrates how to form one.

You must form a URI string to use back end services. This string is a basic identifier used in GVFS, which carries all necessary information needed for unique identification, such as type of service, back end ID, absolute path, or user name if required. You can see this information in the Files address bar and GTK+ open or save file dialog.

The following example is a very basic form of the URI string, which points to a root directory (/) of the File Transfer Protocol (FTP) server running at the domain:

Example 7.1. A URI string pointing to the root FTP directory

Example 7.2. A URI string pointing to a text file on FTP


7.3. Mounting a storage volume in GNOME

In virtual file systems, particular resources are set to be mounted automatically, but the most common way is to trigger mounts manually.


  1. Open the Files application.
  2. Click Other Locations in the side bar.
  3. Enter the URI string in the Connect to Server field.
  4. Press Connect.
  5. If the dialog asks you for login credentials, enter your name and password into the relevant entry boxes.
  6. When the mounting process finishes, you can start working with the storage volume.

7.4. Unmounting a storage volume in GNOME

You can unmount storage volumes or resources using the following procedure.


  1. Open the Files application.
  2. In the side bar, click the Unmount (⏏) icon next to the chosen mount.
  3. Wait until the mount disappears or notification about the safe removal appears.

7.5. Access to GVFS mounts in the file system

This section introduces FUSE, the main daemon for the GVFS virtual file system.

Applications built with the GIO library can access GVFS mounts. In addition, GVFS provides a FUSE daemon which exposes active GVFS mounts. Any application can access active GVFS mounts using the standard POSIX APIs as though mounts were regular file systems.

In certain applications, additional library dependency and new virtual file system (VFS) subsystem specifics might be unsuitable or too complicated. For such reasons and to boost compatibility, GVFS provides a File System in Userspace (FUSE) daemon, which exposes active mounts through its mount for standard Portable Operating System Interface (POSIX) access. This daemon transparently translates incoming requests to imitate a local file system for applications.


You might experience difficulties with certain combinations of applications and GVFS back ends.

The FUSE daemon starts automatically with the main gvfs daemon and mounts volumes either in the /run/user/UID/gvfs/ or ~/.gvfs/ directories as a fallback.

Manual browsing shows individual directories for each GVFS mount. The system passes the transformed path as an argument when you are opening documents from GVFS locations with non-native applications. Note that native GIO applications automatically translate this path back to a native URI.

7.6. Available GIO commands

GIO provides several commands that might be useful for scripting or testing.

Here is a set of POSIX commands counterparts as follows:


gio cat

Displays the content of a file.

gio mkdir

Creates a new directory.

gio rename

Renames a file.

gio mount

Provides access to various aspects of the gio mounting functionality.

gio set

Sets a file attribute on a file.

gio copy

Makes a copy of a file.

gio list

Lists directory contents.

gio move

Moves a file from one location to another.

gio remove

Removes a file.

gio trash

Sends files or directories to the Trashcan. This can be a different folder depending on where the file is located, and not all file systems support this concept. In the common case that the file lives inside a user’s home directory, the trash folder is $XDG_DATA_HOME/Trash.

gio info

Displays information of the given locations.

gio save

Reads from standard input and saves the data to the given location.

gio tree

Lists the contents of the given locations recursively, in a tree-like format. If no location is given, it defaults to the current directory.

Following additional commands provide more control of GIO specifics:


gio monitor

Monitors files or directories for changes, such as creation, deletion, content and attribute changes, and mount and unmount operations affecting the monitored locations.

gio mime

Lists the registered and recommended applications for the mimetype if no handler is given, else, it is set as the default handler for the mimetype.

gio open

Opens files with the default application that is registered to handle files of this type.


For user convenience, bash completion is provided as a part of the package.

All these commands are native GIO clients, there is no need for the fallback FUSE daemon to be running. Their purpose is not to be drop-in replacements for POSIX commands, in fact, a very little range of switches is supported. In their basic form, these commands take an URI string as an argument instead of a local path.

Additional resources

  • The gio(1) man page.

7.7. Sample GIO commands

The following section provides a few examples of the GIO commands usage.

Example 7.3. List all files in the local /tmp directory

$ gio list file:///tmp

Example 7.4. List the content of a text file from a remote system

$ gio cat ssh://

Example 7.5. Copy the previous text file to a local /tmp directory

$ gio copy ssh:// /tmp/

Additional resources

  • The gio man page.

7.8. Overview of GVFS metadata

This section provides information on the GVFS metadata and provides instruction on how to view and manipulate them.

The GVFS metadata storage is implemented as a set of key-and-value pairs that bind information to a particular file. Thus, there is a tool for a user or application to save small data designed for runtime information such as icon position, last-played location, position in a document, emblems, notes, and so on.

Whenever you move a file or directory, GVFS moves the metadata accordingly so that metadata stays connected to the respective file. The GVFS stores all metadata privately, so metadata is available only on the machine. However, GVFS tracks mounts and removable media as well.


GVFS mounts removable media in the /run/media/ directory.

To view and manipulate with metadata, you can use:

  • the gio info command,
  • the gio set command, or
  • any other native GIO way of working with attributes.

Additional resources

  • The gio man page.

7.9. Setting custom GIO metadata attribute

This procedure describes how to set a custom metadata attribute.

Notice the differences between particular gio info calls and data persistence after a move or rename. Note the gio info command output.


  1. Create an empty file:

    $ touch /tmp/myfile
  2. View the metadata of this file:

    $ gio info -a 'metadata::*' /tmp/myfile
    uri: file:///tmp/myfile
  3. Set a string to this file:

    $ gio set -t string /tmp/myfile 'metadata::mynote' 'Please remember to delete this file!'
  4. View the metadata:

    $ gio info -a 'metadata::*' /tmp/myfile
    uri: file:///tmp/myfile
      metadata::mynote: Please remember to delete this file!
  5. Move this file to a new location:

    $ gio move /tmp/myfile /tmp/newfile
  6. View the metadata:

    $ gio info -a 'metadata::*' /tmp/newfile
    uri: file:///tmp/newfile
      metadata::mynote: Please remember to delete this file!

The metadata persists when you move the file using the GIO API.

Additional resources

  • The gio man page.

7.10. Password management of GVFS mounts

This section focuses on the GVFS mount authentication.

A typical GVFS mount authenticates on its activation unless the resource allows anonymous authentication or does not require any authentication at all.

In a standard GTK+ dialog, you can choose whether to store the password.

When you select the persistent storage, the password is stored in the user keyring. GNOME Keyring is a central place for secrets storage. The password is encrypted and automatically unlocked on desktop session start using the password provided on login. For protecting it by a different password, you can set the password at the first use.

The Passwords and Keys application helps to manage the stored password and GNOME Keyring. It allows removing individual records or changing passwords.

7.11. GVFS back ends

Back ends in GVFS provide access to a specific type of resource. This section provides a list of available GVFS back ends and their specifications.


Some back ends are packaged separately and not installed by default. For installing additional back ends, use the dnf package manager.

Table 7.1. Available back ends

Back endDescription


Provides administrator access to the local file system.


A virtual back end that burning applications use as a temporary storage for new CD, DVD, or BD medium content.


Exposes Audio CD through separate Waveform Audio File Format (WAV) files.


A virtual back end consolidating active mounts and physical volumes. Acts similarly to a signpost. Previously used by Files for its Computer view.

dav, davs

A WebDAV client, including secure variant. Authentication is possible only during mount. The back end does not support later re-authentication on per-folder basis.


DNS Service Discovery: An Avahi client, used during network browsing, forms persistent URIs to discovered services.


A fully featured File Transfer Protocol (FTP) client. Supports passive transfers by default. Also, handles secure mode over ftps (explicit mode) and ftpis (implicit mode) schemes.


A Picture Transfer Protocol (PTP) client to access your camera attached by USB or FireWire.


Provides access to Google Drive. The Google Drive account needs to be configured in the Online Accounts settings.


Handles all HTTP requests. Useful for easy downloading files from web in client applications.


A simple testing back end that proxies the file:// URI. The back end supports error injection.


A Media Transfer Protocol (MTP) back end for accessing media player and smart phone memory.


Allows you to browse Window Network and show shares discovered over Avahi.


A back end used in the file chooser dialog to list recent files used by GNOME applications.


A fully-featured SSH File Transfer Protocol (SFTP) client.


Accesses Samba and Windows shares.


A trash back end that allows to restore deleted files.

Chapter 8. Troubleshooting volume management in GNOME

Following are some common errors of volume management in GNOME and ways to resolve them.

8.1. Troubleshooting access to GVFS locations from non-GIO clients

If you have problems accessing GVFS locations from your application, it might mean that it is not native GIO client. Native GIO clients are typically all GNOME applications using GNOME libraries (glib, gio). The gvfs-fuse service is provided as a fallback for non-GIO clients.


  • The gvfs-fuse package is installed.

    $ dnf install gvfs-fuse


  1. Ensure that gvfs-fuse is running.

    $ ps ax | grep gvfsd-fuse

    If gvfs-fuse is not running, log out and log back in. Red Hat does not recommend starting gvfs-fuse manually.

  2. Find the system user ID (UID) for the /run/user/UID/gvfs/ path.

    The gvfsd-fuse daemon requires a path where it can expose its services. When the /run/user/UID/gvfs/ path is unavailable, gvfsd-fuse uses the ~/.gvfs path.

    $ id -u
  3. If gvfsd-fuse is still not running, start the gvfsd-fuse daemon:

    $ /usr/libexec/gvfsd-fuse -f /run/user/_UID_/gvfs

    Now, the FUSE mount is available, and you can manually browse for the path in your application.

  4. Find the GVFS mounts under the /run/user/UID/gvfs/ or ~/.gvfs locations.

8.2. Troubleshooting an invisible connected USB disk

Under certain circumstances, when you connect a flash drive, the GNOME Desktop might not display it. If your flash drive is not visible in Files, but you can see it in the Disks application, you can attempt to set the Show in user interface option in Disks.


  1. Open the Disks application.
  2. Select the disk in the side bar.
  3. Below Volumes, Click Additional partition options (⚙)Edit Mount Options…​.
  4. Click Show in user interface.
  5. Confirm by clicking OK.
  6. If the flash drive is still not visible, you can try to physically remove the drive and try connecting it again.

8.3. Troubleshooting unknown or unwanted partitions listed in Files

Sometimes, you might see unknown or unwanted partitions when you plug a disk in. For example, when you plug in a flash disk, it is automatically mounted and its volumes are shown in the Files side bar. Some devices have a special partition with backups or help files, which you might not want to see each time you plug in the device.


  1. Open the Disks application.
  2. Select the disk in the side bar.
  3. Below Volumes, Click Additional partition options (⚙)Edit Mount Options…​.
  4. Uncheck Show in user interface.
  5. Confirm by clicking OK.

8.4. Troubleshooting if a connection to the remote GVFS file system is unavailable

There are number of situations in which the client is unexpectedly and unwillingly disconnected from a virtual file system or a remote disk mount and is not reconnected automatically.

You might see the error messages in such situations. Several causes trigger such situations:

  • The connection is interrupted. For example, your laptop is disconnected from the Wi-Fi.
  • The user is inactive for some time and is disconnected by the server (idle timeout).
  • The computer is resumed from sleep mode.


  1. Unmount file system.
  2. Mount it again.
  3. If the connection is getting disabled more often, check the settings in the Network panel in the GNOME Settings.

8.5. Troubleshooting a busy disk in GNOME

If you receive a notification about your disk being busy, determine the programs that are accessing the disk. Then, you can end the programs that are running. You can also use the System Monitor application to kill the programs forcefully.


  • The iotop utility is installed:

    # dnf install iotop


  1. Examine the list of open files.

    • Run the lsof command to get the list of open files.
    • If lsof is not available, run the ps ax command.
    • You can use System Monitor to display the running processes in a GUI.
  2. When you have determined the programs, terminate them using any of the following methods:

    • On the command line, execute the kill command.
    • In System Monitor, right-click the line with the program process name, and click End or Kill from the context menu.

Additional resources

  • The kill man page.

Legal Notice

Copyright © 2022 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.