Bug 227566 - digikam does not allow smb:// shared folder as picture collection
Summary: digikam does not allow smb:// shared folder as picture collection
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Collections (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-18 20:28 UTC by Christian González
Modified: 2018-08-13 12:50 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0
Sentry Crash Report:


Attachments
screenshot (102.57 KB, image/png)
2011-04-06 21:18 UTC, Christian González
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian González 2010-02-18 20:28:48 UTC
Version:           1.1.0 (using 4.4.00 (KDE 4.4.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-13-generic

if you want to set up a remote (smb) folder in digikam, it says that the folder does not exist.
Go to digikam settings/configure digikam... -> collections -> "Collections on network shares - and choose a folder on a smb server.
When you press ok, you get a "The selected folder does not exist or is not readable".

Same thing at the first startup of digikam, it somehow looses parts of the URL, trims e.g. "smb://gandalf/share/folder" to "/share/folder" which is local and of course cannot be found.
Comment 1 Marcel Wiesweg 2010-02-18 20:59:46 UTC
Note that digikam does not support smb:// URLs. You need to mount the share natively.
What I will fix in this bug is the error message: You should be given a hint at this fact.
Comment 2 Marcel Wiesweg 2010-02-20 15:53:42 UTC
Reassigning to kdelibs/kio:

We use KFileDialog::getExistingDirectory to ask for a local directory. The API docs are explicit that this is about choosing a local directory only.
However, in the context of network shares, users are tempted to enter smb:// URLs in the line edit at the bottom of the dialog. In this case, the protocol is cut off and only the path is returned from the dialog. 

If using getExistingDirectoryUrl (supposed to return local or remote) to catch this error in a user-friendly manner, I also get a file:// URL back when entering a smb:// url.
Comment 3 Christian González 2011-04-06 21:18:48 UTC
Created attachment 58651 [details]
screenshot

having this bug still present in KDE 4.6.1, this may be not correct.
you can see a screenshot presenting the file dialog after clicking on "Add Collection" using network shares.

The "Network" button on the left and all shortcuts to Network shares should be gone than, shouldn't they?
If getExistingDirectoryUrl is supposed to return a local dir, then it HAS to hide network access.
Comment 4 caulier.gilles 2018-08-13 12:50:33 UTC
Git commit d636f0557a6692b2e36ccd00a6f5c7d662ce889e by Gilles Caulier.
Committed on 13/08/2018 at 12:48.
Pushed by cgilles into branch 'master'.

add a information message in Setup Collection about remote storage which must be mounted natively before to use with digiKam.
Note: this only affect digiKAm with native desktop file dialog, not Qt file dialog
FIXED-IN: 6.0.0

M  +2    -1    NEWS
M  +7    -3    core/utilities/setup/collections/setupcollections.cpp

https://commits.kde.org/digikam/d636f0557a6692b2e36ccd00a6f5c7d662ce889e