Summary: | after last update of virtuoso, search in kmail 2 stops | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Sérgio Basto <sergio> |
Component: | general | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | critical | CC: | bladud, lindsay.mathieson, me, rdieter |
Priority: | NOR | ||
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sérgio Basto
2012-02-22 17:12:33 UTC
virtuoso was taken 100% of one cpu , after that I read some where , that kde team Had found and fix a giant bug on Virtuoso , since Virtuoso update , yeah doesn't take 100% of one core , but nepomuk/kmail 2 stops do search , don't know if it is related. I can give any information about my system if you need it to debug. after virtoso update and reboot, appears that message: Nepomuk Semantic Desktop needs the Virtuoso RDF server to store its data. Installing the Virtuoso Soprano plugin is mandatory for using Nepomuk. which appears again today , since this message kmail 2 search stops to work. search doesn't work at all , automatic completion also doesn't work . I have some pop3 accounts and about 2.4G of email I try debug the problem following: http://kdeatopensuse.wordpress.com/2011/11/09/debugging-nepomukvirtuosos-cpu-usage/ I setting memory use to max , 1000 kbytes , but now I have the inverse problem of virtuoso , before virtuoso doesn't stop for a long time , now stops after a few time . So the best solution was disable nepomuk, at least I have much less cpu load Hi, After update update Fedora 16 , which have the new kde 4.8.1 the things looks better , Serach by folder appears and ask for enable nepomuk , I had enabled and now 3884 sergio 39 19 1901m 624m 3724 S 203.9 16.3 1906:42 virtuoso-t virtuoso-t consumes 200% of CPU and use 624m but doesn't seems to stop , I enable it at Sunday And still not search on body of messages ... Does whatever wasn't working work with kde 4.10? I'm closing this bug as "RESOLVED - WAITINGFORINFO" as we haven't heard back in over a year. Please feel free to reopen this bug if you encounter this issue again. |