https://bugs.kde.org/show_bug.cgi?id=496378
--- Comment #3 from backu...@yahoo.com --- I appreciate the reply. (In reply to caulier.gilles from comment #1) > Did you have this folder open in an external Windows application ? Typically > Windows can lock access to directories in special cases. It's just a regular folder with sub-directories and jpg files in those. Every image viewer except digiKam shows the folder contents. digiKam can't even find the sub-directories. > Another possibility: anti-virus active in background? No, I run a pretty clean system by focusing on comprehensive firewall and only run anti-virus to vet new downloads or when I'm not working (never in the background to keep my system fast). I'm also noticing that `digikam.exe` will never leave the task manager as a "background process" after manually shutting down the digiKam. Is there a folder size limit when digiKam just decides not to do anything? My main photo directory is 100GB. I did give digiKam 6 hours to vet it earlier today. But periodic checking of windows task manager shows digiKam doing nothing at 0% CPU use. I got it working 1. I noticed that a completely different directory would work as expected and show thumbnails 2. I completely deleted the digiKam database (a shame since I had almost 900MB of thumbnails already cached and lots of ratings saved. But it still wouldn't work even after deleting the DB. 3. Stepping up the effort:I renamed my photo directory to something else, deleted the database again, chose a new directory location for the database, deleted all .dtrash folders, renamed my main photo directory back again. 4. digiKam is now recognizing the sub-directories inside the defined Collection folder. Progress! But I'll have to see how long before any thumbnails show up. I think I'll change my tact on how I define Collections. Seems like digiKam can't really handle large collections. (In reply to Maik Qualmann from comment #2) > Based on previous reports, I suspect a defective hard drive. Please check > your hard drive. Nothing else seems weird on my computer. But I take potential hard drive failures seriously. How do you recommend checking the hard drive? It's a relatively new Samsung SSD 980 PRO 2TB -- You are receiving this mail because: You are watching all bug changes.
