File Browser Does not start after drive encryption

After getting encryption working (thanks macom), I noticed that the file broswer plugin does not start. If I unlock my drive and then disable and enable the plugin it starts fine.

OMV is rock solid so I do not expect to restart/shutdown the computer hosting it very often so not a huge issue in the long term. However is there away of sceduling the plugin to "restart" after a certain time, say 10 minutes. My thinking is that if I restart the server I will always manually unlock the drive (I know you can automate this but I do not want to do that). I can't be bothered disabling and enabling the browser plugin so is there a way of rescheduling the restart of the service/plugin?

(Or ideally a fix to so the plugin so it will work with an encrypted drive that is not unlocked)

Thanks for the reply macom. I'm not sure that worked however.

My podman.service now looks like the following.

### Editing /etc/systemd/system/podman.service.d/override.conf
### Anything between here and the comment below will become the new contents of the file


[Service]
ExecStartPre=/bin/sleep 150
StartLimitIntervalSec=300s


### Lines below this comment will be discarded


### /lib/systemd/system/podman.service
# [Unit]
# Description=Podman API Service
# Requires=podman.socket
# After=podman.socket
# Documentation=man:podman-system-service(1)
# StartLimitIntervalSec=0
#
# [Service]
# Type=exec
# KillMode=process
# Environment=LOGGING="--log-level=info"
# ExecStart=/usr/bin/podman $LOGGING system service

I noticed I still get the below at bootup, suggesting that the plugin/service is still trying to start.

Note the File Browser service still does not start (after waiting 5 minutes)

Any suggestions please? Help would be much appreciated.

No rush. Whenever you have the time.

Zitat von macom

For now revert the change with

systemctl revert podman.service

Done

macom. Did you get chance to have a think about this?