I have mounted my NFS network shares using systemd. For every network path there is a *.automount and a *.mount unit. The albums on this network shares are correctly set up in Digikam (not local, but network). When a server containing an album is offline, digikam startup hangs indefinitely. Only starting the corresponding server (and making the network share available for automount) will make Digikam continue the startup. Here the mnt-server.mount unit: [Unit] Description = Mount network shares on server. Wants=cachefilesd.service Requires=wake@server.service nfs-client.target After=wake@server.service nfs-client.target ConditionHost=!server [Mount] What=server:/ Where=/mnt/server/ Type=nfs Options=fsc
Additional info: As soon as I stop the *.automount systemd unit of the server currently offline, Digikam continues the startup process as usual.
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
@wuselwu digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier
@wuselwu, What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Note: bundle is now based on Qt 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier