I'm using Linux Mint which is a gnome-based environment. I have installed a lot of kde libs, so basically digiKam is running.
My photos are on a file server which I can access through smb and sftp. Using Dolphin I can access that folder (both smb and sftp work, so I assume the necessary kio libs are installed).
The database is running on a shared mysql on that same server.
When I try to add the photo directory as a "collection on network share", I can select that directory. The shown path is "sftp://email@example.com:2220/home/shared/Fotos" or "smb://martin@srv0/shared/Fotos".
I can browse the folder's contents with both protocols using the file selector dialog.
When I click OK, the file selector dialog closes but the path is not added to the list of collections.
No output is written to stdout/stderr in that case. The only output is written on startup:
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
digikam(3152)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!
I think this is not related.
I can add that folder through gvfs (not natively but through the legacy mount point):
"/home/martin/.gvfs/shared on srv0/Fotos"
gvfs is the gnome equivalent of kio. This is not an option for me, as this path is different for different users and from different machines.
Steps to Reproduce:
1. Use Linux Mint (or probaby any other Gnome-based desktop), many KDE-libs an Dolphin are installed.
2. Put photos on a network share via smb or sftp
3. Check that the share can be reached/browsed with Dolphin
4. Configure photo database through mysql on server
5. Select folder (sftp or smb) as a collection on network share.
6. Click OK
The folder is not added to the list of collections.
The folder is not scanned for photos.
The folder is listed as a collection with the path I had chosen (e.g. "sftp://firstname.lastname@example.org:2220/home/shared/Fotos" or "smb://martin@srv0/shared/Fotos")
The photos from that folder are added to digiKam.
The share is accessible for all networked users (using the same database, provided that they can access that shared folder)
I have the same issue:
Database and images on a local folder
I cannot add a collection on an empty shared samba network folder (smb) to which I have read/write access and which I can view via Nautilus.
From Digikam I select the folder and add it, but it doesn't appear in the list of collections or albums.
I just upgraded to Digikam 2.80 - exactly the same ridiculous problem.
Collections must be mounted natively, virtual filesystems like kio cannot work. There should be an error message though.
The 'Collections Settings' dialogue offers 'Collections on Network Shares' as one of three options with an 'Add Collection' button.
What network file system should I use to mount shares natively?
>What network file system should I use to mount shares natively?
Network file system, as NFS or Samba...
(In reply to comment #5)
> >What network file system should I use to mount shares natively?
> Network file system, as NFS or Samba...
So, if I mount my collection natively, why would I need a separate option to select a network share. Does digikam behave any different from a local collection (e.g. detection if this collection is offline, tolerant towards different paths to the same collection for different users)?
Would it be so bothersome to support virtual filesystems? A component named "kioslave" already exists - at least within this bug tracker. This suggests that there might already exist some relevant code. Or am I mistaken?
NFS isn't available on this file server; it's a Samba server - surely SMB is Samba?
yes, smb = SAMBA
That's what I thought - I am using Samba to connect to my network share in Digikam's Settings - Configure Digikam - Collections menu.
This shows Local Collections, Collections in Removable Media, and Collections on Network Shares. The Add Collections button for Network Shares brings up a network connections dialogue box for Samba shares ('Choose the folder containing your collection') - I select my Samba server and enter my username and password. I navigate to a folder on the server; select OK. The network address shows: 'smb://servername/Public/myname/Pictures'. I click OK; the dialogue box closes and.... nothing. There is no connection to the server under 'Network Shares'.
This seems like a problem to me.
I've also set up an automounted CIFS/Samba mount point for the server on my machine (using cifs-utils and an fstab entry), with which I have repeated the process. Digikam allows me to set up the collection as a Network Share, and lists it in Collection Settings - Root Album Folders. But it doesn't show up under 'My Albums' in the main viewing screen and I can't see a way to access it via Digikam.
Am I missing something here?
Any help would be much appreciated!
I notice that whereas the local collection has a tick next to it in Settings, the network collection has a greyed-out plug and mousing over it raises a tooltip message 'This collection is currently not available.'
It is mounted and browsable from Nautilus.
> So, if I mount my collection natively, why would I need a separate option to
> select a network share. Does digikam behave any different from a local
> collection (e.g. detection if this collection is offline, tolerant towards
> different paths to the same collection for different users)?
On Linux, the network mount is just a path somewhere. We must not check the associated hardware. We currently dont have code which detects that a given directory is a mount point, for Linux, nor for any other platform. That's why there's the different way to add a network share. Detection for offline/online is simply done by checking if the path is empty or not.
> Would it be so bothersome to support virtual filesystems? A component named
> "kioslave" already exists - at least within this bug tracker. This suggests
> that there might already exist some relevant code. Or am I mistaken?
The virtual filesystems of the desktop environments are high-level. For any low-level access: reading metadata, producing a thumbnail, showing or editing the picture, the file would need to be downloaded and placed in a temporary destination, not because digikam cannot handle all this, but because the underlying libraries need native file pointers.
There are projects like kiofuse which could help in this process, but for cases where the kernel supports native mounting, without the redirection fuse -> kio, I would recommend to take this way, it is certainly faster.
(In reply to comment #11)
> On Linux, the network mount is just a path somewhere. We must not check the
> associated hardware. We currently dont have code which detects that a given
> directory is a mount point, for Linux, nor for any other platform. That's
> why there's the different way to add a network share. Detection for
> offline/online is simply done by checking if the path is empty or not.
I intended to use Digikam to import images from a memory card and organise them on the network folder; the logic of your online/offline test mitigates against this.
However I had placed an image file on the network folder before getting the tooltip message 'This collection is currently not available.' so the online/offline detection doesn't appear to be working as intended.
After an overnight delay, Digikam recognised the Samba/CIFS local mount point of the network folder with an image in it.
I couldn't find a way to force refresh of the Collections, but Digikam does recognise a network folder if there is a file in the folder before the Collection is created. It's just slow to adjust if the image is added later.
I still can't get the Samba network folders New Collection working though.
Have the same problem. After adding new smb: folder as a collection nothing happens and there is no new collection in the main screen of the program.
Please, someone, it has been a year form the time the bug was submitted and it has a status "UNCONFIRMED".
I run Version 3.1.0
Using KDE Development Platform 4.10.5 and Ubuntu 13.04.
*** Bug 329921 has been marked as a duplicate of this bug. ***
I can confirm the same behavior, unable to use a collection on my nas. What needs to be done to change the status of this bug from unconfirmed to confirmed?
I confirm this bug also.
I'm using Linux Mint 17 Cinnamon with the new version of digKam (version 4.4). Everything else seems to work OK.
My photo collection is on an SMB share on a Synology server.
I have spent a couple of weeks getting to know digiKam using copies of some folders on my local PC. Now I'm trying to 'go live' by importing my main photo library from my network server, and I can't.
Can I add my voice to ask that this bug be status be changed to 'Confirmed'?
Still the same. For me it is useless this way. Nobody seems to care.
I am having a Gnome environment as well on Fedora 24.
It seem to be different if you use a samba share in Gnome or KDE.
I have got a work around which let me use a samba share for my Database and my photos.
Install with your favorite software package program a KDE package called " Smb4k"
You can use this to create a network shortcut in "/home/YourUserName/smb4k/YourSambaShare/..." this path you can copy and paste into your digikam database location field.
Following your tips from comments #19, can we considerate this workaround as a solution to close this file ?
Do you see my previous comment ?
for me it's fine to close the file.