I want to know so that I can use dnf5 provides on its literal path (because the KDE Plasma Mobile Spin doesn’t include it, rendering kinfo useless). Usually, I’d use command -v to resolve it, but I don’t think they’re in $PATH (kcmshell6 is, instead).
I’m unfamiliar with the FHS, so is there a reason you expected them to be in /usr?
Additionally, how’d you find them, inside /usr? Perhaps I’m incompetent at RegEx, but I find Dolphin’s Baloo-reliant search fairly inconsistent, and KFind’s rather poor at fuzzy searches.
Irrespective, although useful, I expected that directory to contain whatever supplies kcm_about_distro, but don’t see a relevant .so file (I grep’d to ensure):
The * is a wildcard character. -type f tells find to search only for files, not directories.
KInfoCenter is a separate program, not a KCM. It is a viewer to display KCMs specific to system information. Each entry on its left sidebar is a separate KCM.
Once you find the relevant KCMs you want, you can start them using kcmshell6:
And even KCMs which are hidden in System Settings, such as the background services one:
$ kcmshell6 kcm_kded
Notes:
The shell starting with # means you should run that command as root, or prepend sudo to it.
I use openSUSE Tumbleweed, if you are on a different distro the KCM names might be different.
Anyway, once you find the ones you are after, you can call as kcmshell6 ..., without the .so extension.
On a different distro, the kcmshell6 viewer program, might be named differently. You can try just kcmshell in case kcmshell6 is not found.
Regarding why searching the /usr directory. I am also not an expert on FHS, but what I know is that /usr is where binaries and libraries live, /etc is where configuration lives, and /var where data lives. Take this as an oversimplified outline.
I’m familiar with kcmshell6, but its architecture somewhat eludes me, for where is kcm_about-distro if not in /usr/lib64/qt6/plugins/plasma/kcms/systemsettings/? Is it perhaps part of KInfoCenter, and thus stored elsewhere?
As I wrote this, the incredibly intelligent idea of just… going up a directory came to me. Indeed, the relevant .so is right there: