+++ This bug was initially created as a clone of Bug #248621 +++

Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

Recently upgraded to KDE 4.5 and finally decided to let Strigi and Nepomuk run.  After about 15 hours, Strigi finally finished indexing my files, and the search bar in Dolphin actually appeared to work instead of crashing constantly... huge improvement over the last 2 years of intermittently trying to use these things.
   
   Then I made the fatal mistake of rebooting my computer (yes it happens even in Linux, and this was to apply the kernel updates regarding the recent security bugs).   After rebooting, strigi decides that the existing 1.3 Gigabyte database that worked fine and was (as far as I can tell) cleanly closed out prior to a clean reboot is useless, and begins indexing every file again.  Strigi acknowledges the fact that there is a 1.3 Gigabyte index in the progress window, but apparently it doesn't trust the files from the previous boot and will not recognize any files that are already in the index.

   I double checked Dolphin and all searches that were working fine before now return nothing as the rest of Nepomuk also ignores the existing index data that it spent the better part of a day assembling.

   Looks like Nepomuk & Strigi are being turned off again.. maybe they will kinda sorta work for KDE 4.6.

Reproducible: Always

Steps to Reproduce:
1. Let strigi run (to completion).
2. Reboot
3. Strigi will intentionally ignore the existing index and start over from scratch.