https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #4 from IWBR <iwannaber...@gmail.com> --- I see. Don't worry about it. It's mostly a network problem. However, as I mentioned, due to the high latency, Digikam thinks the path is not available, although I can browse to that location using Ubuntu's file manager. Btw, checking for the availability of the trash is a smart solution. However, during those periods of "non availability", Digikam freezes the interface and Ubuntu constantly asks me to force close the app (related to bug #389652?). Not even a menu or a picture can be selected, even when Digikam is seemingly doing nothing. I understand if pictures couldn't be opened, but browsing catched thumbnails or opening menus should be possible even if the collection is momentarily non-available (considering the database is stored locally, of course). Maybe I should open a bug just for this issue? Anyway, I understand it's not Digikam's fault that it takes so long to scan new files on a remote location. It's just a bit annoying because the main interface is frozen during that process. Regarding the slow startup, even with new file scan disabled, yep, it can take several minutes even to show the splashscreen and the tray icon, and about 10-12 minutes to show the main interface in my case. Do you think something could be done in this regard? -- You are receiving this mail because: You are watching all bug changes.
