You installed Fedora and the desktop does not match your workflow
You installed Fedora Workstation, logged in, and the interface feels too restrictive. You want a traditional taskbar, window decorations, and instant access to every setting. Or you tried KDE Plasma, got buried in configuration menus, and just want a clean workspace that gets out of the way. You are not locked into what shipped on the installation media. Fedora treats desktop environments as modular groups. You can install, remove, or switch between them without touching the kernel or your user data.
What is actually happening under the hood
GNOME and KDE Plasma are not themes. They are complete desktop environments. Each one ships its own window manager, session controller, notification daemon, and settings backend. When you log in, the display manager hands your credentials to a session script. That script starts the desktop environment and sets environment variables like XDG_CURRENT_DESKTOP and XDG_SESSION_DESKTOP. The two environments do not share configuration files. They do not merge their panels or settings apps. They run in isolation, sharing only the underlying X server or Wayland compositor, the package manager, and the system kernel.
Think of them like two different control panels bolted onto the same engine. The engine is Fedora. The control panels are GNOME and KDE. You can swap control panels without rebuilding the engine. Fedora's dnf package manager handles the dependencies cleanly. Installing both groups will not break your system. It will consume extra disk space and add a few background services that only run when you select that session at login.
Configuration files follow a strict convention. User modifications live in /etc/ or ~/.config/. Package defaults ship in /usr/lib/. The desktop environments respect this boundary. When you install a new desktop group, dnf places new defaults in /usr/lib/ and leaves your existing ~/.config/ untouched. This prevents accidental overwrites. You can safely switch back and forth without losing your custom shortcuts or panel layouts.
Run dnf upgrade --refresh weekly to keep the desktop stack current. The command forces a metadata refresh and pulls the latest security patches before they accumulate.
How to install and switch between desktop environments
Fedora groups desktop environments into installable meta-packages. You pull the group you want, log out, and pick the new session from the display manager. The display manager on Fedora Workstation is GDM. It supports both GNOME and KDE sessions out of the box.
Here is how to add KDE Plasma to a default GNOME installation.
sudo dnf groupinstall "KDE Plasma Workspaces"
# groupinstall pulls the meta-package and all recommended dependencies
# sudo elevates privileges to write to /usr and /etc
# Fedora resolves dependencies automatically and prompts for confirmation
# The transaction installs plasmashell, kwin_wayland, and core KDE utilities
If you are running KDE and want to add GNOME, run the equivalent command for the GNOME group.
sudo dnf groupinstall "GNOME"
# This pulls the core GNOME stack including gnome-shell and mutter
# It does not replace your current desktop environment
# Dependencies are merged with your existing package set
# The command also installs gdm if it was not present previously
After the transaction completes, log out of your current session. Click the gear icon or session selector on the login screen. Choose the new desktop environment from the dropdown. Enter your password. The display manager will launch the new session script and start the corresponding window manager.
Reboot only if the display manager fails to list the new session. Most of the time, a simple logout and login is enough.
Verify the session is running correctly
Confirm that the system recognized your choice. Open a terminal and check the desktop environment variable.
echo $XDG_CURRENT_DESKTOP
# Returns GNOME for GNOME sessions
# Returns KDE for Plasma sessions
# This variable tells applications which desktop integration to use
# Many GTK and Qt apps read this to apply the correct theme
Check the running session process to verify the correct compositor is active.
ps -C gnome-shell plasmashell --no-headers
# Lists the main desktop process if it is running
# An empty output means the session failed to start the compositor
# Check journalctl if the process is missing
# The compositor handles window placement and screen rendering
Run the status check before guessing at configuration issues. The variable tells you exactly which environment is handling your windows and panels.
Common pitfalls and what the errors look like
Switching desktop environments introduces a few predictable friction points. The most common issue involves display server selection. Fedora defaults to Wayland for both GNOME and KDE. Some legacy applications, older NVIDIA drivers, or remote desktop tools still require X11. If your screen flickers or the desktop fails to start, switch to X11 at the login screen before entering your password.
Configuration drift is the second trap. GNOME and KDE store settings in different directories. GNOME uses ~/.config/gnome-shell and dconf. KDE uses ~/.config/plasma* and ~/.local/share/kxmlgui5. They do not sync. If you switch back and forth, your panel layouts, keyboard shortcuts, and theme choices will reset to the defaults for that environment. This is intentional. The environments are not designed to share state.
Extension conflicts break GNOME sessions frequently. Third-party extensions from gnome-extensions.org often target a specific GNOME version. When Fedora upgrades the desktop stack, outdated extensions can prevent gnome-shell from starting. You will see a blank screen or a fallback session. Disable extensions before upgrading the desktop group.
(gnome-shell:1234): GLib-GObject-WARNING **: 10:00:01.234: invalid cast from 'MetaWindow' to 'GnomeShellExtension'
KDE crashes usually involve plasmashell. If the panel disappears and you get a notification about a crashed component, check the user journal.
journalctl -xeu plasmashell --no-pager | tail -20
# -x adds explanatory context to journal entries
# -u filters for the plasmashell unit
# --no-pager outputs raw text for easier reading
# tail shows the most recent crash dump and stack trace
# The output reveals missing libraries or theme conflicts
SELinux policies remain identical regardless of which desktop you run. Fedora enforces the same mandatory access controls for both environments. You will not gain or lose security by switching. File associations and MIME types are handled separately by each desktop. If icons look broken after switching, install the base icon themes.
sudo dnf install adwaita-icon-theme breeze-icon-theme
# adwaita is the default GNOME icon set
# breeze is the default KDE icon set
# Installing both prevents missing icon fallbacks
# The package manager resolves conflicts automatically
Trust the package manager. Manual file edits drift, snapshots stay.
When to use GNOME versus KDE Plasma
Use GNOME when you want a consistent, keyboard-driven workflow with minimal configuration overhead. Use KDE Plasma when you need granular control over window behavior, panel layouts, and system-wide theming. Use GNOME when you develop for Linux desktops and want to test against the most widely adopted upstream stack. Use KDE Plasma when you prefer a traditional desktop metaphor with start menus, taskbars, and right-click context menus. Use GNOME when you value stability and a smaller attack surface for desktop extensions. Use KDE Plasma when you need built-in tools for system monitoring, network management, and file associations without installing third-party packages. Stay on the default Workstation spin if you only deviate from the defaults occasionally.