mirror of
https://github.com/systemd/systemd.git
synced 2026-08-10 17:14:31 +00:00
When 'homectl deactivate' is called immediately after a preceding operation, the umount inside systemd-homework can fail with EBUSY because something briefly holds a reference to the home mount (e.g. a concurrent inspect). systemd-homed already handles this gracefully by moving the home into the 'lingering' state and retrying deactivation after 15 seconds, but the bus reply for the original DeactivateHome call returns the org.freedesktop.home1.HomeBusy error immediately, which makes TEST-46-HOMED flaky. Fix homectl to follow homed and retry for up to 30 seconds on HomeBusy and add a test case trying to make the issue more reproducible.