since I updated to 12.1 I thought I would give Stringi/Nepomuk a new chance. Up to now it was always the first thing I disabled (at least in 11.4, but also in 11.3 if it existed then).
The good news is that, plasma no longer crashes when it is enabled, contrary to my prior experience. However, it is indexing my /home directory the whole day and shows a database size of 1GB and 53.000 files (and growing). First of all, I hardly imagine that I need all these files indexed. Moreover, this is a working laptop where HD space is a valuable asset. But what concerns me most is that the laptop fan has not stopped rotating the whole day.
Is this going to stop, once it has finished indexing for the first time (probably in a week or so), or will I have to disable it once again?
Is this massive database, which as far as I thought should only contain metadata, normal, or should I be afraid there is some kind of leak?
Does anybody of you, actually use Stringi/Nepomuk and see’s some added value in it? Meaning: Do you think it is worth the trouble (and space)?
Depending on what it really is supposed to do, is there a way to limit the directories it indexes?
Thank you for providing me enlightenment , and for your thoughts and suggestions on the above.
Nikos.
First thing I disabled, but strangulation would be better. There was even a hidden icon for “Nepomuk File Indexing” in my system tray, but it said “Service not running” so I closed it with Quit.
>
> Hello community,
>
> since I updated to 12.1 I thought I would give Stringi/Nepomuk a new
> chance. Up to now it was always the first thing I disabled (at least in
> 11.4, but also in 11.3 if it existed then).
>
> The good news is that, plasma no longer crashes when it is enabled,
> contrary to my prior experience. However, it is indexing my /home
> directory the whole day and shows a database size of 1GB and 53.000
> files (and growing). First of all, I hardly imagine that I need all
> these files indexed. Moreover, this is a working laptop where HD space
> is a valuable asset. But what concerns me most is that the laptop fan
> has not stopped rotating the whole day.
>
> 1. Is this going to stop, once it has finished indexing for the first
> time (probably in a week or so), or will I have to disable it once
> again?
> 2. Is this massive database, which as far as I thought should only
> contain metadata, normal, or should I be afraid there is some kind of
> leak?
> 3. Does anybody of you, actually use Stringi/Nepomuk and see’s some
> added value in it? Meaning: Do you think it is worth the trouble (and
> space)?
> 4. Depending on what it really is supposed to do, is there a way to
> limit the directories it indexes?
>
> Thank you for providing me enlightenment , and for your thoughts and
> suggestions on the above.
> Nikos.
>
>
i’m actually using it, quite happily at the moment. i limited the area to
be indexed, excluding what doesn’t make sense to me, and initial indexing
finises in a few hours.
i’m not using a notebook and living in a tropical climate, so my fans keep
running anyway. otherwise performance isn’t affected by indexing – with 4
CPU cores & 8 GB RAM; might be different with more economic configurations.
since KDE 4.7.3 i noticed that searching via dolphin does return useful
results, so i’m actually using it now & then.
For me I have the Nepomuk enabled & configured the Strigi to only index my Docs, Pictures, Videos, & Music.
One can do that by doing this
Kickoff>Configure Desktop>Desktop Search
1)then checked the Enable Nepomuk Box
2) Clicked the Desktop Query tab
3)clicked where it says Custom Index Folders
4)In the box that shows up checked the boxes of what I wanted indexed unchecked the ones I didn’t
5) clicked OK Then Apply
Now it works great!
Here’s a How To use it video Desktop Search - Nepomuk Strigi & Faceted Browsing - Kubuntu 10.10 - YouTube
Thank you all!
I decided to firstly limit the folders that are indexed significantly and give it another week or so to see if it inhibits performance, and if I actually use it.
It would be interesting to know how that goes. Perhaps you could post back here in a week or so with some comment re performance etc. It might help other users facing the same issue.
What did this plasma crash look like? Did it rip up your desktop icons like a shark attack, sometimes scrambling text pixels so it looks like unknown languages?
This and another issue where we get kicked out to the login randomly are something I’m looking into and attempting to compile out of my own kde (4.6.0 still).
Or does your ‘plasma crash’ do something different.
Thanks for this post and also for the comments from others.
It was the “standard” black backround and a typical KDE message “sorry apllication plasma crashed…”. It is at least six months since the time I tried this last time so forgive my ambiguity as I recall this message from memory. But I think you get the point.
As for the feedback I promised: Once the initial indexing finished, there is no obvious impact on performance and the fan has stopped annoying. With regard to usability, I tried it twice. It actually found the files I were looking for, but I was to stupid to see where the files it found are supposed to be located (Since I did not search these files to test Nepomuk, but I really needed them fast, I did not push it a lot though).
With regard to usability, I tried it twice. It actually found the files I were looking for, but I was to stupid to see where the files it found are supposed to be located
Ok, this was embarrassingly simple, just rightclick and tick path…
> As for the feedback I promised. Once the initial indexing finished,
> there is no obvious impact on performance and the fan has stopped
> annoying. With regard to usability, I tried it twice. It actually found
> the files I were looking for, but I was to stupid to see where the file
> it found is supposed to be located (Since I did not search these files
> to test Nepomuk, but I really needed them fast, I did not push it a lot
> though).
dolphin doesn’t show the file path by default. if you enable that, you’ll
see where the files have been discovered.
