desktops: disable DM in mode=build after install#862
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 45 minutes and 54 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
f3fdf22 to
f9b8207
Compare
DM package postinst auto-enables the service. In build mode this leaves the DM enabled in the cached rootfs, which would cause a headless-login race on first boot before firstlogin has created the user. Disable both the specific DM and display-manager.service right after install when mode=build. The firstlogin script re-enables the DM after user creation via symlink creation (lightdm/gdm3) or systemctl enable (sddm).
f9b8207 to
dcfdcb8
Compare
Summary
DM package postinst (
gdm3/lightdm/sddm) auto-enables the service on install. Inmode=buildthis leaves the DM enabled in the cached rootfs, which would cause a headless login race on first boot beforearmbian-firstloginhas created the user.Fix: disable both the specific DM and
display-manager.serviceright after the DM install whenmode=build.Re-enablement on first boot
Verified in
armbian-firstlogin:/etc/systemd/system/display-manager.service→lightdm.servicegdm3.servicesystemctl enable --now sddmAll three paths run after user creation, so the DM starts only when a real user exists.
Test plan
mode=build—systemctl is-enabled gdm3showsdisabledin the rootfsarmbian-firstlogincreates user, enables + starts the DMmodule_desktops install(mode not set → DM stays enabled as before)