Registered Member
|
Hi guys,
sorry for opening this again, however I cannot help not to ask. In FAQ, there is following:
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:
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:
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.
|
Registered Member
|
And I am not sure if this is related, some of the errors from .xsession-errors:
Many of this sort:
Probably not an error, though it is spamming the error log a lot:
|
Registered Member
|
Today, it finished with a message: "Initial indexing of files for fast searching finished in 1 hour and 38 minutes".
|
Manager
|
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. |
Registered Member
|
Only Akonadi related in there as far as I can see. Nevertheless, I have cleared those too.
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. |
Manager
|
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 |
Registered Member
|
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. |
Registered Member
|
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. |
Administrator
|
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."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
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? |
Registered Member
|
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. |
Registered Member
|
Created a bug report: Bug #287712
|
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]