Bug 104005

Summary:	import of smb:/ folder fails
Product:	[Applications] digikam	Reporter:	Edwin Schepers <yez>
Component:	Import-Albums	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version First Reported In:	0.7.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Edwin Schepers 2005-04-16 13:47:02 UTC

Version:           0.7.3-beta1 (using KDE 3.4.0, compiled sources)
Compiler:          gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
OS:                Linux (i686) release 2.6.10-1.766_FC3

Hi,
I'm trying to import a folder from a smb:/ share, but when I click OK on the fileselection dialog, nothing happens.

Regards,
Edwin.

Comment 1 Edwin Schepers 2005-04-16 14:10:40 UTC

It's also happening when using the fish:/ or ftp:/ protocol

Comment 2 Tom Albers 2005-04-16 14:41:05 UTC

Hi Edwin, did you happen to look at the source?

Comment 3 Joern Ahrens 2005-04-16 15:44:21 UTC

CVS commit by jahrens: 

Checking if a remote directory really exists, isn't supported.

BUG: 104005


  M +1 -1      albumfolderview.cpp   1.73


--- kdeextragear-3/digikam/digikam/albumfolderview.cpp  #1.72:1.73
@@ -895,5 +895,5 @@ void AlbumFolderView::albumImportFolder(
 
     KFileDialog dlg(QString::null, "inode/directory", this, "importFolder", true);
-    dlg.setMode(KFile::Directory | KFile::ExistingOnly |  KFile::Files);
+    dlg.setMode(KFile::Directory |  KFile::Files);
     if(dlg.exec() != QDialog::Accepted)
         return;

Comment 4 Oliver Schonrock 2007-04-06 08:59:34 UTC

status = "resolved", resolution = "fixed"?

I am still seeing this problem in Digikam 0.9.1.

My current workaround is to use to mount sshfs instead of fish:// or sftp:// but that shouldn't really be necessary for a native KDE app? (i have to do it anyway for OpenOffice).

Is it the Kioslave that doesn't support checking the existence of remote folders, or is that a digikam limitation?

Comment 5 Angelo Naselli 2007-04-06 09:57:53 UTC

I didn't test the fixing but I'd like to add a note.

-> status = "resolved", resolution = "fixed"?
That means it is solved in svn
 
-> I am still seeing this problem in Digikam 0.9.1.
That does mean that has not been backported in stable,
moreover it cannot be magically updated, digikam team has to
release a package 0.9.1.1 for instance with fixings. Or they can
decide to postpone such a fixing into the future 0.9.2.

Another way is to ask for that fixing to your distro maintainers,
they can backport the fixing into stable package.

Cheers,
	Angelo