Tried a bunch of things and cruising the forums but just ended up being a mess. Seems like allot of other newbs are having trouble mounting the network drive at boot in fstab. That said, most problems are related to hostname resolution across the network.
#Networking digikam windows#
Once you're finished, you should be able to browse and connect to Windows shares by clicking on "places" > "connect to server". In this howto, I will outline the five primary reasons for the problem, and provide fixes for each. Windows share browsing issues are somewhat complex in that even though your symptoms are exactly the same, the causes can be extremely different. So, if you’re willing to put forth a bit of effort for greater rewards than this tutorial will provide, please see the second link in my signature. It is more difficult to get things working properly, but once it’s done you never have to think about it again. Location: - date: May 25, 2009įirst of all, even though it’s more difficult, manually mounting shares via /etc/fstab gives many advantages including faster speeds, more reliability, and larger file transfer sizes. Ln: creating symbolic link `/media/Pictures/Pictures/digikam3.db': File existsĪnd when I try to run digikam (from terminal) I get this:ĭigikam: WARNING: [bool Digikam::AlbumDB::execSql(const QStrin :~/Pictures$ ln -s digikam3.db /media/Pictures/Pictures/ Here's the symlink command I'm using from the local directory I pointed digikam to use for albums:
But I can't seem to get the symlink working correctly. I can go into ~/.kde/share/config/digikamrc config file and change album path back to local share and digikam will start back up just fine.
#Networking digikam update#
So I follow the instructions here: and i get this: "Failed to update old Database to new Database format". Specifically at /media/Pictures/Pictures/. I want to use digikam for my pictures which are located on another network share.
0 kommentar(er)
