KDE Plasma replaces Linux Mint’s default Cinnamon desktop with a highly customizable environment where you control panel layouts, desktop widgets, window behavior, and theming down to individual accent colors. If Cinnamon feels restrictive or you need features like advanced tiling workflows, per-monitor DPI scaling, or native Wayland sessions, Plasma delivers those capabilities without requiring a distribution switch.
This guide covers installing KDE Plasma from Linux Mint’s default repositories, which provides the stable Plasma version matched to your Ubuntu LTS base. You will learn how to choose between minimal, standard, and full installation profiles, configure the SDDM display manager to switch between Cinnamon and Plasma at login, avoid the virtual keyboard bug in VM environments, verify your installation, and cleanly remove Plasma if needed. If you use NVIDIA graphics on Linux Mint, KDE Plasma works well with both proprietary and open-source drivers.
Understand Linux Mint Version and Plasma Availability
Linux Mint uses Ubuntu as its package base, which determines which Plasma version you receive from the default repositories. Before installing, confirm your Mint version so you know what to expect:
| Linux Mint Version | Ubuntu Base | Plasma Version (Default Repos) | Support Until |
|---|---|---|---|
| Linux Mint 22.x (Wilma) | Ubuntu 24.04 LTS (noble) | Plasma 5.27.x | April 2029 |
| Linux Mint 21.x (Virginia) | Ubuntu 22.04 LTS (jammy) | Plasma 5.24.x | April 2027 |
Plasma 5.27 (available on Mint 22) includes significant improvements over 5.24, including better Wayland support, a revamped System Settings interface, and improved multi-monitor handling. Both versions provide a fully functional KDE desktop experience.
Install KDE Plasma from Default Repositories
Installing from Linux Mint’s default repositories provides a stable, tested KDE Plasma environment without adding third-party package sources. This method uses the same Plasma version that ships with the underlying Ubuntu LTS base and receives security updates through the standard Mint update process.
Update Your System
Before installing KDE Plasma, update your system to ensure you have the latest security patches and package versions. This prevents dependency conflicts during the desktop environment installation:
sudo apt update && sudo apt upgrade -y
Check for Existing KDE Installation
Before proceeding, verify that KDE meta packages are not already installed on your system:
dpkg -l | grep -E '^ii.*(kde-plasma-desktop|kde-standard|kde-full)'
If the command returns any results showing installed packages, Plasma is already on your system and you can skip to the SDDM configuration section. An empty output means no KDE meta packages are installed.
Compare KDE Plasma Installation Packages
KDE Plasma is available through three meta packages, each providing a different level of completeness. The table below summarizes your options:
| Use Case | Meta Package | Approximate Size | What You Get |
|---|---|---|---|
| Minimal install for VMs or custom setups | kde-plasma-desktop | ~1.2 GB | Plasma shell, KWin, System Settings, and essential configuration utilities without extra KDE apps. |
| Balanced daily-driver desktop | kde-standard | ~1.5 GB | Adds Dolphin file manager, Konsole terminal, Discover app store, Gwenview image viewer, and core KDE frameworks. |
| Complete KDE workflow | kde-full | ~3.4 GB | Includes KDE PIM (KMail, KOrganizer), Calligra office suite, educational apps, games, and the complete Kubuntu application set. |
For most users, kde-standard provides the best balance between functionality and disk space. It includes the applications most people need without the bloat of rarely-used educational software or games.
To preview exactly what packages will be installed and see the precise disk space requirement for your system, run a simulation with the -s flag:
sudo apt install -s kde-standard
Substitute kde-plasma-desktop or kde-full to preview those options instead. The simulation shows the full package list and disk usage without making any changes to your system.
Install KDE Standard (Recommended)
The standard installation provides a balanced KDE Plasma desktop with essential applications for daily use. Run the following command to install:
sudo apt install kde-standard -y
This command installs Dolphin file manager, Konsole terminal, Discover app store, Gwenview image viewer, and the core KDE frameworks that enable widgets, activities, and Plasma’s customization features. The installation typically takes 5-15 minutes depending on your internet connection and disk speed.
During installation, you will be prompted to select a display manager. This is covered in the next section.
Install KDE Minimal (Lightweight)
For a lighter installation suitable for virtual machines or custom setups where you want to choose your own applications:
sudo apt install kde-plasma-desktop -y
This deploys only the Plasma shell, KWin window manager, and System Settings without bundled applications. You will need to install a file manager, terminal emulator, and other utilities separately.
Install KDE Full (Complete Suite)
For the complete KDE experience with all default applications:
sudo apt install kde-full -y
This includes KDE PIM (KMail, KOrganizer, Kontact), Calligra office suite, educational apps, games, and every utility shipping with Kubuntu. Choose this option if you want the full KDE ecosystem and have sufficient disk space.
(Optional) Enable Kubuntu Updates PPA for Early Bugfixes
The Kubuntu Updates PPA provides KDE Plasma bugfix releases before they reach Ubuntu’s main repositories. This PPA does not deliver major version upgrades (you will still receive Plasma 5.27.x on Mint 22 or 5.24.x on Mint 21), but you may get point releases with bug fixes slightly earlier than the default update schedule.
This PPA is maintained by the Kubuntu team, not Linux Mint. While it works on Mint systems, packages are not tested against Cinnamon or other Mint-specific components. Most users do not need this PPA since updates typically reach the default repositories within a few weeks. Only add it if you specifically want early access to Plasma bugfix releases.
To add the Kubuntu Updates PPA, run:
sudo add-apt-repository ppa:kubuntu-ppa/ppa -y
After adding the PPA, update your package lists:
sudo apt update
If you have already installed KDE Plasma from the default repositories, upgrade to receive any newer bugfix versions from the PPA:
sudo apt upgrade -y
To remove the PPA later and revert to official repository packages, use ppa-purge:
sudo apt install ppa-purge -y
sudo ppa-purge ppa:kubuntu-ppa/ppa
Configure SDDM Display Manager
During installation, a prompt appears asking you to choose the default display manager. The display manager controls the login screen and session selection. You have two practical options:
| Display Manager | Best For | Advantages | Considerations |
|---|---|---|---|
| SDDM | Dedicated KDE Plasma users | Native KDE integration, better theme support, modern features | Additional package to maintain, designed specifically for KDE |
| LightDM | Multi-desktop setups | Linux Mint default, lighter resource usage, works with all desktops | Less polished with KDE themes, fewer Plasma-specific features |
For most users installing KDE Plasma, select SDDM when prompted. It provides the best integration with Plasma’s theming system and features like automatic session restoration. If you frequently switch between Cinnamon and Plasma or prefer the familiar Mint login screen, LightDM remains a solid universal choice.
To proceed with SDDM in the terminal dialog, press the TAB key to highlight <Ok>, then press ENTER.

