STEPS TO REPRODUCE 1. Run kcmshell5 autostart or kcmshell5 kdeconnect 2. Right-click on the task manager icon 3. Click "Start new instance" OBSERVED RESULT for kdeconnect nothing happens for autostart the error "The file or folder kcmshell doesn't exist" appears EXPECTED RESULT KCMs are inherently single-instance so it should not offer to launch a new instance in the first place. The same applies to systemsettings, which is also a single instance app SOFTWARE/OS VERSIONS Everything master
With https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1288 and https://invent.kde.org/plasma/kde-cli-tools/-/merge_requests/25 clicking "New instance" on a kcmshell window opens systemsettings with that KCM, which is a bit less broken than showing an error but is still quite odd
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1289
*** Bug 429428 has been marked as a duplicate of this bug. ***
Git commit c58e5433436393e2b437ccb34f375b5aacb6419c by Nicolas Fella. Committed on 25/12/2021 at 00:11. Pushed by nicolasfella into branch 'master'. [libtaskmanager] Prevent launching a new instance of services with NoDisplay=true It is not possible for the user to launch such an app from the UI, so we should not allow to launch a new instance from the task manager context menu. M +15 -0 libtaskmanager/tasktools.cpp https://invent.kde.org/plasma/plasma-workspace/commit/c58e5433436393e2b437ccb34f375b5aacb6419c