Adding KDE Plasma to an existing Fedora system is no longer the old groupinstall workflow. Current Fedora releases expose Plasma as the kde-desktop-environment DNF5 environment, with Fedora KDE Plasma Desktop 44 using Plasma 6.6 packages and the newer Plasma Login Manager instead of the older SDDM-first setup. The current environment path installs KDE Plasma on Fedora while letting you keep or change the display manager deliberately and add the optional X11 session only when you need it.
For a clean KDE-first install, download Fedora KDE Plasma Desktop instead of converting an existing Fedora Workstation install. The official KDE edition ships with Plasma selected from the start, while the DNF method applies to systems that already run Fedora with another desktop.
This workflow targets DNF-managed Fedora Workstation or a comparable mutable Fedora desktop. Fedora Kinoite and other Atomic desktops use rpm-ostree workflows instead of the DNF environment commands used here.
Install KDE Plasma on Fedora
Update Fedora Packages First
Refresh Fedora metadata and apply pending package updates before adding a second desktop environment. This reduces the chance of mixing old libraries with the current Plasma transaction.
sudo dnf upgrade --refresh
These commands use sudo for system package changes. If your account cannot run sudo on Fedora, add the user to the Fedora wheel group for administrator access before continuing.
Check the KDE Plasma Environment ID
Fedora 44 lists KDE Plasma as a DNF environment named kde-desktop-environment. Check the environment before installing so you can see the package groups Fedora will add.
dnf environment list --available | grep -i kde
dnf environment info kde-desktop-environment
On Fedora 44, the environment details should identify KDE Plasma Workspaces and show the full desktop environment pulling in the KDE group alongside the base graphical, hardware, fonts, input, multimedia, networking, printing, and standard Fedora groups:
Id : kde-desktop-environment
Name : KDE Plasma Workspaces
Required groups : admin-tools
: base-graphical
: core
: desktop-accessibility
: dial-up
: fonts
: guest-desktop-agents
: hardware-support
: input-methods
: kde-desktop
: multimedia
: networkmanager-submodules
: printing
: standard
Default groups : firefox
: kde-apps
: kde-media
: kde-pim
: libreoffice
The underlying KDE group ID is kde-desktop, but the environment install is the fuller desktop path. DNF5 removed legacy aliases such as groupinstall and groupremove; use the current dnf environment or dnf group subcommands instead. For command details, see the DNF5 group commands on Fedora reference.
Install the KDE Plasma Environment
Install the complete KDE Plasma environment with DNF5. Review the transaction before accepting it because the environment is large and includes desktop applications, media support, printing, accessibility, and other graphical components.
sudo dnf environment install kde-desktop-environment
On a Fedora 44 Workstation system, DNF transaction planning for this environment can approach a 2 GiB download and about 3 GiB of additional installed data, depending on what is already present. Let DNF finish the transaction before logging out or rebooting.
Verify Core KDE Packages
After installation, confirm the core Plasma packages and Fedora KDE login components are installed:
rpm -q plasma-desktop plasma-workspace plasma-login-manager kcm-plasmalogin
The command should print installed package version lines. If any package reports as not installed, rerun the environment install command and review the DNF output for skipped packages or dependency conflicts.
Optionally Install the Plasma X11 Session
Fedora’s current Plasma environment installs the Wayland session through plasma-workspace. Install the separate X11 session package only if you need an Xorg fallback for older applications, remote desktop tools, or graphics-driver troubleshooting.
sudo dnf install plasma-workspace-x11
This package provides the startplasma-x11 launcher and the /usr/share/xsessions/plasmax11.desktop login-session entry. If you do not need X11, leave this package uninstalled and use the default Plasma Wayland session.
Log In to KDE Plasma on Fedora
After the DNF transaction finishes, log out or reboot. Existing Fedora Workstation installs normally keep GDM as the active display manager unless you change it, and GDM can still launch Plasma from the session selector.
sudo reboot
At the login screen, select your user, open the session selector, and choose Plasma. Select Plasma (Wayland) for the normal Fedora KDE session. If you installed plasma-workspace-x11, Plasma (X11) should also appear as a fallback option.

