Kevin Kofler wrote: I can now log in again and dolphin and gwenview are back. I think it is all ok again. Thanks. Would you please clear up some confusion for me: is sesame2 or virtuoso a nepomuk backend? Do I need both? In order to do the update you suggested above, I had to uninstall soprano-backend-sesame2, so I now only have virtuoso-opensource (which seems to be working fine, I presume). It seems to me that having only virtuoso and no sesame2 worked fine, but adding sesame2 and everything fell apart.

Benjamin K. Stuhl wrote: That is good to hear. Virtuoso appears to be indexing very well at this end and regularly checks every time I log in, it seems. There is quite a large data base. It is cooperating with strigi and both daemons run and I have no problems with them (except for the unfortunate issue of yesterday with sesame2). They even work on my laptop without issue, except that it is not quite powerful enough, so it disables compositing while indexing. The problem: I read the article that the aforementioned link points to, but whenever I type anything into the search field in Dolphin, the nepomuk selectors appear, as both described and illustrated, but the search button remains dimmed and I cannot ever perform any search or use the nepomuk database in any way whatsoever! Also, there was supposed to be some way to use krunner (F2) to do searches, but I have the same problem: type anything and nothing happens. All that indexing is for nought. Is there no way I can meaningfully access it yet?

2010/2/16 Petrus de Calguarium <kwhiskerz(a)gmail.com&gt;: It works yes. But very very slow? It was only 3 seconds and it found everything here. So it depends on a few things ;) -- LG Thomas Dubium sapientiae initium

Martin Kho wrote: Right, Rawhide also had the offending 2.4.0, so of course Rawhide was also affected by the exact same issues. Kevin Kofler

2010/2/12 Paul Scott <paulsscott(a)gmail.com&gt;: Quite interesting. I get the following when i try to start kontact: <unknown program name>(1897)/: Communication problem with "kontact" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " But that's not a workaround here. Killing the kontact process and starting kontact again results in the same error. I use "on login start with an empty session" all the time. -- LG Thomas Dubium sapientiae initium