[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #24 from Maik Qualmann --- Git commit d472489b5457710d44c83ed6bac61c795e607646 by Maik Qualmann. Committed on 25/04/2024 at 19:18. Pushed by mqualmann into branch 'master'. show an error icon if the collection/album root is not available Related: bug 481888, bug 467766 M +17 -0core/libs/album/engine/albumthumbnailloader.cpp M +1-0core/libs/album/engine/albumthumbnailloader.h https://invent.kde.org/graphics/digikam/-/commit/d472489b5457710d44c83ed6bac61c795e607646 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #23 from caulier.gil...@gmail.com --- @Stefan, digikam 8.2.0 pre-release have been rebuilt using last Qt 5.15.11 + KDE 5.110 frameworks. Installer is available at usual place : https://files.kde.org/digikam/ Can reproduce the problem with this version? Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #22 from caulier.gil...@gmail.com --- Hi all, digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #21 from caulier.gil...@gmail.com --- Git commit e4fbd86ff7be46b388aaf8ba78b780d45f2029a5 by Gilles Caulier. Committed on 20/06/2022 at 16:52. Pushed by cgilles into branch 'qt5-maintenance'. DMemoryInfo: sync with master M +0-1core/app/DigikamCoreTarget.cmake M +0-1core/libs/CMakeLists.txt M +15 -13 core/libs/dialogs/libsinfodlg.cpp M +11 -9core/libs/dimg/loaders/dimgloader.cpp D +0-20 core/libs/kmemoryinfo/CMakeLists.txt D +0-215 core/libs/kmemoryinfo/kmemoryinfo.cpp D +0-127 core/libs/kmemoryinfo/kmemoryinfo.h D +0-847 core/libs/kmemoryinfo/libstatgrab/kmemoryinfo_backend.cpp M +1-0core/libs/threadimageio/CMakeLists.txt A +547 -0core/libs/threadimageio/engine/dmemoryinfo.cpp [License: GPL (v2+)] A +162 -0core/libs/threadimageio/engine/dmemoryinfo.h [License: GPL (v2+)] M +3-4core/libs/threadimageio/fileio/loadingcache.cpp https://invent.kde.org/graphics/digikam/commit/e4fbd86ff7be46b388aaf8ba78b780d45f2029a5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #20 from caulier.gil...@gmail.com --- Git commit 930de78b3fc3171b87846877a66ec64a45011510 by Gilles Caulier. Committed on 20/06/2022 at 16:39. Pushed by cgilles into branch 'master'. use new class from DK core to handle memory device information M +0-1core/app/DigikamCoreTarget.cmake M +0-1core/libs/CMakeLists.txt M +15 -12 core/libs/dialogs/libsinfodlg.cpp M +10 -7core/libs/dimg/loaders/dimgloader.cpp D +0-20 core/libs/kmemoryinfo/CMakeLists.txt D +0-215 core/libs/kmemoryinfo/kmemoryinfo.cpp D +0-127 core/libs/kmemoryinfo/kmemoryinfo.h D +0-847 core/libs/kmemoryinfo/libstatgrab/kmemoryinfo_backend.cpp M +1-0core/libs/threadimageio/CMakeLists.txt M +3-3core/libs/threadimageio/fileio/loadingcache.cpp https://invent.kde.org/graphics/digikam/commit/930de78b3fc3171b87846877a66ec64a45011510 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #19 from caulier.gil...@gmail.com --- Maik, I just discovered that KMemoryInfo is in KF5::KCoreAddons module here since KF5 5.95 : https://invent.kde.org/frameworks/kcoreaddons/-/blob/master/src/lib/util/kmemoryinfo.h ... and it support Windows, Linux, FreeBsd, Android, and... MacOS. It don't use libstatgrab backend, it's a pure Qut implementation as i can see. I think it safe to replace DK core class as well (KF5 5.95 is too young for the moment)... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 caulier.gil...@gmail.com changed: What|Removed |Added Platform|Other |macOS (DMG) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.2.0 |7.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #18 from Eric Moret --- I can still reproduce this problem with latest build as of 9/1/2021 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #17 from Maik Qualmann --- A new MacOS package is available. Can the problem still be reproduced? https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #16 from caulier.gil...@gmail.com --- Hi, The daily bundles build machine is down since 15 of august due to a power shutdown. This machine build a PKG installer for MacOS which is published online in a download area. This machine will be up later next monday, not before. sorry. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #15 from Eric Moret --- Sorry for a noob question, how can I test this change? Should I wait for the next version of Digikam to come out or is there a better/faster way? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #14 from Maik Qualmann --- Git commit 40d09500b9c94333e74473da98da37bc1f64097d by Maik Qualmann. Committed on 21/08/2021 at 13:51. Pushed by mqualmann into branch 'master'. try with QFileInfo to wake up and use QDirIterator M +3-3core/libs/database/collection/collectionmanager_location.cpp https://invent.kde.org/graphics/digikam/commit/40d09500b9c94333e74473da98da37bc1f64097d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #13 from Maik Qualmann --- (In reply to caulier.gilles from comment #12) > About the comment #8 : What's about the right access to the mount path from > client applications under MacOS ? Since the second attempt works, through the workaround in Comment 4, since CollectionManager::updateLocations () is triggered again, it cannot actually be a rights problem. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #12 from caulier.gil...@gmail.com --- About the comment #8 : What's about the right access to the mount path from client applications under MacOS ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #11 from caulier.gil...@gmail.com --- A possible solution is given in this post using sysctl: https://stackoverflow.com/questions/8782228/retrieve-ram-info-on-a-mac Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #10 from caulier.gil...@gmail.com --- Maik, The memory info is not supported from kmemoryinfo code in digiKam core, for MacOS. This code come from the memory_stats.c part from libststgrab : https://libstatgrab.org/ Code is on github : https://github.com/libstatgrab/libstatgrab/tree/master/src/libstatgrab As MacOS is a freebsd like system this can be easy to patch... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #9 from Maik Qualmann --- Regardless of this problem, we can not determine the currently available memory size under MacOS because the function not supported MaOS. We only create a cache of 60MB for preview images. Normally, it is approximately cache from 400MB for a memory size of 8GB. We need to fix this. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #8 from Maik Qualmann --- Yes, the network collections are recognized as not available. This must be a MacOS specific problem. The network path must contain at least one file or folder. The QDir::entryList() returns no entries. Either MacOS "sleeps" or the file system is mount during the first access. I have an idea for a workaround I'll test. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #7 from Eric Moret --- Created attachment 140898 --> https://bugs.kde.org/attachment.cgi?id=140898=edit Terminal Output macOS 11.5.2, Digikam 7.3.0, network path not working -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #6 from Maik Qualmann --- The log from the terminal when starting digiKam would be interesting to see whether the network collection is recognized. Here is a description of how the environment variable is set and how the log can be obtained in MacOS: https://www.digikam.org/contribute/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 Eric Moret changed: What|Removed |Added CC||eric.mo...@gmail.com --- Comment #5 from Eric Moret --- I have the same problem running on macOS BigSur 11.5.2 with Digikam 7.3.0. The workaround described in https://bugs.kde.org/show_bug.cgi?id=438845#c4 is only fixing it temporarily. A more reliable way to access network share from MacOS would be better. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #4 from Stefan Paul --- Hi Maik, I just had 5min to retest digikam a bit more. I copied the path out of the network connection in the preferences of digikam, then I deleted the path, an I pasted the path which I copied before in, and it solved my problem. What actualy the reason for this problem was, I don't know, but thanks for your help. Now I've got a other problem with the tag symbols under macOS, but for this I will make a new post -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #3 from Maik Qualmann --- Hmm, testing a network collection to see if it's online is easy. We check whether there is at least one file or folder in the mount path, if not, we take the collection offline. So the question is why there are apparently no files in the mount path under MacOS. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #2 from Stefan Paul --- Yes, the folder is added as network collection //ds-educdesign-e/home/Drive/Moments -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The image folder should be added as a network collection. Was it done like that? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Database-Media -- You are receiving this mail because: You are watching all bug changes.
