Situation: 1. Baloo file indexer is disabled. 2. Start kinfocenter 3. Choose the "File Indexer Monitor" item => Console output: Error loading plugin "kcm_fileindexermonitor" "The shared library was not found." Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") The environment variable QT_PLUGIN_PATH might be not correctly set 4. Press the button "Start File Indexer" 5. Nothing happens but a console message "Baloo File Indexing has been disabled" Expected: Either enable the Baloo file indexing or show an appropriate message box or similar.
I have the same problem on openSUSE Tumbleweed (20160412) (x86_64) with Qt: 5.5.1 KDE Frameworks: 5.21.0 ~> kcmshell5 kcm_fileindexer Error loading plugin "kcm_fileindexermonitor" "The shared library was not found." Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") The environment variable QT_PLUGIN_PATH might be not correctly set fetched suspend state Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion KInit could not launch 'khelpcenter5'. ~> The File Indexer Monitor is fired up, but show only some button, as shown in the attachment. A "File Indexer Monitor" app is visible both in the application dashboard and krunner, but nothing happens. The "File Indexer Monitor" in KInfoCenter freezes the GUI for about a minute before showing it and there what it looks like a progress bar, but I'm not sure it makes sense, given the issues just described
This sounds a lot like a packaging problem you should take up with your distribution. Assuming the bug is still relevant at all.
On Tumbleweed 20191023 still the same error: ~ kcmshell5 kcm_fileindexermonitor org.kde.kcoreaddons: Error loading plugin "kcm_fileindexermonitor" "The shared library was not found." Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") The environment variable QT_PLUGIN_PATH might be not correctly set Could this still be a packaging error?
Oh I think I know what it is! It's not an error though is it? It's a warning... and everything works correctly, right?
Right, so, the plugin error is not really so much an error as it is a warning, and it means nothing for the KCM. It's entirely irrelevant here. (kcmutils supports two paths, if the first doesn't exist there's a warning about it failing to load the plugin, but then another path is tried anyway so that warning is moot) The actual indexer problem seems to be that baloo gets confused about its own state.
Moving to indexer component. The 'Start File Indexer' would do literally what the button says. It tries to start the file indexer process. The indexer will promptly quit again when it has been disabled via system settings. So, I guess, technically the button is correct. It never promised to enable the indexer first :'D I am not quite sure how to best deal with this. I would, perhaps, simply hide the KCM entirely when indexing is disabled. Alternatively the module could actually enable baloo first, but that somewhat impedes on the functionality of the systemsettings KCM. Or just display a "yo, baloo is disabled maybe enable it first in systemsettings" warning and offer no interaction at all, which is likely the cheapest option.
*** Bug 418867 has been marked as a duplicate of this bug. ***
This page is long dead, having had its UI moved to the search page in System Settings.