Version: 4.7 (using KDE 4.7.4) OS: Linux Sorry we are a bit fed up with the whole thing. kmail2 search stops again read all messages in thread 'Searching x 2' http://lists.kde.org/?t=132777727500003&r=1&w=2 Reproducible: Always Steps to Reproduce: update kde , Actual Results: search on kmail and on compose messages search in address book stops again ! Expected Results: have search in kmail2 and autocomplete in compose messages. Fix it ASAP , and stop develop anything else , try debug your code before put your code in stable repos . Major , this bug cause many problems for who use stable versions. and mind lost .
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.