Client install: auto-login for a password-less screen account, so a screen shows the player after a reboot #232
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage#232
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
After a power cut or reboot, a screen stays at the GDM login page. The player starts only after a desktop login, and on campus nobody is there to log in. Seen on the test client (10.0.0.188:23) on 2026-11-15: no desktop session since boot, so the new build did not start.
Decision (product owner, GRI-2051, 2026-11-15)
The signage devices have no password on the screen account: a screen is never locked, so a password protects nothing.
What
install.sh(client mode) does--kiosk-user, defaultscryglass. Not insudo, no admin rights.passwd -d), so it logs in with no prompt./etc/gdm3/custom.conf,[daemon] AutomaticLoginEnable=true,AutomaticLogin=<user>. Edit only those two keys; keep the rest of the file.install.sh upgradekeeps an existing setting and does not re-create the account.Safety
sshdrefuses empty passwords by default (PermitEmptyPasswords no). The installer checks that and stops with a clear message if it is set toyes.--kiosk-password-keep(or the config key): then only auto-login is set.Done when
scripts/tests/for thecustom.confedit (keys set, other content kept, second run changes nothing).docs/deployment guide names the account and the opt-out.State: implemented, PR #234 open against
dev, CI running.What
install.sh clientnow does: everything in the description (account,passwd -d, the two GDM keys only, locked no-lock/no-blank/no-suspend dconf for that account only,upgradekeeps an existing setting) plus the sshd check and--kiosk-password-keep. Details are in the PR body and inplan/operations/deployment.md→ "The screen account".Choices I made that the description did not settle:
--no-kiosk(SCRYGLASS_KIOSK=no): no account and no auto-login, for somebody installing the client on a desktop they use themselves. The settings are recorded in/etc/grimoirix-signage/install.tomlso an upgrade keeps them. Without that file, an upgrade would quietly add the account to a device installed with--no-kiosk.Measured:
scripts/tests/install-client-kiosk-test.sh, 62 assertions, all pass. They cover the custom.conf edit (keys set, all other lines kept, second run byte-identical) and the whole step run twice on a private root (second run writes nothing).local-gates.sh --frontend-onlypassed.Not measured yet, and I cannot measure it from here: the first Done-when item, a real install followed by a reboot. This build host has no root and no container, and I have no access to the test client 10.0.0.188. Once #234 is merged, somebody with that access needs to run
... | sudo bash -s -- upgrade clienton it, reboot, and check that the player shows with no keyboard input. If it does not, runjournalctl -b -u gdmandcat /etc/gdm3/custom.confand post both outputs here.State: PR #234 is green and ready to merge into
dev.fj ci 234→ exit 0 on616ae9b5. All 11 contexts pass, includinginstall.sh client upgrade(stepscripts/tests/install-client-kiosk-test.sh, the new 62-assertion test: keys set, other content kept, second run changes nothing).dev.Still open before this issue can close: the reboot proof on a real device. "A fresh client install, then a reboot, shows the player with no keyboard input" has not been done. I have no login on 10.0.0.188 and no root on the build host. After the merge, someone with access needs to run:
Then check:
scryglassin with no keyboard input.Chief of staff: please name who holds 10.0.0.188. I'll leave this issue open until that result is posted here.