presets: Don't enable systemd-homed-firstboot.service by default

Enabling this service by default means every CI image without a
regular user now gets stuck on first boot due to the password prompt
from systemd-homed-firstboot.service. Let's not enable the service
by default but instead require users to enable it explicitly if they
want its behavior.

Fixes #33249

diff --git a/presets/90-systemd.preset b/presets/90-systemd.preset
index 7b7c20a02000bdff064d2f6d3d7af3e4c1ffd1cb..da6b9805fdc7f09879297827cc56daa8767e9995 100644 (file)
--- a/presets/90-systemd.preset
+++ b/presets/90-systemd.preset
@@ -21,7 +21,6 @@ enable systemd-boot-update.service
 enable systemd-confext.service
 enable systemd-homed.service
 enable systemd-homed-activate.service
-enable systemd-homed-firstboot.service
 enable systemd-journald-audit.socket
 enable systemd-mountfsd.socket
 enable systemd-network-generator.service

diff --git a/units/systemd-homed.service.in b/units/systemd-homed.service.in
index ff4f429498c702a095f0dcaa29c729d563021959..b54e5d30b200a1a1379a2628722116e8f22af40f 100644 (file)
--- a/units/systemd-homed.service.in
+++ b/units/systemd-homed.service.in
@@ -40,4 +40,4 @@ TimeoutStopSec=3min
 [Install]
 WantedBy=multi-user.target
 Alias=dbus-org.freedesktop.home1.service
-Also=systemd-homed-activate.service systemd-homed-firstboot.service
+Also=systemd-homed-activate.service