How to Install and Uninstall gdm.i686 Package on CentOS 8 / RHEL 8
Last updated: November 16,2024
1. Install "gdm.i686" package
Please follow the steps below to install gdm.i686 on CentOS 8 / RHEL 8
$
sudo dnf update
Copied
$
sudo dnf install
gdm.i686
Copied
2. Uninstall "gdm.i686" package
Please follow the step by step instructions below to uninstall gdm.i686 on CentOS 8 / RHEL 8:
$
sudo dnf remove
gdm.i686
Copied
$
sudo dnf autoremove
Copied
3. Information about the gdm.i686 package on CentOS 8 / RHEL 8
Last metadata expiration check: 1 day, 4:31:14 ago on Sun May 9 13:03:46 2021.
Available Packages
Name : gdm
Epoch : 1
Version : 3.28.3
Release : 34.el8
Architecture : i686
Size : 564 k
Source : gdm-3.28.3-34.el8.src.rpm
Repository : appstream
Summary : The GNOME Display Manager
URL : https://wiki.gnome.org/Projects/GDM
License : GPLv2+
Description : GDM, the GNOME Display Manager, handles authentication-related backend
: functionality for logging in a user and unlocking the user's session after
: it's been locked. GDM also provides functionality for initiating user-switching,
: so more than one user can be logged in at the same time. It handles
: graphical session registration with the system for both local and remote
: sessions (in the latter case, via the XDMCP protocol). In cases where the
: session doesn't provide it's own display server, GDM can start the display
: server on behalf of the session.
Available Packages
Name : gdm
Epoch : 1
Version : 3.28.3
Release : 34.el8
Architecture : i686
Size : 564 k
Source : gdm-3.28.3-34.el8.src.rpm
Repository : appstream
Summary : The GNOME Display Manager
URL : https://wiki.gnome.org/Projects/GDM
License : GPLv2+
Description : GDM, the GNOME Display Manager, handles authentication-related backend
: functionality for logging in a user and unlocking the user's session after
: it's been locked. GDM also provides functionality for initiating user-switching,
: so more than one user can be logged in at the same time. It handles
: graphical session registration with the system for both local and remote
: sessions (in the latter case, via the XDMCP protocol). In cases where the
: session doesn't provide it's own display server, GDM can start the display
: server on behalf of the session.