Linux Mint no longer ships a dedicated KDE edition, but KDE Plasma is still a practical replacement when Cinnamon feels too rigid or you want stronger multi-monitor tools, deeper theming, and a more configurable workspace. You can install KDE Plasma on Linux Mint from the default repositories instead of hunting down a separate download or moving to another distribution.
Linux Mint 22.x currently pulls Plasma 5.27.x and Linux Mint 21.x pulls Plasma 5.24.x from the Ubuntu base, so the sensible route is the tested default-repository install rather than chasing Plasma 6 packages or adapting LMDE steps. That path lets you pick a lean Plasma shell or a fuller KDE desktop, keep Cinnamon available through LightDM if you want a fallback, and switch display managers later if SDDM does not become active during installation.
Understand KDE Plasma Availability on Linux Mint
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, Xia, Zara, Zena) | Ubuntu 24.04 LTS (noble) | Plasma 5.27.x | June 2029 |
| Linux Mint 21.x (Vanessa, Vera, Victoria, Virginia) | Ubuntu 22.04 LTS (jammy) | Plasma 5.24.x | June 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.
Yes, Linux Mint 22.x and 21.x support KDE Plasma from the default repositories, but the packaged desktop is still on the Plasma 5 series rather than Plasma 6. LMDE uses Debian packages instead, so it needs a separate Debian-focused workflow instead of the Ubuntu-based Mint steps here.
Install KDE Plasma from Default Repositories
Installing from Linux Mint’s default repositories gives you a stable KDE Plasma setup without adding third-party package sources. Mint pulls these packages from the Ubuntu universe component that is already enabled on standard Linux Mint desktop installs, so the same path also keeps updates inside the normal Mint update flow.
Update Linux Mint Before Installing KDE Plasma
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
These commands use
sudofor system changes. If your account is not in the sudoers file yet, follow the guide on how to create and add users to sudoers on Linux Mint or run the commands from an administrator account.
Check for Existing KDE Plasma Packages
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.
If you do not use text filters often, the grep command in Linux guide shows how grep narrows the dpkg -l output to just the KDE packages you want to inspect.
Compare KDE Plasma Package Profiles on Linux Mint
These three KDE meta packages cover the usual Linux Mint setups, from a lean VM install to the full KDE application stack:
| Use Case | Meta Package | What You Get |
|---|---|---|
| Minimal install for VMs or custom setups | kde-plasma-desktop | Plasma shell, KWin, System Settings, and the core desktop pieces without the broader KDE application set. |
| Balanced daily-driver desktop | kde-standard | Adds Dolphin file manager, Konsole terminal, Discover, Gwenview, and the core KDE frameworks most Mint users expect. |
| Complete KDE workflow | kde-full | Pulls in KDE PIM, Calligra, educational packages, games, and the wider Kubuntu application stack. |
For most users, kde-standard is the balanced choice because it adds the everyday KDE tools without pulling in the full Kubuntu software stack.
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 the KDE Standard Profile on Linux Mint
The standard profile is the best fit for most Linux Mint systems because it installs the core KDE applications without dragging in every optional package.
sudo apt install kde-standard -y
This command installs Dolphin, Konsole, Discover, Gwenview, and the core KDE frameworks that power widgets, activities, and Plasma’s customization features. If the package installer asks which display manager to use, choose SDDM for the most KDE-native login screen. If no prompt appears or LightDM remains active after reboot, switch to SDDM later with sudo dpkg-reconfigure sddm.
Install the KDE Minimal Profile on Linux Mint
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 the Full KDE Profile on Linux Mint
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.
Configure SDDM for KDE Plasma on Linux Mint
If the installer asks which display manager to use, that choice controls which login screen handles your KDE Plasma sessions. Linux Mint users usually narrow the decision to these two 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 Linux Mint systems, SDDM is the better match because it integrates cleanly with Plasma’s theming and session handling. Keep LightDM if you switch between Cinnamon and Plasma often or you prefer Mint’s default login screen.
To proceed with SDDM in the terminal dialog, press the TAB key to highlight <Ok>, then press ENTER.

