Nepomuk indexing excluded sub-directories (mountpoints for sshfs mounts)

Bug #584341 reported by James Sams on 2010-05-22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kdebase-runtime (Ubuntu)
nepomuk-core (Fedora)

Bug Description

Binary package hint: virtuoso-nepomuk

I've found Nepomuk to be indexing sub-folders in my home directory that I un-clicked in the Nepomuk interface. When I go to the configuration, the folders are still unselected and greyed-out, indicating that Nepomuk should know that it should not index those folders.

I discovered this when I noticed sshfs taking up an aberrant amount of memory and CPU, which continued after I closed all applications that I knew to be using those mount points. Running 'lsof' on the mounted folders listed only nepomuk as using them. Suspending File Indexing via the System Tray icon resolved the memory/CPU problems with sshfs, and nepomuk did indeed release the files in the folder. When restarting the file indexer, I found nepomuk to be back to indexing those folders.

My system is straight install of Kubuntu, using 64bit Lucid, upgraded from Karmic, using 6.1.0-0ubuntu3 of virtuoso-nepomuk (I couldn't find any other packages on my system that may have been providing nepomuk, apologies if that is overly specific). The specific binary that was 'nepomukservicestub' being run (according to ps aux) as:

/usr/bin/nepomukservicestub nepomukstrigiservice

Obviously, I would expect folders that I unselect through the folder interface to not be indexed or even touched by nepomuk, at all.

affects: virtuoso-opensource (Ubuntu) → kdebase-runtime (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kdebase-runtime (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers