Bug 279124 - nepomukstrigiservice reindexes all files after an indexing suspension.
Summary: nepomukstrigiservice reindexes all files after an indexing suspension.
Status: RESOLVED DUPLICATE of bug 278591
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 06:03 UTC by Alejandro Nova
Modified: 2011-08-03 12:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro Nova 2011-08-02 06:03:05 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

Strigi won't skip already indexed files if you suspend and resume file indexing. Instead, Strigi will reindex all files after the suspension,

Reproducible: Always

Steps to Reproduce:
1. Boot your computer. Strigi, accurately, indexes what need reindexing and skips the rest.
2. Unplug your computer, or trigger a file indexing suspension through nepomukcontroller.
3. Resume file indexing. Strigi will reindex all of your files.

This bug isn't in itself serious. It's the combo with the nepomukstorage memory leak what makes this bug damaging.

Actual Results:  
Every file is reindexed by Strigi.

Expected Results:  
Strigi only indexes files needing reindexing, using its own algorithms.
Comment 1 Alejandro Nova 2011-08-02 17:59:25 UTC 
This bug can be worked around by restarting nepomukserver after an indexing suspension.
Comment 2 Alejandro Nova 2011-08-03 12:16:53 UTC 
The same packaging issues also caused this.

Please, put this into the Release Notes.

*** This bug has been marked as a duplicate of bug 278591 ***