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

Nepomuk uses 100% CPU on 1 core in KDE 4.11

Tags: None
(comma "," separated)
User avatar
aljazek
Registered Member
Posts
13
Karma
0
OS
Hi. I recently upgraded Kubuntu 13.04 to KDE SC 4.11 and now I have problems with nepomuk.
Since the upgrade, I had to stop nepomuk server, delete the database and deselect/select folders, to reindex all folders.
After an hour it stopped at 6500files and now runs 100% CPU on one core for a few hours, without changing the number of indexed files.
What can be wrong or how to fix that?
User avatar
aljazek
Registered Member
Posts
13
Karma
0
OS
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Reporting a bug was the correct thing to do in this case as Nepomuk should not be trying to endlessly index a single file. If the process which is hung (and using 100% of CPU) is called "nepomukindexer" then you can safely kill this and Nepomuk should move on to the next file.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
aljazek
Registered Member
Posts
13
Karma
0
OS
Well, it doesn't. nepomukindexer again tries to index the same file. Only deleting the file helps. :-)
User avatar
google01103
Manager
Posts
6668
Karma
25
is there something unusual about the file? s


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
aljazek
Registered Member
Posts
13
Karma
0
OS
Yeah, that should be a presentation, but when I open it, there is over 300 pages of question marks and other nonsense. :-)
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Okay, from what I was aware after a certain number of crashes Nepomuk was supposed to give up and stop attempting to index the file. If you keep killing it does it eventually move on to another file or does it remain stuck?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
aljazek
Registered Member
Posts
13
Karma
0
OS
bcooksley wrote:Okay, from what I was aware after a certain number of crashes Nepomuk was supposed to give up and stop attempting to index the file. If you keep killing it does it eventually move on to another file or does it remain stuck?

It remains stuck, but Simeon Bird just commented:
Aljaz: thank you for reporting the bug, I have fixed it and the fix should be in 4.11.1
wotan
Registered Member
Posts
131
Karma
-2
OS
Are you sure that instead of reporting the bug, we should not reporting the name of the nepoumuk and semantic-desktop developer itself?
I am using kde since 4.6 now and from all this versions it never happened only one time that I upgrade the next version without having again the problem of 100% cpu + big loss in the semantic collections (recently when I make a search in tags:/ in dolphin, I will only see one and only file, but I will see it several times under the same tags... ;) )

I don't really think that the people that develop nepomuk are that bad. Hence if the results is so bad then it must mean that they simply don't want to be good, that they simply don't want to have the least commitment about the job they are doing. That they have 0.0% respect toward the community

I can agree on the fact that when one want to push a new features, it might be buggy for the first releases, but when it is 100.0% buggy and erratic years after years, at some point it makes sense to re-think the whole decision of adding the semantik-desktop burden.
This decision should be made in the light of
1) Does the community really have the wingspan and man power to develop such an ambitious project?
2) Is the expected gain in confort really higher than the actual burden and trouble it generates? I have never heard of someone using semantic desktop (and how could one use it, since it is not reliable at all) but I have always heard over the past years of people tired of virtuoso-t, nepomuk strigi etc....

Let me remind the developper (if by a miracle, they happen to get out of their own world and listen to the community) that an experimentale features does not have to be tagged released and end up in a package version of a distro. There is the git versions to do this. Moreover, as you know KDE is not a company, also no one has a superior that puts a deadline our work. There is hence no reason why a software would not be ready when released...


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell