AlmaLinux ships with GNOME as its default desktop. That's fine β GNOME is solid and well-supported. But if you've ever stared at it and thought "I wish I could move everything around," you're not alone.
KDE Plasma gives you that control. It's one of the most customizable desktop environments available for Linux, and yes, it runs beautifully on AlmaLinux. This guide walks you through the whole installation process, from a clean terminal to a fully working KDE desktop β with real commands, real explanations, and no made-up nonsense.
Related reading on BigWriteHook
How to Pause When Using the LS Command: A Linux User's Guide βWhat is KDE Plasma β and why bother?
KDE Plasma is a free, open-source desktop environment built on the Qt framework. It has been around since 1996, which makes it one of the oldest and most mature graphical environments in the Linux world. The current version, Plasma 5.27 LTS, is what you'll find in the EPEL repository for AlmaLinux 9. According to the KDE Community Wiki, AlmaLinux even ships a dedicated KDE Live ISO for both x86_64 and ARM architectures.
GNOME takes a clean, opinionated approach β you do things its way or not at all. KDE takes the opposite stance: it hands you the keys and says, "Do whatever you want." That's either liberating or overwhelming, depending on the kind of person you are. For power users and developers who want a truly personal workspace, KDE is hard to beat.
AlmaLinux is a community-driven RHEL clone built for enterprise stability. Pairing it with KDE gives you server-grade reliability with a desktop that doesn't look like it belongs in 2009.
Before you start: requirements
KDE Plasma is lightweight by modern standards, but it still needs a reasonable system. The table below shows the minimum and recommended specs, based on what the AlmaLinux community and KDE documentation suggest.
| Component | Minimum | Recommended |
|---|---|---|
| RAM | 2 GB | 4 GB+ |
| Processor | Dual-core | Quad-core |
| Storage | 10 GB free | 20 GB free |
| Graphics | OpenGL support | Dedicated GPU |
| Network | Active internet connection | Stable broadband |
You'll also need:
- AlmaLinux 9 installed (server or minimal install both work)
- sudo or root access β most commands here need elevated privileges
- A terminal β SSH is fine if you're on a remote or headless machine
Step 1: Update your AlmaLinux system
Before anything else, bring your system fully up to date. This avoids dependency mismatches and ensures you're working with the latest security patches.
Terminal
sudo dnf update -y
The -y flag auto-confirms all prompts, so you don't need to sit there pressing Enter repeatedly. On a fresh install this might pull in a few hundred megabytes. Grab a coffee.
AlmaLinux 9 - BaseOS Β 4.3 MB/s | 2.3 MB
AlmaLinux 9 - AppStream Β 5.1 MB/s | 8.7 MB
Dependencies resolved.
Complete!
Step 2: Enable the EPEL repository
KDE Plasma is not part of AlmaLinux's default repositories. You need to add the Extra Packages for Enterprise Linux (EPEL) repository β a well-maintained collection of additional packages maintained by the Fedora Project. The official AlmaLinux documentation lists EPEL as the correct source for KDE Plasma packages.
Terminal
sudo dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
Alternatively, on AlmaLinux 9 you can install it directly from the repos:
sudo dnf install -y epel-release
Once installed, verify it's active:
sudo dnf repolist
You should see epel listed in the output.
Step 3: Enable the CRB repository
Some KDE dependencies live in the Code Ready Builder (CRB) repository β AlmaLinux's equivalent of RHEL's CodeReady Linux Builder. This repo provides development tools and build dependencies that aren't in the default channels.
AlmaLinux 9 / CentOS Stream 9
sudo dnf config-manager --set-enabled crb
subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms
Confirm the CRB repo is now enabled:
sudo dnf repolist all | grep crb
You should see it listed as enabled.
Step 4: Install KDE Plasma Workspaces
Now for the main event. The following command installs the full KDE Plasma Workspaces group along with base-x (the foundational X11 components needed to run a graphical interface):
Terminal β install KDE Plasma
sudo dnf groupinstall "KDE Plasma Workspaces" "base-x" -y
This pulls in a substantial number of packages β typically several hundred megabytes. The exact amount depends on what's already on your system. On a minimal AlmaLinux server install, expect to wait 10β20 minutes depending on your internet speed.
What does this package group include? Among other things: the Plasma shell, KWin (the window manager), the KDE application suite, the Dolphin file manager, and SDDM (the display manager KDE uses for login).
Installing group/module packages:
Β plasma-desktop Β Β Β Β Β Β Β Β Β Β Β Β x86_64 Β 5.27.9-3.el9 Β epel
Β plasma-workspace Β Β Β Β Β Β Β Β Β x86_64 Β 5.27.9-3.el9 Β epel
Β sddm Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β x86_64 Β 0.19.0-8.el9 Β epel
Β xorg-x11-server-Xorg Β Β Β Β Β x86_64 Β 1.20.11-22 Β Β baseos
Install Β 347 Packages
Total download size: 312 M
Complete!
Step 5: Enable SDDM and set the graphical target
KDE uses SDDM (Simple Desktop Display Manager) as its login screen. You need to tell AlmaLinux to use it β and to boot into graphical mode by default instead of staying in text mode.
Enable SDDM
sudo systemctl enable sddm
Set graphical target as default
sudo systemctl set-default graphical.target
The graphical.target tells systemd to start the full GUI stack on boot. Without this, you'd boot into the command line and have to start the desktop manually β which gets old quickly.
sudo systemctl start sddmThis starts SDDM immediately and drops you to the login screen.
Step 6: Reboot and log in to KDE
Save any open work and reboot:
sudo reboot
Your system will restart and land on the SDDM login screen β a clean, dark interface. Here's the important bit: if you previously had GNOME installed, AlmaLinux might default to it.
To select KDE, click the gear/session icon near the bottom of the login screen, choose Plasma, then enter your password and log in.
Welcome to KDE Plasma. Your taskbar is at the bottom, your application launcher is bottom-left, and the rest is yours to rearrange however you like.
KDE vs GNOME on AlmaLinux
If you're not sure whether KDE is the right call, here's a quick and honest comparison. Both environments are well-maintained and work reliably on AlmaLinux β this is about preference, not quality.
π· KDE Plasma
- Highly customizable β move anything
- Windows-like layout by default
- Lower RAM usage at idle
- KDE Connect for Android integration
- Steeper learning curve
- Uses Qt framework
πΆ GNOME
- Clean, opinionated design
- Ships as AlmaLinux default
- Fewer configuration options out-of-the-box
- Excellent touchscreen support
- Uses GTK framework
- Extensions ecosystem
According to a comparison on the AlmaLinux community resources, KDE tends to be more resource-efficient in enterprise environments β which matters if you're running workstations alongside server workloads.
Post-install tips: making KDE yours
Once you're in, here are a few things worth doing right away:
Change the theme
Right-click the desktop β Configure Desktop and Wallpaper. Or open System Settings β Appearance β Global Theme for a full theme overhaul. Breeze Dark is excellent.
Install additional KDE apps
sudo dnf install kdenlive krita k3b -y
Kdenlive is a professional video editor. Krita is a digital painting app. K3B burns discs if you still do that sort of thing.
Set up KDE Connect
KDE Connect lets your Android phone and AlmaLinux desktop talk to each other β share files, see notifications, control media. Install it with:
sudo dnf install kdeconnect -y
Adjust power settings
Go to System Settings β Power Management to configure sleep timers and screen lock behaviour β especially useful on laptops.
More technology guides on BigWriteHook
Browse all Technology articles βTroubleshooting common issues
System boots to text mode after install
This means the graphical target wasn't set correctly. Run these two commands, then reboot:
sudo systemctl enable sddm
sudo systemctl set-default graphical.target
sudo reboot
Blank or black screen at login
This sometimes happens with older graphics hardware. Switch to a virtual console with Ctrl+Alt+F2, log in as your user, and check for driver issues with:
sudo journalctl -xe | grep -i error
KDE not showing up as a session option in SDDM
The installation may be incomplete. Try reinstalling the group:
sudo dnf groupinstall "KDE Plasma Workspaces" -y
Poor performance / sluggish animations
Open System Settings β Display and Monitor β Compositor and reduce animation speed, or switch the rendering backend from OpenGL to XRender. This usually fixes slowness on older integrated graphics.
Package dependency errors during install
Double-check that both EPEL and CRB repositories are enabled:
sudo dnf repolist | grep -E "epel|crb"
If either is missing, revisit Steps 2 and 3.
That's it β you're running KDE on AlmaLinux
The process comes down to four core steps: update your system, enable EPEL and CRB repositories, install the KDE Plasma group, and set SDDM as your display manager. Everything else is customisation.
KDE and AlmaLinux is a genuinely good combination. You get the stability and long-term support of an enterprise Linux distribution paired with one of the most flexible desktop environments available. Whether you're setting this up as a daily driver, a developer workstation, or a test environment β it holds up.
If you run into anything not covered here, the AlmaLinux community forums and the KDE community forums are both active and helpful.
Sources and references
- AlmaLinux Wiki β After Installation Guide
- KDE Community Wiki β Plasma Live Images
- linux.how2shout.com β Installing KDE Plasma on AlmaLinux 9
- idroot.us β How To Install KDE Plasma on AlmaLinux 9
- orcacore.com β Install KDE Plasma on AlmaLinux 9 / RHEL 9
- Linux.org forums β Installing KDE Plasma on AlmaLinux 9.1
AlmaLinux ships with GNOME as its default desktop. That's fine β GNOME is solid and well-supported. But if you've ever stared at it and thought "I wish I could move everything around," you're not alone.
KDE Plasma gives you that control. It's one of the most customizable desktop environments available for Linux, and yes, it runs beautifully on AlmaLinux. This guide walks you through the whole installation process, from a clean terminal to a fully working KDE desktop β with real commands, real explanations, and no made-up nonsense.
Related reading on BigWriteHook
How to Pause When Using the LS Command: A Linux User's Guide βWhat is KDE Plasma β and why bother?
KDE Plasma is a free, open-source desktop environment built on the Qt framework. It has been around since 1996, which makes it one of the oldest and most mature graphical environments in the Linux world. The current version, Plasma 5.27 LTS, is what you'll find in the EPEL repository for AlmaLinux 9. According to the KDE Community Wiki, AlmaLinux even ships a dedicated KDE Live ISO for both x86_64 and ARM architectures.
GNOME takes a clean, opinionated approach β you do things its way or not at all. KDE takes the opposite stance: it hands you the keys and says, "Do whatever you want." That's either liberating or overwhelming, depending on the kind of person you are. For power users and developers who want a truly personal workspace, KDE is hard to beat.
AlmaLinux is a community-driven RHEL clone built for enterprise stability. Pairing it with KDE gives you server-grade reliability with a desktop that doesn't look like it belongs in 2009.
Before you start: requirements
KDE Plasma is lightweight by modern standards, but it still needs a reasonable system. The table below shows the minimum and recommended specs, based on what the AlmaLinux community and KDE documentation suggest.
| Component | Minimum | Recommended |
|---|---|---|
| RAM | 2 GB | 4 GB+ |
| Processor | Dual-core | Quad-core |
| Storage | 10 GB free | 20 GB free |
| Graphics | OpenGL support | Dedicated GPU |
| Network | Active internet connection | Stable broadband |
You'll also need:
- AlmaLinux 9 installed (server or minimal install both work)
- sudo or root access β most commands here need elevated privileges
- A terminal β SSH is fine if you're on a remote or headless machine
Step 1: Update your AlmaLinux system
Before anything else, bring your system fully up to date. This avoids dependency mismatches and ensures you're working with the latest security patches.
Terminal
sudo dnf update -y
The -y flag auto-confirms all prompts, so you don't need to sit there pressing Enter repeatedly. On a fresh install this might pull in a few hundred megabytes. Grab a coffee.
AlmaLinux 9 - BaseOS Β 4.3 MB/s | 2.3 MB
AlmaLinux 9 - AppStream Β 5.1 MB/s | 8.7 MB
Dependencies resolved.
Complete!
Step 2: Enable the EPEL repository
KDE Plasma is not part of AlmaLinux's default repositories. You need to add the Extra Packages for Enterprise Linux (EPEL) repository β a well-maintained collection of additional packages maintained by the Fedora Project. The official AlmaLinux documentation lists EPEL as the correct source for KDE Plasma packages.
Terminal
sudo dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
Alternatively, on AlmaLinux 9 you can install it directly from the repos:
sudo dnf install -y epel-release
Once installed, verify it's active:
sudo dnf repolist
You should see epel listed in the output.
Step 3: Enable the CRB repository
Some KDE dependencies live in the Code Ready Builder (CRB) repository β AlmaLinux's equivalent of RHEL's CodeReady Linux Builder. This repo provides development tools and build dependencies that aren't in the default channels.
AlmaLinux 9 / CentOS Stream 9
sudo dnf config-manager --set-enabled crb
subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms
Confirm the CRB repo is now enabled:
sudo dnf repolist all | grep crb
You should see it listed as enabled.
Step 4: Install KDE Plasma Workspaces
Now for the main event. The following command installs the full KDE Plasma Workspaces group along with base-x (the foundational X11 components needed to run a graphical interface):
Terminal β install KDE Plasma
sudo dnf groupinstall "KDE Plasma Workspaces" "base-x" -y
This pulls in a substantial number of packages β typically several hundred megabytes. The exact amount depends on what's already on your system. On a minimal AlmaLinux server install, expect to wait 10β20 minutes depending on your internet speed.
What does this package group include? Among other things: the Plasma shell, KWin (the window manager), the KDE application suite, the Dolphin file manager, and SDDM (the display manager KDE uses for login).
Installing group/module packages:
Β plasma-desktop Β Β Β Β Β Β Β Β Β Β Β Β x86_64 Β 5.27.9-3.el9 Β epel
Β plasma-workspace Β Β Β Β Β Β Β Β Β x86_64 Β 5.27.9-3.el9 Β epel
Β sddm Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β x86_64 Β 0.19.0-8.el9 Β epel
Β xorg-x11-server-Xorg Β Β Β Β Β x86_64 Β 1.20.11-22 Β Β baseos
Install Β 347 Packages
Total download size: 312 M
Complete!
Step 5: Enable SDDM and set the graphical target
KDE uses SDDM (Simple Desktop Display Manager) as its login screen. You need to tell AlmaLinux to use it β and to boot into graphical mode by default instead of staying in text mode.
Enable SDDM
sudo systemctl enable sddm
Set graphical target as default
sudo systemctl set-default graphical.target
The graphical.target tells systemd to start the full GUI stack on boot. Without this, you'd boot into the command line and have to start the desktop manually β which gets old quickly.
sudo systemctl start sddmThis starts SDDM immediately and drops you to the login screen.
Step 6: Reboot and log in to KDE
Save any open work and reboot:
sudo reboot
Your system will restart and land on the SDDM login screen β a clean, dark interface. Here's the important bit: if you previously had GNOME installed, AlmaLinux might default to it.
To select KDE, click the gear/session icon near the bottom of the login screen, choose Plasma, then enter your password and log in.
Welcome to KDE Plasma. Your taskbar is at the bottom, your application launcher is bottom-left, and the rest is yours to rearrange however you like.
KDE vs GNOME on AlmaLinux
If you're not sure whether KDE is the right call, here's a quick and honest comparison. Both environments are well-maintained and work reliably on AlmaLinux β this is about preference, not quality.
π· KDE Plasma
- Highly customizable β move anything
- Windows-like layout by default
- Lower RAM usage at idle
- KDE Connect for Android integration
- Steeper learning curve
- Uses Qt framework
πΆ GNOME
- Clean, opinionated design
- Ships as AlmaLinux default
- Fewer configuration options out-of-the-box
- Excellent touchscreen support
- Uses GTK framework
- Extensions ecosystem
According to a comparison on the AlmaLinux community resources, KDE tends to be more resource-efficient in enterprise environments β which matters if you're running workstations alongside server workloads.
Post-install tips: making KDE yours
Once you're in, here are a few things worth doing right away:
Change the theme
Right-click the desktop β Configure Desktop and Wallpaper. Or open System Settings β Appearance β Global Theme for a full theme overhaul. Breeze Dark is excellent.
Install additional KDE apps
sudo dnf install kdenlive krita k3b -y
Kdenlive is a professional video editor. Krita is a digital painting app. K3B burns discs if you still do that sort of thing.
Set up KDE Connect
KDE Connect lets your Android phone and AlmaLinux desktop talk to each other β share files, see notifications, control media. Install it with:
sudo dnf install kdeconnect -y
Adjust power settings
Go to System Settings β Power Management to configure sleep timers and screen lock behaviour β especially useful on laptops.
More technology guides on BigWriteHook
Browse all Technology articles βTroubleshooting common issues
System boots to text mode after install
This means the graphical target wasn't set correctly. Run these two commands, then reboot:
sudo systemctl enable sddm
sudo systemctl set-default graphical.target
sudo reboot
Blank or black screen at login
This sometimes happens with older graphics hardware. Switch to a virtual console with Ctrl+Alt+F2, log in as your user, and check for driver issues with:
sudo journalctl -xe | grep -i error
KDE not showing up as a session option in SDDM
The installation may be incomplete. Try reinstalling the group:
sudo dnf groupinstall "KDE Plasma Workspaces" -y
Poor performance / sluggish animations
Open System Settings β Display and Monitor β Compositor and reduce animation speed, or switch the rendering backend from OpenGL to XRender. This usually fixes slowness on older integrated graphics.
Package dependency errors during install
Double-check that both EPEL and CRB repositories are enabled:
sudo dnf repolist | grep -E "epel|crb"
If either is missing, revisit Steps 2 and 3.
That's it β you're running KDE on AlmaLinux
The process comes down to four core steps: update your system, enable EPEL and CRB repositories, install the KDE Plasma group, and set SDDM as your display manager. Everything else is customisation.
KDE and AlmaLinux is a genuinely good combination. You get the stability and long-term support of an enterprise Linux distribution paired with one of the most flexible desktop environments available. Whether you're setting this up as a daily driver, a developer workstation, or a test environment β it holds up.
If you run into anything not covered here, the AlmaLinux community forums and the KDE community forums are both active and helpful.
Sources and references
- AlmaLinux Wiki β After Installation Guide
- KDE Community Wiki β Plasma Live Images
- linux.how2shout.com β Installing KDE Plasma on AlmaLinux 9
- idroot.us β How To Install KDE Plasma on AlmaLinux 9
- orcacore.com β Install KDE Plasma on AlmaLinux 9 / RHEL 9
- Linux.org forums β Installing KDE Plasma on AlmaLinux 9.1
