My $HOME folder is containing some symbolic links, pointing to folders in Truecrypt containers or network folders on samba shares. Content of this folders is not indexed and therefore not contained in search results.

I have tried xmlindexer $HOME. This program also does not crawl into the folders.

System: Kubuntu 11.04, strigi-daemon 0.7.2, KDE and Nepomuk 4.6.5

This sounds like a bug. Please file a bug on bugs.kde.org.

I would like to know, if this problem is also present for other KDE users.

In bugtracking system I found a controvert bug report: https://bugs.kde.org/show_bug.cgi?id=208602. In this bug report it was counted as a bug, that strigi is indexing also linked folders, seems this bug is solved and the solution has got a bug for me.

I don't establish a new bug report but would like to discuss it: Should strigi better avoid following symbolic links or should it better follow into linked folders?

I've got a solution for my problem.

For folders mounted otherwhere, but not im my $HOME, I have replaced the symbolic link with a hard link created through mount --bind command.

For the Truecrypt folders I moved the mountpoint into my $HOME and created some symbolic links to the location where I want to see the different folders contained in the Truecrypt.


Strigi is just crawling through these folders.

In Strigi/Nepomuk settings this should be improved. I can select folders connected through symbolic links but Strigi/Nepomuk ignores this selected folders.

I ran into this problem. I mount my Windows NTFS drive as /mnt/WindowsXPDrive and then have symlinks in my /home/$USER directory to My Documents, My Music, etc. in here. Even though these symlinks appear checked in System Settings > Desktop Search > Desktop index folders > Customize index folders… > Strigi Index Folders and I can navigate into subfolders to select and unselect them, Nepomuk/Strigi has never indexed their contents.

Mr. Trueg suggested the symlink might be my problem, so I think this is by design. The code in Nepomuk::IndexScheduler::analyzeDir() simply bails if a directory is a symlink. It seems complex to index symlinks and you could end up with endless recursion and other problems. However it would make it easier to manage indexing by just making symlinks to what you want to index instead of navigating checkboxes in Strigi Index Folders, so maybe someone should file an enhancement request bug.

I did file bug 287593 in System Settings': "“Customize index folders” must handle symlinks specially, as Nepomuk/Strigi doesn’t index them".

I think there's another bug that Dolphin should warn you when you Find [Content] [From here (some_dir)] when some_dir is not indexed.

I don't think these issues are documented anywhere, is userbase's Nepomuk article the right place

Yes it should be. Feel free to edit the wiki to add them.