A few days ago I did an update using the built in Garuda Octopi system. Now my local network samba shares are not being loaded via systemd at boot time (the service units *.automount and *.mount). I tracked it down (I think!) to a boot error which I can't find an answer to. Early in the /var/log/boot.log record I get the message:
Failed to start systemd-guest-user.service
When logged into a kde plasma session terminal I do:
....and get the following output:
Loaded: loaded (/usr/lib/systemd/system/systemd-guest-user.service; static)
Active: failed (Result: exit-code) since Wed 2022-01-12 11:01:15 NZDT; 34min ago
Main PID: 621 (code=exited, status=5)
Jan 12 11:01:15 hpelitebook850g2 systemd: Starting systemd-guest-user.service...
Jan 12 11:01:15 hpelitebook850g2 usermod: usermod: no changes
Jan 12 11:01:15 hpelitebook850g2 chsh: chsh: Shell not changed.
Jan 12 11:01:15 hpelitebook850g2 chsh: Changing shell for guest.
Jan 12 11:01:15 hpelitebook850g2 passwd: passwd: existing lock file /etc/shadow.lock without a PID
Jan 12 11:01:15 hpelitebook850g2 passwd: passwd: cannot lock /etc/shadow; try again later.
Jan 12 11:01:15 hpelitebook850g2 systemd: systemd-guest-user.service: Main process exited, code=exited, status=5/NOTINSTAL>
Jan 12 11:01:15 hpelitebook850g2 systemd: systemd-guest-user.service: Failed with result 'exit-code'.
Jan 12 11:01:15 hpelitebook850g2 systemd: Failed to start systemd-guest-user.service.
So far I have tried reinstalling the package systemd-guest-user from chaotic aur, which didn't help - not fixed.
I am able to manually load the samba drive via the following:
systemctl start home-rob-Network-Pi4Drive.mount && systemctl enable home-rob-Network-Pi4Drive.automount
Anyone have any ideas about how to fix this systemd-guest-user.service problem?