Fix the KDE Plasma Virtual Keyboard Bug in Linux Mint VMs
In some virtual environments, especially after you install VirtualBox on Linux Mint or run Mint under VMware or QEMU, a bug can cause 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; sudo tee is used because plain > redirection would still try to write the file as your regular user. 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 Linux Mint and Verify KDE Plasma
Once the installation completes, reboot your system to apply the desktop environment and display manager changes:
sudo reboot
After restarting, you will arrive at the login screen. If you selected SDDM, you should see the KDE-themed login interface. If LightDM remained the default, Plasma still appears in the session chooser.
Select the KDE Plasma Session on Linux Mint
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 on Linux Mint
After rebooting, confirm that the Plasma package and session file are present before you start customizing the desktop:
dpkg-query -W -f='${Version}\n' plasma-desktop
ls /usr/share/xsessions | grep plasma
Expected output on Linux Mint 22.x:
4:5.27.12-0ubuntu0.1 plasma.desktop
Expected output on Linux Mint 21.x:
4:5.24.7-0ubuntu0.1 plasma.desktop
The first line confirms which Plasma package version Mint installed, and plasma.desktop confirms the login manager can offer a Plasma session. Package revisions can increase after later Ubuntu updates, but Mint 22.x should stay on the 5.27 branch and Mint 21.x on the 5.24 branch. If you are already inside a local Plasma session, you can open Konsole and run plasmashell --version as an extra check.

Switch Between SDDM and LightDM on Linux Mint
If you need to switch back to LightDM for Cinnamon or reselect SDDM for Plasma later, you can reconfigure the default display manager at any time.
Reconfigure the Default Linux Mint 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:
sudo reboot
Once restarted, your system uses the newly selected display manager.
Troubleshoot KDE Plasma on Linux Mint
Most post-install problems come from the display manager, missing session files, or a damaged Plasma profile, so start with those checks before reinstalling the whole desktop.
Fix a KDE Plasma Login Screen That Shows Only the 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
sudo reboot
After rebooting, the login screen should display the normal password field.
Fix a Missing KDE Plasma Session at Linux Mint 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
Fix KDE Plasma Crashes After Linux Mint 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 the crashes happen on AMD or Intel graphics, it is also worth checking whether you need to upgrade Mesa drivers on Linux Mint before rebuilding the Plasma profile.
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 Removing KDE Plasma
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 on Linux Mint
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 sddm -y
After the meta packages are removed, clean up orphaned dependencies:
sudo apt autoremove --purge -y
Remove Leftover KDE Applications from Linux Mint
The autoremove step may still leave standalone KDE applications behind. Check for the most common packages before deciding whether you want to purge them too:
dpkg -l | grep -E '^ii.*(konsole|dolphin|okular|gwenview|kate|ark|kwrite)'
If the command shows installed KDE applications and you do not want to keep them, remove them individually:
sudo apt purge konsole dolphin okular gwenview kate ark kwrite -y
sudo apt autoremove --purge -y
Remove KDE Plasma Configuration Files on Linux Mint
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 KDE Plasma Removal on Linux Mint
Confirm KDE Plasma has been fully removed:
dpkg -l | grep -E '^ii.*plasma'
No output means the remaining installed package list no longer contains Plasma packages. Reboot to complete the change:
sudo 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” from the Mint 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 Software Manager prompts you to pick a display manager.
When Software Manager finishes, 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.
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.
Conclusion
KDE Plasma is now installed on Linux Mint with the package profile and display manager you chose, so you can keep Cinnamon as a fallback or settle into a full KDE workflow. If graphics issues show up after the switch, review how to install NVIDIA drivers on Linux Mint or how to upgrade Mesa drivers on Linux Mint before rebuilding your Plasma profile.
I added the KDE skill to Linux Mint 22.3.
Now I get this message when starting Linux Mint with the KDE configuration.
The current theme cannot be loaded due to the errors below, please select another theme.
file:///usr/share/sddm/themes/SilentSDDM-1.4.2/Main.qml: Library import requires a version
file:///usr/share/sddm/themes/SilentSDDM-1.4.2/Main.qml: Library import requires a version
file:///usr/share/sddm/themes/SilentSDDM-1.4.2/Main.qml: Library import requires a version
file:///usr/share/sddm/themes/SilentSDDM-1.4.2/Main.qml: Library import requires a version
What does this mean and what should I do about it?
Thank you for the awesome easy to follow guide.
The thing I did not anticipate (or know about) prior to switching, both Vivaldi & Signal immediately threw up flags because my “OS encryption keyring backend has changed from gnome_libsecret to kwallet5”. They both have good documentation for how to deal with it, but it might be good to give a heads up about this consequence.
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! 👍