https://bugs.kde.org/show_bug.cgi?id=420939
--- Comment #49 from [email protected] --- (In reply to Scott from comment #48) > ... I have now discovered that some > files are indexed but do not display a duration. The following file appears > in the indexed list but there is no duration displayed... It's "video/mp2t", that's good news. Does it give a "Duration" if you look with "MediaInfo"? If it does... Try copying to your home directory, see if you can index it there and check the results of "balooshow -x" If it doesn't... It'd be a question of thinking back to ask "what is different" or "what did I do differently" with this one. Not going to be easy... > 5/ This seems to be your "red flag" > baloosearch -i "Battle of Jutland the Navys Bloodiest Day 2016".ts > f3f600000031 /mnt/pool/Entertainment/Documentaries/Movies/Battle of > Jutland the Navys Bloodiest Day 2016.ts > f8c500000031 /mnt/pool/Entertainment/Documentaries/Movies/Battle of > Jutland the Navys Bloodiest Day 2016.ts > Elapsed: 0.997359 msecs This looks "complicated"... Maybe bad news for your indexing. In each of your examples the "device Id" was 31(hex)/49(decimal). My worry was that was changing when you rebooted. What is strange is that the (supposed) "Inode" for the file _is_ changing. It may be that I've got this wrong, but it looks like it appears as: 63685(decimal) 70217(decimal) plus baloo has seen: f3f6(hex) - which is 62454(decimal) f8c5(hex) - which is the 63685(decimal) If these ID's are jumping round then baloo doesn't have a chance. You are looking at /mnt/pool/... and have a set of discs mounted behind it? Your original .config/baloofilerc mentioned /media/data/disk01, disk02, disk03 and so on... Maybe the "pool" doesn't keep inodes stable :-/ Try finding your "Battle of Jutland the Navys Bloodiest Day 2016".ts on the mounted discs (rather than on the "pool") and do a stat of it there... It'd be something like: cd /media/data/disk1/entertainment/Movies stat "Battle of Jutland the Navys Bloodiest Day 2016".ts The hope is that the device number/inode remains stable (and indeed stays the same when you reboot) -- You are receiving this mail because: You are watching all bug changes.
