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 flashed raspberry pi os lite 32-bit onto a 16GB SD card and booted it on a raspberry pi v4. For flashing, I used the following settings within new config menu (sorry for german language):
After booting, systemd service userconfig.service hangs and blocks some other services from starting. I recognized, because an own systemd service of mine was waiting for multi-user.target. Trying to start it just hang without providing any logs/output on stdout, stderr, journalctl or syslog. Quite annoying ...
Took me a while to figure out what was happening:
pi@<hostname>:~ $ sudo systemctl list-jobs
JOB UNIT TYPE STATE
104 userconfig.service start running
2 multi-user.target start waiting
1 graphical.target start waiting
117 systemd-update-utmp-runlevel.service start waiting
4 jobs listed.
pi@<hostname>:~ $ sudo journalctl -u userconfig
-- Journal begins at Thu 2022-09-22 02:23:40 CEST, ends at Wed 2023-01-18 22:02:42 CET. --
Sep 22 02:24:25 <hostname>[1]: Starting User configuration dialog...
If I check "Benutzername und Passwort setzen" (english "set username and password") in config setting dialog, the error is not happening.
The text was updated successfully, but these errors were encountered:
I flashed raspberry pi os lite 32-bit onto a 16GB SD card and booted it on a raspberry pi v4. For flashing, I used the following settings within new config menu (sorry for german language):
After booting, systemd service
userconfig.service
hangs and blocks some other services from starting. I recognized, because an own systemd service of mine was waiting for multi-user.target. Trying to start it just hang without providing any logs/output on stdout, stderr, journalctl or syslog. Quite annoying ...Took me a while to figure out what was happening:
If I check "Benutzername und Passwort setzen" (english "set username and password") in config setting dialog, the error is not happening.
The text was updated successfully, but these errors were encountered: