https://bugs.kde.org/show_bug.cgi?id=359159
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|hubn...@gmail.com |stefan.bruens@rwth-aachen.d
| |e
Summary|File Indexer Monitor: |Start File Indexer starts
|"Start File Indexer" button |disables file indexer. No
|has no effect |way to enable.
Component|general |File Indexer Monitor
--- Comment #6 from Harald Sitter <sit...@kde.org> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
