In short
KDE has introduced a new utility, `kscreenctl`, for managing screens, and has implemented automatic locking of remote sessions. Let's take a closer look at what this means for those who use KDE on servers and remote desktops.
Two features have been added to KDE that have long been requested by users who rely on the desktop environment not only on their laptops at home: the kscreenctl utility for managing screens from the command line and automatic locking of remote sessions.
kscreenctl is a CLI interface to the KScreen subsystem. Until now, configuring monitor layouts, modes, and output priorities was mainly done through the GUI, which is inconvenient for scripts, auto-login, and headless scenarios. The new utility fills this gap: screen configurations can now be defined declaratively and applied without having to manually click through System Settings.
The second change—automatic locking of remote sessions—addresses a more serious issue. Previously, screen locking in KDE was triggered by a timer regardless of whether the session was local or remote. This meant that a session via VNC or RDP could remain unlocked if the local timer did not function correctly in the context of a remote connection. Now, remote sessions lock automatically, reducing the risk of leaving the desktop unlocked if the connection is lost.
Both fixes are minor, but they demonstrate that KDE continues to improve its infrastructure—where a GUI was previously lacking, there is now a proper CLI and a well-thought-out security policy for remote work.