Bug 223294

Summary: wish: don't notify that strigi is stopped to save resources
Product: [Unmaintained] nepomuk Reporter: Diederik van der Boor <vdboor>
Component: generalAssignee: Sebastian Trueg <sebastian>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: user581, w.richert
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Diederik van der Boor 2010-01-18 16:07:05 UTC 
Version:           onbekend (using 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)) "release 212", KDE:KDE4:Factory:Desktop / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.8-0.1-desktop

Strigi started indexing my system for the first time. From time to time I got notifications that strigi was stopped to save resources. Could this notification please be disabled by default?

Bottom line: I don't care _when_ my files are getting indexed, as long as they eventually will be. I'd rather expect the system to behave like this:
- First time indexing could take some time, so it could be possible some files don't show up yet. Completion status can be requested by the user, notifications are not needed.
- Each time a new file is created/saved, it will be queued for update in the index (this is what spotlight does, and what makes files appear instantly there). So no notifications are needed either.
Comment 1 Willi Richert 2010-03-01 14:19:38 UTC 
The same happens with my KDE 4.4beta: Strigi/nepomuk disables itself after a while due to limited resources.

Trueg at #strigi assumes that this bug is related to KDE's battery handling.
Comment 2 Kubuntiac 2011-10-06 00:47:27 UTC 
This is a duplicate of bug #200991

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