You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried many times now to make a headless RPI boot and setting the user and password using the new /boot/userconf.
And it works great except for one thing - it always set the login default to automatic text login.
I don't think this is the expected behavior.
In my "image" i remove /etc/systemd/system/getty@tty1.service.d/autologin.conf and run systemctl --quiet set-default multi-user.target
, but the problem seems to be that when the userconf-service is handling the userconf - the flow seems to be like this:
Userconf-service get to this line (which is rename but also set the new password):
Thanks - I have basically removed in my local images. I can't really figure out why the userconf needs to run the cancel-rename always and reset the login option.
As mentioned here this was planned soon: RPi-Distro/pi-gen#614 (comment)
And AFAIK it needs to be B1: guysoft/CustomPiOS#163 (comment)
I though I might make a PR to make this easier to merge in.
Also I am planning to make a patch out of it to have inside CustomPiOS untill this is fixed.
I tried many times now to make a headless RPI boot and setting the user and password using the new /boot/userconf.
And it works great except for one thing - it always set the login default to automatic text login.
I don't think this is the expected behavior.
In my "image" i remove /etc/systemd/system/getty@tty1.service.d/autologin.conf and run systemctl --quiet set-default multi-user.target
, but the problem seems to be that when the userconf-service is handling the userconf - the flow seems to be like this:
Userconf-service get to this line (which is rename but also set the new password):
Which then will hit this:
Which again will hit this:
userconf-pi/cancel-rename
Line 28 in 602561b
Thereby calling raspi-config to set it to B2 Console Autologin
Im not sure why renaming the username or/and setting the password should cause any changes to the login behavior but I might be missing something
The text was updated successfully, but these errors were encountered: