[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [nepomuk] [Bug 321796] New: Indexer passive (with a clean db at least)
From:       Hrvoje Senjan <hrvoje.senjan () gmail ! com>
Date:       2013-06-30 15:54:24
Message-ID: bug-321796-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=321796

            Bug ID: 321796
           Summary: Indexer passive (with a clean db at least)
    Classification: Unclassified
           Product: nepomuk
           Version: git master
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: grave
          Priority: NOR
         Component: fileindexer
          Assignee: nepomuk-bugs@kde.org
          Reporter: hrvoje.senjan@gmail.com
                CC: nepomuk-bugs@kde.org

So, again cleaned the db. This now is something i noticed few weeks ago, but
somehow forgot to report. 
1) fileindexer seems to have lesser priority than e.g. akonadi_nepomuk_feeder
2) it appears to index only new/changed files -> e.g. touch a.txt will index
the file, but if the file was there already, it wouldn't be indexed. Or, e.g.
songs get indexed only after they start playing in clementine

Reproducible: Always

Steps to Reproduce:
1. Clean the db, re-login/restart nepomuk

Actual Results:  
Indexed:
Files: 3
Emails 20100
running for couple of hours at least. Files appeared only after i turned of
akonadi.
Usually i would have at least 15000, 20000 files

Expected Results:  
All files in checked dirs should be indexed in that time

Let me know what info is needed. This isn't again that recursive thing, as when
one creates files in further subdirs, they get indexed. Same results w/ & w/o
filewatcher.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]