Bug 279349

Summary: Mediate to the user why the filter panel is inactive
Product: [Applications] dolphin Reporter: S. Burmeister <sven.burmeister>
Component: panels: searchAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: mail, skreech2
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description S. Burmeister 2011-08-04 06:54:30 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

IF nepomuk + strigi are not available the filter panel is greyed out completely. The user can only guess why. There is nothing in the panel or connected to that bit of the GUI which hints to nepomuk/strigi.

Since the checkboxes etc. are disabled anyway and of no use they should be replaced by a notification  in case strigi is not enabled.

Instead of just showing a disabled panel, show a text or even a start button, i.e.:

"The search panel can only be used when nepomuk + strigi is enabled"

"Start Nepomuk + strigi" as button which opens the kcm or as text only: "If you want to enable nepomuk + strigi you can do so in KDE's systemsettings > Desktop search"

Reproducible: Always

Steps to Reproduce:
disable nepomuk+strigi
enable the filter panel

Actual Results:  
useless panel and no hint as to why

Expected Results:  
mediating why the panel is disabled and how to enable it
Comment 1 Roger Pixley 2011-10-03 03:11:44 UTC 
I find in KDE 4.7.1 though that even if I have them enabled I still do not get the panel ungreyed. I'm not sure that I've ever had it ungrey since that's been installed. Tried a few other people in other distros with varying levels of nepomuk and strigi enabled and none of them ever got it ungrey either.
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:18:41 UTC 
Resetting assignee to default as per bug #305719
Comment 3 Julian Steinmann 2019-06-14 10:40:24 UTC 
Closed in favor of the more up-to-date bug report 408680.

*** This bug has been marked as a duplicate of bug 408680 ***