https://bugs.kde.org/show_bug.cgi?id=435202
--- Comment #15 from vaarti...@gmail.com --- After rebuilding the library with the explicit IP address network location, the same behavior exists. It is still attempting a ridiculous amount of CSC namespace create file operations, which fail. I do not have offline file caching enabled. Is there anything else you can think of to prevent digiKam from behaving this way? On Thu, Apr 1, 2021 at 4:00 PM Chris Poldervaart <vaarti...@gmail.com> wrote: > BTW.... Enable Offline Files was already disabled. > > On Thu, Apr 1, 2021 at 2:25 PM Chris Poldervaart <vaarti...@gmail.com> > wrote: > >> I have changed the mapped drive letter location for the collection >> folders to the explicit network mapping via IP address. I am currently >> rebuilding the database (re-scanning) and there are far fewer instances of >> CSC write attempts. I'll report back if that changes anything once that >> process is complete. >> >> >> On Thu, Apr 1, 2021 at 1:42 PM Maik Qualmann <bugzilla_nore...@kde.org> >> wrote: >> >>> https://bugs.kde.org/show_bug.cgi?id=435202 >>> >>> --- Comment #12 from Maik Qualmann <metzping...@gmail.com> --- >>> The "NAME NOT FOUND" messages come from Windows. The Windows offline >>> cache >>> ("C:\Windows\CSC") searches for files here. I think digiKam "hangs" when >>> accessing files over the Windows file API. The offline cache can be >>> deactivated >>> under Windows. >>> >>> Maik >>> >>> -- >>> You are receiving this mail because: >>> You reported the bug. >> >> -- You are receiving this mail because: You are watching all bug changes.
