Bug 315817 - file-indexer should not try to repeatedly re-index files
Summary: file-indexer should not try to repeatedly re-index files
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: fileindexer (show other bugs)
Version: 4.10.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Nepomuk Bugs Coordination
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-26 17:02 UTC by nickpantazis
Modified: 2013-06-08 17:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.11


Attachments
the requested mp3 (3.10 MB, audio/mpeg)
2013-03-01 10:45 UTC, nickpantazis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nickpantazis 2013-02-26 17:02:18 UTC
When leaving the pc idle for a while, it starts indexing as indicated by CPU-usage and the nepomuk status in system settings. The problem is that the displayed file name that is indexed, an mp3 file, is always the same and the indexer never progress to another file. It just uses 50% of CPU for ever.

Thank you.

Reproducible: Always

Steps to Reproduce:
don't know
Comment 1 Simeon Bird 2013-03-01 04:16:12 UTC
Is it possible for you to send us a copy of the problematic file?

Thanks
Comment 2 nickpantazis 2013-03-01 10:45:00 UTC
Created attachment 77661 [details]
the requested mp3
Comment 3 Simeon Bird 2013-03-04 01:39:01 UTC
Thanks! I can reproduce it breaking the indexing, and I'll have a look at fixing it. It also causes vlc to segfault on exit, which you might want to report to them separately.
Comment 4 Simeon Bird 2013-03-04 02:52:47 UTC
Hm, no, scratch that, indexing this file works fine for me (I had unrelatedly broken things).
What happens if you do:

nepomukindexer path-to-that-mp3-file

at a command line?
Comment 5 nickpantazis 2013-03-05 09:04:37 UTC
No problem is reported back in the command line if I run nepomukindexer '/home/...mp3'
I tried --clear and then I run the command again.

The bug still exists for me.
Comment 6 nickpantazis 2013-03-05 10:11:11 UTC
I moved the file into a non-indexed folder
I restarted the PC, and then I moved the file back in to it's original location.
Now the problem seems to be gone away.
Comment 7 Simeon Bird 2013-03-06 01:07:17 UTC
Interesting... given that you seem likely to be using non-latin characters somewhere, I wonder if this was bug 305903? Moving the file probably updated the encoding and made everything work.
Comment 8 nickpantazis 2013-03-06 10:30:55 UTC
My system encoding in UTF-8. I moved the file to a ntfs partition and then back to ext4. I have many files with non latin (Greek) characters that caused no problems to the file indexer.

I believe there should be an internal check within fileindexer to skip files that are indexed for many minutes.
Comment 9 Simeon Bird 2013-03-06 16:54:46 UTC
Yes, you're right. Ideally there should also be some way for the user to see a list of files that were not indexed correctly. I'll leave the bug open until we implement that.