Version: 1.9.0 OS: Linux I have most of my picture files on a NAS server, which is part of my LAN. When I try to add one of the NAS folders via Settings-Configure-Collections- Network Shares-Add collection I can choose the folder on the NAS cliucking through the Samba Shares tree. But when I add it, I get the window telling me: "Problem adding collection. The selected folder does not exist or is not readable". How that, if I have just found it with Digikam? Reproducible: Didn't try Steps to Reproduce: The NAS is mounted using a bash scrip with gvfs-mount. It is accessible in Dolphin. I use the menu steps Settings-Configure-Collections- Network Shares-Add collection, find and choose a folder on the NAS (I do not want to have all the picture directories continuously added as collction as that would probably make the system very slow). Actual Results: I always get the response that the folder is not readable. Expected Results: I want to b able to add the folders on the NAS as collections. I am running DigiKam on a Ubuntu Natty Narwhal desktop PC. I am not a linux guru, and unable to use the workarounds which were described in various forums for older versions of DigiKam.
defintivly, i recommend to check 2.0.0 rc where a lots of improvements and fixes have been done. final release is planed in few days... gilles caulier
This is the relevant code in collectionmanager.cpp: QString path = fileUrl.toLocalFile(KUrl::RemoveTrailingSlash); QDir dir(path); if (!dir.isReadable()) { *message = i18n("The selected folder does not exist or is not readable"); } as you see, it looks pretty innocent. We'd need to check that nothing is done to the file path prior to this, then why QDir says the directory is not readable. I dont have a NAS for testing here.
It seems I found a work-around: When the NAS is mounted, it can be accessed in the .gvfs folder (hidden). If I add this as a local collection, it works fine. Just be sure you don't have too big folders, else it takes ages to get them searched and added. And now I will wait for 2.0.0. Maybe the samba works there. Or could there be an issue that mounting with gvfs is different from mouting cifs, and DigiKam only likes the cifs-mounted external resources?
Could it be that you have some sort of virtual file system with gvfs like some KDE ioslaves do? We need a native filesystem provided by the kernel.
Jowi, Do you see comment #4 from Marcel ? Can you test digiKam 2.4 ? Gilles Caulier
I am not seeing the error message, instead it does nothing. I am running Kubuntu 13.04 amd64, KDE 4.10.4, digikam 3.1.0.
This file still valid using last digiKam 5.0.0 ? Gilles Caulier
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier
No feedback. Cloased