KDE Plasma 6.8, slated for release on October 14, 2026, will introduce a long-overdue security feature: the desktop environment can automatically lock the local session when the last Remote Desktop Protocol (RDP) client disconnects. For Windows users who routinely connect to Linux machines, this change closes a common security gap where ending a remote session left the physical desktop unlocked and exposed. The option, first reported by Linuxiac, will be configurable, meaning users and administrators can decide when automatic locking makes sense for their workflows.

What Plasma 6.8 is changing

The core addition is a new toggle in Plasma’s built-in RDP server settings. When enabled, Plasma monitors active RDP connections and, once the final client disconnects, issues a lock-screen command. This applies regardless of whether the user closed the RDP window, lost network connectivity, or simply forgot to lock manually. Critically, it locks only the session—running applications, background tasks, and unsaved work remain untouched, just protected behind the login screen until the user authenticates again.

The “last connected” logic is deliberate. A single user might connect from multiple devices simultaneously, or an administrator could be observing a session while another user is still active. Locking right after the first disconnect would disrupt such scenarios. Plasma’s approach waits until no RDP clients remain, a more pragmatic design that balances security with usability.

The feature is not a blanket mandate. KDE has made it optional, which accommodates edge cases like kiosk systems, supervised workstations, or environments where a local user is expected to take over immediately after remote maintenance. But for the majority of personal and professional setups, the safe default will be to leave it on.

Besides RDP locking, Plasma 6.8 bundles several other improvements:
- Per-user session memory: The Plasma Login Manager will remember the last desktop session type (e.g., Wayland vs. X11) chosen by each account, removing a repetitive step on multi-session systems.
- New display tool: kscreenctl replaces the older kscreen-doctor as a command-line utility for managing monitors. It promises greater reliability and a more conventional syntax, useful for scripting and remote troubleshooting.
- Smarter multi-monitor shortcuts: The Meta+number keyboard shortcuts for task switching will now target the panel on the active screen, not always the primary one. This aligns the behavior with where the user’s attention actually is.
- Discover refinements: The software center groups active and completed transactions more clearly, and Flatpak application icons load faster.
- Plasma Setup language search: Users can search for languages by locale code, native name, or English name, easing setup for multilingual environments.

These features arrive alongside maintenance releases for current Plasma versions. Plasma 6.7.4 (due August 4, 2026) fixes a KWin crash during login on some laptops, resolves a login-screen glitch after monitor reconnection, and patches a System Settings crash triggered by certain Fanatec racing pedals. Plasma 6.6.7 addresses an NVIDIA-related KWin login crash, restores full-screen video in Chromium-based browsers on virtual displays, and squashes bugs in the Digital Clock widget and Media Frame slideshow.

What this means for you

The impact depends on how you use (or administer) a Linux desktop.

For Windows users who RDP into Linux
This is the headline improvement. If you regularly connect to a Linux box via RDP—whether it’s a home server, a lab machine, or a remote workstation—the new lock behavior mimics what Windows itself does. You can disconnect and walk away, knowing the console won’t stay unlocked for anyone with physical access. It eliminates the need to remember to manually lock before closing the RDP client. However, it only works with Plasma’s native RDP server; if you rely on a third-party server like xrdp or a VNC tool, you won’t get this protection automatically.

For IT administrators and power users
The configurable nature of the feature is a double-edged sword. You’ll need to decide whether to enforce it via policies or leave it to individual users. In a managed environment, automatically locking after RDP is a basic security hygiene measure, but you may have to augment it with additional controls such as forced logouts after inactivity, full-disk encryption, or network-level RDP restrictions. The new kscreenctl tool will be welcomed by anyone who scripts display arrangements across docking stations or multi-monitor setups; it’s a foundational improvement for remote management.

For everyday Plasma users
Even if you never touch RDP, the other changes will subtly improve daily use. The Login Manager remembering your session choice means one less click at boot. If you use multiple monitors, task-switching shortcuts will feel more intuitive. Discover’s UI polish makes software updates less confusing, and faster icon loading makes the store feel snappier.

How we got here

Remote desktop on Linux has long been a patchwork of solutions, from VNC to X11 forwarding to third-party RDP implementations. KDE’s built-in RDP server, introduced in recent Plasma releases, aimed to provide a first-class, Wayland-native experience. Yet it lacked a basic security nicety that Windows RDP has offered for years: when you disconnect a remote session, the local desktop locks. On Windows, this is the default; the console session is either locked or switched to the login screen, preventing unauthorized physical access.

For Linux users, that gap meant that ending an RDP session often left the machine’s screen exactly as it was—open documents, file managers, and web browsers visible to anyone who walked up. This wasn’t just a theoretical risk. Shared offices, university labs, and home environments with family members could all be compromise points. KDE’s decision to add automatic locking, even as an optional feature, signals that the project is taking remote access security as seriously as any enterprise desktop.

The broader Linux ecosystem has been moving toward more professional remote-work support, driven by the shift to hybrid work and the growing popularity of the Steam Deck and other Linux gaming devices that double as desktop PCs. Plasma 6.8’s multi-monitor and display-management improvements further this trend, addressing real-world pain points for users who dock and undock laptops or work across several screens.

What to do now

Until Plasma 6.8 arrives in your distribution’s repositories, you can take several steps to tighten RDP security:

  • Lock manually before disconnecting. It’s a simple habit: press Super+L or your equivalent shortcut before closing the RDP client.
  • Review your RDP setup. Ensure you are using Plasma’s built-in server if you want the future automatic lock to work. Check your distribution’s documentation—some default to third-party servers.
  • Limit exposure. Use a VPN or SSH tunnel to access RDP rather than exposing port 3389 directly to the internet. Combine with strong, unique passwords or key-based authentication where possible.
  • Test the feature early. If you run rolling-release distributions or are willing to use the beta builds (first expected September 10, 2026), you can try the feature in advance and provide feedback to KDE developers.

Once Plasma 6.8 is installed, navigate to the remote desktop settings and enable the lock-on-disconnect option. If you administer multiple machines, consider deploying a configuration file that sets this option by default. Pay attention to how your workloads behave: the feature locks the session, not the screen, so applications continue running—exactly what most people want, but verify it doesn’t interfere with automated tasks that expect an unlocked desktop.

Outlook

KDE Plasma 6.8 is shaping up to be a release that refines the desktop’s credentials for remote work and professional use. Automatic RDP locking is a small, focused change, but it patches an obvious vulnerability and aligns Linux with the expectations of Windows users. Combined with smarter multi-monitor handling and a more scriptable display backend, Plasma is becoming increasingly viable for hybrid workstations that must play well with both local and remote sessions.

Keep an eye on the beta releases in September 2026; early testing often reveals edge cases that can influence the final October launch. For Windows shops dipping their toes into Linux desktops, these improvements make the cross-platform experience smoother—and safer. The era of leaving a Linux box unlocked after a remote session is, at long last, coming to an end.