How to Install and Uninstall gdm.i686 Package on Fedora 39
Last updated: November 25,2024
1. Install "gdm.i686" package
Please follow the steps below to install gdm.i686 on Fedora 39
$
sudo dnf update
Copied
$
sudo dnf install
gdm.i686
Copied
2. Uninstall "gdm.i686" package
This guide covers the steps necessary to uninstall gdm.i686 on Fedora 39:
$
sudo dnf remove
gdm.i686
Copied
$
sudo dnf autoremove
Copied
3. Information about the gdm.i686 package on Fedora 39
Last metadata expiration check: 1:37:09 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : gdm
Epoch : 1
Version : 45.0.1
Release : 4.fc39
Architecture : i686
Size : 945 k
Source : gdm-45.0.1-4.fc39.src.rpm
Repository : fedora
Summary : The GNOME Display Manager
URL : https://wiki.gnome.org/Projects/GDM
License : GPL-2.0-or-later
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 : 45.0.1
Release : 4.fc39
Architecture : i686
Size : 945 k
Source : gdm-45.0.1-4.fc39.src.rpm
Repository : fedora
Summary : The GNOME Display Manager
URL : https://wiki.gnome.org/Projects/GDM
License : GPL-2.0-or-later
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.