Created attachment 112247 [details] screenshot of error in window I tried looking for the library that wasn't found, but Elisa gives no debug information even saying what the library is.
Okay I opened elisa using the terminal and looked at the output there. Here's the terminal output when I try opening "Configure Elisa": ``` org.kde.kcoreaddons: Error loading plugin "kcm_elisa_local_file" "The shared library was not found." Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/local/bin") The environment variable QT_PLUGIN_PATH might be not correctly set Error loading plugin: "The shared library was not found." ```
I found the file kcm_elisa_local_file.so in the build/bin directory of the unzipped source folder, created when I installed Elisa. I moved it to /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_elisa_local_file.so I then restarted Elisa and tried again. Here's the error message I got: "The service 'Elisa Local Files Indexer' does not provide an interface 'KCModule' with keyword 'kcm_elisa_local_file'" So the error message is different. Not sure what it is now. Could it be because I disabled Baloo on my system? Baloo wasn't a required package and it shouldn't interfere with the settings module for Elisa.
Another error message: this time from the terminal: ``` Error loading plugin: "The shared library was not found." This module has no valid entry symbol at all. The reason could be that it's still using K_EXPORT_COMPONENT_FACTORY with a custom X-KDE-FactoryName which is not supported anymore ```
(In reply to Nicholas Estrada from comment #3) > Another error message: this time from the terminal: > > ``` > Error loading plugin: "The shared library was not found." > This module has no valid entry symbol at all. The reason could be that it's > still using K_EXPORT_COMPONENT_FACTORY with a custom X-KDE-FactoryName which > is not supported anymore > ``` Could you please try the flatpak version (for example the nightly KDE builds https://community.kde.org/Guidelines_and_HOWTOs/Flatpak ) ? The support for loading the KCM configuration module requires that you configure some environment variables and that the support is installed in the expected way. I do not remember the details right now. This is why I ask you to tell with a flatpak build given that I know that the configuration module is properly packaged and displays correctly.
If you can provide the information requested in comment #4, please add it.
To further investigate this issue, KDE developers need the information requested in comment #4. If you can provide it, or need help with finding that information, please add a comment.
No response, changing status. If you have new information, please add a comment.