Fix the Virtual Machine Keyboard Bug
In some virtual environments (VirtualBox on Linux Mint, VMware, QEMU), a bug causes the SDDM login screen to display only a large on-screen keyboard after rebooting, making it impossible to log in normally. To prevent this issue, create an SDDM drop-in configuration before rebooting:
sudo mkdir -p /etc/sddm.conf.d
printf "[General]\nInputMethod=\n" | sudo tee /etc/sddm.conf.d/virtualkbd.conf
The first command creates the configuration directory if it does not exist. The second command writes a drop-in file that sets InputMethod= to empty, which disables the virtual keyboard. SDDM automatically loads configuration files from /etc/sddm.conf.d/ even when the main /etc/sddm.conf file does not exist, so this approach works without generating the base configuration manually.
This fix is only necessary if you are running Linux Mint inside a virtual machine. If you are installing on physical hardware, you can skip this step.
Reboot and Verify Installation
Once the installation completes, reboot your system to apply the desktop environment and display manager changes:
reboot
After restarting, you will arrive at the login screen. If you selected SDDM, you will see the KDE-themed login interface.
Select KDE Plasma at Login
Before entering your credentials, ensure KDE Plasma is selected as your desktop session:
- Click the session selector (gear icon or dropdown menu) typically located in the bottom-left corner of the SDDM login screen or top-right corner on LightDM.
- Select “Plasma” or “Plasma (X11)” from the list. If you want to try Wayland, select “Plasma (Wayland)” instead.
- Enter your username and password to log in.
Your selection is remembered for future logins, so you only need to choose the session once unless you want to switch between desktops.
Verify KDE Plasma Installation
After logging in, verify your Plasma installation by checking the version. Open Konsole (the KDE terminal) from the application launcher and run:
plasmashell --version
Expected output on Linux Mint 22.x:
plasmashell 5.27.12
Expected output on Linux Mint 21.x:
plasmashell 5.24.7
The version number confirms KDE Plasma is installed and running. Minor version numbers may differ slightly after system updates.

Switch Display Managers
If you need to switch between display managers after installation, perhaps to return to LightDM for Cinnamon or to GDM for GNOME, you can reconfigure the default at any time.
Reconfigure the Default Display Manager
Open a terminal and run the reconfigure command:
sudo dpkg-reconfigure sddm
A dialog appears listing all installed display managers. Use the arrow keys to select your preferred option and press ENTER. After making your selection, reboot to apply the change:
reboot
Once restarted, your system uses the newly selected display manager.
Troubleshoot Common KDE Plasma Issues
Desktop environment installations can occasionally run into issues. This section covers the most common problems and their solutions.
Login Screen Shows Only Virtual Keyboard
If the SDDM login screen displays only a large on-screen keyboard with no option to type your password normally, the virtual keyboard bug is affecting your system. This typically happens in virtual machines.
To fix this, switch to a text console by pressing Ctrl+Alt+F3, log in with your username and password, then run:
sudo mkdir -p /etc/sddm.conf.d
printf "[General]\nInputMethod=\n" | sudo tee /etc/sddm.conf.d/virtualkbd.conf
reboot
After rebooting, the login screen should display the normal password field.
Plasma Session Not Available at Login
If “Plasma” does not appear in the session selector at the login screen, the session files may not have been installed correctly. Verify the installation by checking for the session file:
ls /usr/share/xsessions/ | grep plasma
Expected output:
plasma.desktop
If the file is missing, reinstall the plasma-desktop package:
sudo apt install --reinstall plasma-desktop
Plasma Crashes After Login
If Plasma crashes immediately after login or you see a black screen, a corrupted configuration file may be the cause. Switch to a text console with Ctrl+Alt+F3, log in, and rename your Plasma configuration directory to reset settings:
mv ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasma-org.kde.plasma.desktop-appletsrc.backup
mv ~/.config/kwinrc ~/.config/kwinrc.backup
Then switch back to the graphical login with Ctrl+Alt+F1 and try logging in again. If this resolves the issue, you can gradually restore settings from the backup files or reconfigure Plasma manually.
Remove KDE Plasma from Linux Mint
If you decide to remove KDE Plasma and return to your previous desktop setup, follow these steps to cleanly uninstall all components.
Switch Back to LightDM Before Removal
Before purging KDE components, return the system to Mint’s default display manager (LightDM) so the login screen still works after Plasma is removed:
sudo dpkg-reconfigure lightdm
sudo systemctl enable lightdm
sudo systemctl disable sddm
After selecting LightDM in the dialog, verify the change took effect:
cat /etc/X11/default-display-manager
Expected output:
/usr/sbin/lightdm
Only proceed with removal once this file shows the correct display manager.
Uninstall KDE Plasma Packages
Remove the KDE meta packages and core components. This command covers all three installation profiles:
sudo apt purge kde-standard kde-plasma-desktop kde-full plasma-desktop kubuntu-desktop sddm -y
After the meta packages are removed, clean up orphaned dependencies:
sudo apt autoremove --purge -y
Remove Leftover KDE Applications
The autoremove command may not catch every KDE application. Check for remaining packages:
dpkg -l | grep -E '^ii.*(konsole|dolphin|okular|gwenview|kate|ark|kwrite)'
If this command shows installed packages, remove them individually:
sudo apt purge konsole dolphin okular gwenview kate ark kwrite -y
sudo apt autoremove --purge -y
Remove KDE Configuration Files
The following commands permanently delete KDE Plasma configuration files, including customized panel layouts, widget settings, and application preferences. If you might reinstall Plasma later and want to keep your settings, skip this step.
To fully clean up user-level configuration files:
rm -rf ~/.config/kde* ~/.config/plasma* ~/.config/kwin* ~/.local/share/kded5 ~/.local/share/plasma*
Verify Removal
Confirm KDE Plasma has been fully removed:
dpkg -l | grep -E '^ii.*plasma'
If no output appears, all Plasma packages have been removed. Reboot to complete the process:
reboot
After restarting, your system will boot into the Cinnamon desktop with LightDM as the login screen.
Install KDE Plasma Using Software Manager
If you prefer a graphical installation method instead of terminal commands, Linux Mint’s Software Manager provides a straightforward alternative. However, this method installs only the minimal kde-plasma-desktop package.
- Open Software Manager from the application menu or by searching for “Software Manager” in the start menu.
- Search for “KDE Plasma Desktop” using the search bar at the top.
- Select the “KDE Plasma Desktop” package from the search results.
- Click the “Install” button and enter your password when prompted.
- Choose SDDM or LightDM when asked to select a display manager (see the comparison table earlier in this guide).
After installation completes, log out or reboot, then select “Plasma” from the session chooser at the login screen. If you want the additional applications included in kde-standard or kde-full, use the terminal installation method instead.
Conclusion
You now have KDE Plasma installed on Linux Mint, complete with configuration options for display managers and the knowledge to troubleshoot common issues. Plasma provides extensive customization through System Settings, including panel positioning, widget management, desktop effects, and theming. If you run into graphics driver issues, consider reviewing your NVIDIA driver configuration. For users who want to customize their boot experience alongside their new desktop, the GRUB Customizer tool integrates well with KDE’s theming capabilities.
Official KDE Resources
For further information, updates, and community support related to KDE Plasma:
- KDE Plasma Desktop – Official Plasma homepage with feature highlights and the latest release information.
- KDE Community Wiki – Documentation, development resources, and community discussions.
- KDE UserBase Plasma Documentation – User-focused guides for configuring and customizing Plasma.
- Kubuntu Updates PPA – Optional PPA providing early access to KDE Plasma bugfix releases for Ubuntu-based distributions.
If you’re trying to apply the bug fix but getting “no such file or directory”, you can simply create the file.
“sudo touch /etc/sddm.conf”
Then run the sed command.
Obviously, this won’t actually fix the bug if SDDM is looking for it’s config file in another location, but assuming it’s still looking there in /etc, you should be fine.
Thanks for the suggestion! I actually updated the article to use a drop-in config approach instead, since Debian-based SDDM packages don’t include the main
/etc/sddm.conffile by default. The new method creates/etc/sddm.conf.d/virtualkbd.confwhich works reliably without needing to generate the base config file manually.it’s actually really cool the you can just do this on linux. Imagine if this was possible on windows too.
Btw, for those having the “no such file or directory” error (I had it too), you have to create a file “/etc/sddm.conf.d/kde_settings.conf” and write at the end this:
[General]
InputMethod=
Thanks for sharing that! The article already covers creating a drop-in config file in
/etc/sddm.conf.d/(I usedvirtualkbd.confas the filename, but any name works). The key is that SDDM loads all files from that directory automatically. Your approach withkde_settings.confdoes the exact same thing. Appreciate you confirming it works!I expected this to be a very hard thing to do, I´m lucky I found your AWESOME tutorial!
you can fix this error simply with adding “autologin” after installation 🙂
Thanks for the tip! Autologin is a great feature for convenience, but it doesn’t actually fix the virtual keyboard bug that some users see in VMs. The article’s drop-in config approach directly addresses that issue by setting
InputMethod=in SDDM. If you want to enable autologin too, you can add it to the same config file under a new section. Appreciate you sharing!I am also getting this same error.
Hi Bob, see my reply to Scott.
I get a no such file or directory message when trying to apply bug fix. Any ideas?
Hi Scott, thanks for the comment! That “no such file or directory” error when trying to apply the SDDM bug fix (the
sedcommand for/etc/sddm.conf) usually means thesddm.conffile isn’t where the command expects it, or it hasn’t been created yet.A few things to check:
1. Did the KDE installation (e.g.,
sudo apt install kde-standardor whichever version you chose) complete successfully before you ran thesedcommand? SDDM and its configuration file are typically set up during that main KDE installation.2. Could you double-check the path in the command? It should be exactly:
sudo sed -i '/\[General\]/a InputMethod=' /etc/sddm.conf. Sometimes a small typo can creep in and cause this.3. You can quickly check if the configuration file exists by running this command in your terminal:
ls /etc/sddm.conf. If the output says something like “cannot access ‘/etc/sddm.conf’: No such file or directory”, then the file indeed isn’t there, and the issue likely stems from the KDE/SDDM installation step.Let me know if checking these points helps, or if you spot anything else!
Hello, had same issue as Scott. Pretty sure I’ve made no typos and installation went smoothly. Fixed it by creating sddm.conf manually and typing in InputMethod=
Hope it helps someone
Hey Josh, it seems that there is a bug with the repository not providing the sddm.conf file upon installation. I was able to fix this by using the command “sddm –example-config“, and then copying the text that generates to make sddm.conf file. Then I went ahead and applied your fix and then it worked.
I found the info for the conf file here: https://forums.debian.net/viewtopic.php?t=149885
Thanks John for the detailed breakdown and the Debian forums link! You’re spot on about the repository bug, SDDM packages in Debian-based distros don’t include the main
/etc/sddm.conffile by default. I’ve updated the article to use a drop-in config approach instead, which creates/etc/sddm.conf.d/virtualkbd.confand works without needing the base file. Yoursddm --example-configworkaround is a solid alternative for anyone still using the old method. Appreciate you sharing that! 👍