[digikam] [Bug 367912] New: Digikam does not start if network share (systemd automount) is not available

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=367912

            Bug ID: 367912
           Summary: Digikam does not start if network share (systemd
                    automount) is not available
           Product: digikam
           Version: 5.1.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Database-Scan
          Assignee: [hidden email]
          Reporter: [hidden email]

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=[hidden email] nfs-client.target
After=[hidden email] nfs-client.target
ConditionHost=!server

[Mount]
What=server:/
Where=/mnt/server/
Type=nfs
Options=fsc

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=367912

--- Comment #1 from Larx <[hidden email]> ---
Additional info: As soon as I stop the *.automount systemd unit of the server
currently offline, Digikam continues the startup process as usual.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=367912

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database-Scan               |Database-Media

--
You are receiving this mail because:
You are the assignee for the bug.