Audit/port usages of kcmshell5
Open, Needs TriagePublic

Description

In various applications we use the kcmshell5 executable to open KCMs.

This is problematic for several reasons:

  • Typically we want to open KCMs in systemsettings instead of a standalone window (not always though)
  • kcmshell5 comes from kde-cli-tools (i.e. Plasma) 5. It's not good when apps depend on that
  • It can only open Qt5-based KCMs
  • For KF6 there's kcmshell6 from kcmutils, which only works with Qt6 KCMs

We need to go over each usage and determine what the relevant compatibility constraints are and do something about it

There may also be cases where we prematurely ported to kcmshell6 and we need the ability to open a Qt5-based KCM. This could happen e.g. when running a KF6-based app in Plasma 5 (assuming that's a supported case at all)

We have plasma-open-settings as an agnostic tool to open systemsettings/plasma-settings with fallbacks to kcmshell.