I use Kubuntu 13.04.
Those features were just fine few days ago, then I upgrade to KDE 4.11 and also uninstall "transmission-common", somehow the package of "nepomuk-core" was uninstalled when I use "apt-get autoremove", that's when everything started to get abnormal.

I reinstalled nepomuk-core, but it didn't work very well, the RecentDocuments Folder stopped updating, and Nepomuk icon missed in the system tray, and when I try to use 'Find' in Dolphin, it showed nothing.

I try to to start nepomukserver manually, it gives this output:

Code: Select all

DBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
"/org/freedesktop/UDisks2/drives/ST9500325AS_6VEYNG6A" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Generic_USB2_2e0_CRW_20100201396000000" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/MATSHITADVD_RAM_UJ8B1AS_SPB2408900" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/MATSHITADVD_RAM_UJ8B1AS_SPB2408900" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/MATSHITADVD_RAM_UJ8B1AS_SPB2408900" : property "Device" does not exist
"/org/freedesktop/UDisks2/block_devices/sr0" : property "Name" does not exist
"/org/freedesktop/UDisks2/drives/ST9500325AS_6VEYNG6A" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/ST9500325AS_6VEYNG6A" : property "Device" does not exist
"/org/freedesktop/UDisks2/drives/ST9500325AS_6VEYNG6A" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Generic_USB2_2e0_CRW_20100201396000000" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/MATSHITADVD_RAM_UJ8B1AS_SPB2408900" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/MATSHITADVD_RAM_UJ8B1AS_SPB2408900" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/MATSHITADVD_RAM_UJ8B1AS_SPB2408900" : property "Device" does not exist
"/org/freedesktop/UDisks2/block_devices/sr0" : property "Name" does not exist
"/org/freedesktop/UDisks2/drives/ST9500325AS_6VEYNG6A" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/ST9500325AS_6VEYNG6A" : property "Device" does not exist
nepomukindexer(16045)/nepomuk (strigi service): "SQLExecDirect failed on query 'sparql insert { graph <nepomuk:/ctx/1b8ae24b-49ef-40de-a85a-4332f921890b> { <nepomuk:/res/a068d5e1-46a5-4076-842c-5ecea9246fb9> nie:plainTextContent "4132\n0\n0\n1234\

... ...


(iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SR172: Transaction deadlocked)"


Working on this for a few days, still not get a solution, anyone can help?

The message below indicates that there is either problems with the Virtuoso database used by Nepomuk to store it's data, or it has hung - requiring you to restart Nepomuk (easiest way would be to logout and back in again).

Code: Select all

(iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SR172: Transaction deadlocked)"

Have you logged out/back in or rebooted since encountering this issue?

Yes, I have logged out and in, also rebooted the system many times,
I even reset the database of virtuoso, deleted everything under ~/.kde/share/apps/nepomuk/repository/

Funny thing,
I created another account under kde, logged in, and the desktop search seemed working just fine, but still the "Recent Documents" not working.

Given that clearing the Nepomuk data repository did not help, could you try moving all the Nepomuk associated configuration files (located at ~/.kde4/share/config/ or ~/.kde/share/config depending on your system) elsewhere? Only those files beginning with nepomuk* should be moved, as all other KDE applications also store their preferences there as well.

Thank, that seems fix the desktop search feature for me, still not bring the recent document back.

But somehow, I find there is a folder named applnk under ~/.kde/share/, it store all the files and applications have recently been used, made a soft link to ~/.kde/share/apps/RecentDocument/, and Problem Solved.

metalbrick wrote:But somehow, I find there is a folder named applnk under ~/.kde/share/, it store all the files and applications have recently been used, made a soft link to ~/.kde/share/apps/RecentDocument/, and Problem Solved.

I just now discovered that I have the same problem, apparently since upgrading to 4.11RC1 according to the file dates in ~/.kde4/share/apps/RecentDocuments/ and ~/.kde4/share/apps/applnk... (I have used 4.10.5 before that)

So I guess this warrants a bug report...

Hmm - where is this Recent Documents functionality you are referring to exactly?
It shouldn't be necessary to symlink from ~/.kde4/share/applnk/ to ~/.kde4/share/apps/RecentDocuments/

bcooksley wrote:Hmm - where is this Recent Documents functionality you are referring to exactly?

In the kickoff menu, on the "Recently Used" tab.

It shouldn't be necessary to symlink from ~/.kde4/share/applnk/ to ~/.kde4/share/apps/RecentDocuments/

Yeah. That seems to be a bug/regression in 4.11... (recently opened documents apparently are now saved in ~/.kde4/share/applnk/ instead of ~/.kde4/share/apps/RecentDocuments/)

That is not normal behaviour - if it also occurs under a new user, please file a bug report, as the change of location should be reversed (saving in applnk is incorrect and wrong).

bcooksley wrote:That is not normal behaviour - if it also occurs under a new user, please file a bug report, as the change of location should be reversed (saving in applnk is incorrect and wrong).

Yes, it also occurs for a new user.

Bug filed: https://bugs.kde.org/show_bug.cgi?id=324110

I hope that was the right component...

wolfi323 wrote:Bug filed: https://bugs.kde.org/show_bug.cgi?id=324110

So apparently this is already fixed in git (the fix should be in 4.11.1):
https://projects.kde.org/projects/kde/k ... 6a518903c1

I will compile kdelibs with this patch and report back if it works for me then...

wolfi323 wrote:I will compile kdelibs with this patch and report back if it works for me then...

Yes, that commit fixes this issue for me.

So I guess this thread could be marked as "solved"...

Topic has now been marked as solved - thanks for posting the commit link and performing the confirmation test.