Optionally Switch to Plasma Login Manager
Switching display managers is optional. Fedora KDE Plasma Desktop 44 uses Plasma Login Manager for fresh KDE installs, but an existing Workstation system can keep GDM and still run Plasma sessions.
Check the active display manager before changing it:
systemctl status display-manager --no-pager
Changing the display manager affects graphical login. Keep another administrator session or a TTY available so you can switch back if the new login screen does not start correctly.
To use Plasma Login Manager after installing the KDE environment, enable its service with --force because display managers share the display-manager.service alias:
sudo systemctl enable --force plasmalogin.service
sudo reboot
To return Fedora Workstation to GDM later, enable GDM again and reboot:
sudo systemctl enable --force gdm.service
sudo reboot
Verify the Active Plasma Session
After logging in to Plasma, open Konsole from the application launcher and check the running Plasma version and display server type:
plasmashell --version
printf '%s\n' "$XDG_SESSION_TYPE"
The first command prints the installed Plasma shell version. The second command prints wayland for a Wayland session or x11 for the optional X11 session.

Manage KDE Plasma on Fedora
Update KDE Plasma Packages
KDE Plasma packages update through Fedora’s normal DNF workflow. Regular system updates refresh Plasma, KDE applications, the login manager, and related desktop libraries from the enabled Fedora repositories.
sudo dnf upgrade --refresh
For unattended package checks or scheduled update notifications, configure DNF Automatic on Fedora separately.
Remove KDE Plasma from Fedora
Before removing Plasma, log out of the Plasma session and choose another working desktop such as GNOME. If you switched to Plasma Login Manager and want to return to Fedora Workstation’s default login manager, re-enable GDM before removing the KDE environment.
sudo systemctl enable --force gdm.service
sudo reboot
Remove the KDE environment with the same DNF5 environment ID used for installation:
sudo dnf environment remove kde-desktop-environment
If you installed the optional X11 session separately and it remains installed, remove it as well:
sudo dnf remove plasma-workspace-x11
Review unused dependency cleanup rather than running it blindly. DNF may identify packages that are no longer required, but the list can include libraries or tools used by another desktop or application.
sudo dnf autoremove
Package removal does not delete your personal Plasma settings. Back up or review user configuration under
~/.config,~/.local/share, and~/.cachebefore deleting any profile data by hand.
Troubleshoot KDE Plasma on Fedora
DNF Reports groupinstall as an Unknown Argument
Older Fedora examples often used dnf groupinstall "KDE Plasma Workspaces" or dnf groupinstall "KDE". Current DNF5 rejects those aliases:
Unknown argument "groupinstall" for command "dnf5".
Use the DNF5 environment command for the full KDE desktop install:
sudo dnf environment install kde-desktop-environment
If you intentionally need only the core KDE group rather than the full desktop environment, the current group command form is:
sudo dnf group install kde-desktop
Plasma Does Not Appear in the Login Screen
If the login screen does not offer a Plasma session, first confirm the session files and core packages are present:
rpm -q plasma-workspace plasma-desktop
ls /usr/share/wayland-sessions/plasma.desktop
If the package check fails or the session file is missing, complete the KDE environment install again:
sudo dnf environment install kde-desktop-environment
sudo reboot
For the optional X11 entry, verify the separate package and session file:
rpm -q plasma-workspace-x11
ls /usr/share/xsessions/plasmax11.desktop
Black Screen or Login Loop After Selecting Plasma
A black screen or login loop usually points to a graphics, session, or display-manager problem rather than a missing KDE package. From a TTY, inspect the current boot logs for display-manager errors:
sudo journalctl -b -u display-manager -n 100 --no-pager
sudo journalctl -b -p warning..alert -n 100 --no-pager
If you are using NVIDIA hardware and Wayland fails, install the optional X11 session and try Plasma (X11) at the next login:
sudo dnf install plasma-workspace-x11
sudo reboot
For proprietary driver setup, use the Fedora-specific NVIDIA driver installation guide before treating KDE itself as broken.
Plasma Login Manager Does Not Start
If you switched from GDM to Plasma Login Manager and the graphical login fails, check the service directly:
systemctl status plasmalogin.service --no-pager
sudo journalctl -b -u plasmalogin.service -n 100 --no-pager
Reinstall the Fedora KDE login-manager packages if files are missing or the service reports package-related errors:
sudo dnf reinstall plasma-login-manager kcm-plasmalogin
To recover the Fedora Workstation login path, re-enable GDM and reboot:
sudo systemctl enable --force gdm.service
sudo reboot
Conclusion
KDE Plasma is installed on Fedora through the current DNF5 environment path, with Wayland as the normal Plasma session and X11 available only when the extra session package is installed. Keep GDM if it already works for your system, or switch deliberately to Plasma Login Manager after confirming you have a recovery path. For a lighter alternate desktop, compare the Fedora Xfce installation path.


Formatting tips for your comment
You can use basic HTML to format your comment. Useful tags currently allowed in published comments:
<code>command</code>command<strong>bold</strong><em>italic</em><blockquote>quote</blockquote>