This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Nepomuk reindexing everything after restart

Tags: None
(comma "," separated)
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
Hi guys,

sorry for opening this again, however I cannot help not to ask. In FAQ, there is following:

Q. Nepomuk re-indexes files at startup.

A. This bug has been fixed in 4.7.0 versions. Now Nepomuk just "scans" for changes, without indexing anything.

I am running on KDE 4.7.3 (Arch Linux) and everytime I restart my computer, the Nepomuk tray icons pops up, it says "Indexing files for fast searching. This process may take a while." and goes through my home again. When I hover over the tray icon, the tooltip says:

Search Service: Strigi is currently indexing files in folder ...

To me, this looks like it is not looking only for changes. Also, this process takes at least couple hours.

Is this a correct behavior?

ps aux | grep nepomuk:
kdeinit4: nepomukserver [kdeinit]
/usr/bin/nepomukservicestub nepomukstorage
/usr/bin/akonadi_nepomuk_calendar_feeder --identifier akonadi_nepomuk_calendar_feeder
/usr/bin/akonadi_nepomuk_contact_feeder --identifier akonadi_nepomuk_contact_feeder
/usr/bin/akonadi_nepomuk_email_feeder --identifier akonadi_nepomuk_email_feeder
/usr/bin/nepomukcontroller -session 10cdd4d369000131336127600000015340031_1320781165_466802
/usr/bin/nepomukservicestub nepomukstrigiservice
/usr/bin/nepomukservicestub nepomukfilewatch
/usr/bin/nepomukservicestub digikamnepomukservice
/usr/bin/nepomukservicestub nepomukqueryservice
/usr/bin/nepomukservicestub nepomukbackupsync

I have recently removed all files related to Nepomuk, Strigi and Akonadi just to make sure that this is not related to an old config or something like that (recently = 4.7.x timeframe).

Also note that I am using Virtuoso 6.1.3.

Thanks.

Last edited by jirik on Wed Nov 09, 2011 2:35 am, edited 1 time in total.
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
And I am not sure if this is related, some of the errors from .xsession-errors:
[/usr/bin/nepomukservicestub] "/usr/bin/nepomukservicestub(1530)" Soprano: "Invalid argument (1)": "Unknown protocol '' encountered in efuaj"

Many of this sort:
[/usr/bin/nepomukservicestub] "/usr/bin/nepomukservicestub(1530)" Soprano: "Invalid argument (1)": "Cannot set values for abstract property 'http://www.semanticdesktop.org/ontologies/nfo#bitsPerSample'."

Probably not an error, though it is spamming the error log a lot:
[/usr/bin/nepomukservicestub] nepomukstorage(1530) Nepomuk::Sync::ResourceIdentifier::identifyAll: 3
[/usr/bin/nepomukservicestub] nepomukstorage(1530) Nepomuk::Sync::ResourceIdentifier::runIdentification: "select distinct ?r count(?p) as ?cnt where { ?r ?p ?o. filter( ?p in (<http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#hashAlgorithm>,<http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#hashValue>) ). optional { ?r <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#hashAlgorithm> ?o0 . } . filter(!bound(?o0) || ?o0="SHA1"^^<http://www.w3.org/2001/XMLSchema#string>). ?r a <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileHash> . optional { ?r <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#hashValue> ?o1 . } . filter(!bound(?o1) || ?o1="b9debf9c39852a5893b949e9e5fe60de75c14138"^^<http://www.w3.org/2001/XMLSchema#string>). filter( bound(?o0) || bound(?o1) ) . } order by desc(?cnt)"
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
Today, it finished with a message: "Initial indexing of files for fast searching finished in 1 hour and 38 minutes".
User avatar
google01103
Manager
Posts
6668
Karma
25
when you removed relevant folders did you clear those in ~/.local/share also?

have you looked for existing bugs @ bugs.kde.org for post 4.7.0 releases? If none found I would file a bug report, if found I would confirm it as a bug and vote.


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
google01103 wrote:when you removed relevant folders did you clear those in ~/.local/share also?

Only Akonadi related in there as far as I can see. Nevertheless, I have cleared those too.

google01103 wrote:have you looked for existing bugs @ bugs.kde.org for post 4.7.0 releases? If none found I would file a bug report, if found I would confirm it as a bug and vote.

I did a quick search and found nothing. Also, a couple of weeks ago, I read on Sebastian Trueg's blog that this probably should not be happening on 4.7.x. I was hoping that somebody here might know more before I go to report it.
User avatar
google01103
Manager
Posts
6668
Karma
25
In your ~/.kde[4]/share/config/nepomukstrigirc file is the the the "first run=" option false?

Didn't thin the ~/.local/share/Akonadi would matter just that you cleaned up all the other Akonadi so figured may as well get it all


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
google01103 wrote:In your ~/.kde[4]/share/config/nepomukstrigirc file is the the the "first run=" option false?

Interesting, it says true. Even though, it said that the indexing was finished (as shown in my previous post). This could be a bug, I suppose. I will log out and change it to false. Thanks for help. If it does not revert, I will mark this thread as completed. Either way, I will file a new bug.
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
Ok, so now it does not start with the Start indexing... notification, however it is still taking a long time to (re)index everything again. This might be however related to keeping the database up to date between sessions.

And behold, first run reverted back to yes.
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
Although it happens to "seem" reindexing, it isn't. I thought I had the same problem and helped by Sebastian Trueg, I found out that it wasn't the case. Why the icon there, then? It's because at first start Nepomuk can't tell if a file has been modified or not, then it scans it, but without reindexing it.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
Well, suppose you are right. Shouldn't then the first run property in nepomukstrigirc config file be equal to false after it finishes the first run?

Could this be related to the Unknown protocol error I mentioned in my second post?
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
jirik wrote:Could this be related to the Unknown protocol error I mentioned in my second post?


Just to add, https://bugs.kde.org/show_bug.cgi?id=278593.

Therefore, probably not related, however I am not sure. Most of these Unknown protocol errors were happening on c/c++ files.
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
Created a bug report: Bug #287712


Bookmarks



Who is online

Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]