Bug#1051441: systemd: user unit is no longer started after upgrade to bookworm

[Michael Biebl]

Am 08.09.23 um 13:37 schrieb Vincent Lefevre:

On 2023-09-08 13:05:23 +0200, Michael Biebl wrote:

Am 08.09.23 um 11:08 schrieb Vincent Lefevre:

On 2023-09-08 07:48:43 +0200, Michael Biebl wrote:

Please attach the output of
systemctl --user status rsysinfo.service

rsysinfo-status attached.

systemctl --user cat rsysinfo.service

rsysinfo-cat attached.

Given that your rsysinfo.service resides in $HOME/config/systemd, you rely
on systemd --user to trigger the mount request?

No, the mount is done automatically at boot, but this is done
asynchronously and it is not immediate (it can take a few seconds).
BTW, this disk is not directly related to the user, but also contains
various other data, such as the contents of the website.

I assume if you ensure that $HOME is mounted prior to the login,
rsysinfo.service is properly started

I don't know how this can be done. I would actually expect systemd
to automatically wait for $HOME to be available (possibly with a
timeout), since it is needed.

systemd-user-sessions.service has
After=remote-fs.target nss-user-lookup.target network.target home.mount


and user@.service has
After=systemd-user-sessions.service

If you have a custom mount setup, you should be able to tweak those unit files to your needs e.g. via RequiresMountsFor=

OpenPGP_signature.asc
Description: OpenPGP digital signature