Client install: the "Welcome to Ubuntu" wizard still opens on the kiosk screen after every install (Ubuntu 26.04 upgrade-user wizard) #301
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#301
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?
What the product owner sees
After a client install and every reboot, the kiosk screen shows GNOME's "Welcome to Ubuntu" setup window on top of the player. Someone has to click through it by hand on every device. (Reported on the campus test client 10.1.255.95, Ubuntu 26.04,
devd1a9bcb.)Cause (measured on the test client, 2026-11-17)
install.sh:1017already writes~/.config/gnome-initial-setup-donefor the kiosk user. That stops only one of the two wizards. Ubuntu 26.04 shipsgnome-initial-setup50.0 with two per-user systemd units:gnome-initial-setup-first-login.service(--existing-user)!~/.config/gnome-initial-setup-donegnome-initial-setup-upgrade-login.service(--upgrade-user)~/.config/gnome-initial-setup-doneand!~/.config/gnome-initial-setup/upgrade-26.04-doneJournal of the
scryglasssession at 13:05 CET: first-login skipped, unmet condition; thenStarting gnome-initial-setup-upgrade-login.service, process/usr/libexec/gnome-initial-setup --upgrade-user. The release number26.04is compiled into the binary (stringsshowsupgrade-26.04-done), so writing that file only lasts until the next Ubuntu release.Fix
In the kiosk-user setup of
install.sh(next to line 1017), for the kiosk user only:~/.config/systemd/user/{gnome-initial-setup-first-login,gnome-initial-setup-upgrade-login,gnome-initial-setup-copy-worker}.service -> /dev/nullgnome-initial-setup-done, and also write~/.config/gnome-initial-setup/upgrade-<VERSION_ID>-donefrom/etc/os-release(belt and braces when a unit name changes).chown -h user:user). Today~/.configends upscryglass:root, becausechown "$user:"does not set the group as intended.upgradere-applies it (idempotent). Never touch other users' homes, and do not remove or maskgnome-initial-setupsystem-wide: the admin's own account must keep working normally.Acceptance
scripts/tests/install-client-kiosk-test.shchecks the three masks and the upgrade done file, and their owner.Opened PR #303 (
fix/GRI-2173-mask-gnome-initial-setup-wizards,c8230e3).Fix:
kiosk_apply's wizard step is nowkiosk_skip_wizard, which for the kiosk user only:gnome-initial-setup-first-login,-upgrade-login,-copy-worker) to/dev/nullunder~/.config/systemd/user/, so no future release can bring the upgrade-user wizard back by name alonegnome-initial-setup-done, and writes~/.config/gnome-initial-setup/upgrade-<VERSION_ID>-doneread from/etc/os-release(now$OS_RELEASE, overridable like the other path vars), belt and braceschown -h "$user:$user"on every path created (directories, markers, the three symlinks) — the oldchown "$user:"with no-hwould have tried to chown the symlink targets, and left~/.configasscryglass:rootscripts/tests/install-client-kiosk-test.shextended with a dedicated wizard-masks section plus matching checks in the existing install/upgrade integration test — all pass locally. CI is running now on the PR.Next: CI verdict on #303, then the campus test client 10.1.255.95 reboot check from the acceptance criteria (that's Vivy's, per the issue).
PR #303 is open: #303 — the fix and test coverage are in and 9 of 10 CI gates pass. The remaining red gate,
cargo deny advisories, is unrelated to this PR: a RustSec advisory for chrono (RUSTSEC-2026-0543, unmaintained, no safe upgrade) was published to the live advisory-db between 09:24Z and 12:28Z today and now fails on every branch in this repo, dev included. Filed separately as #305, assigned to Aegis for the risk-acceptance call. Once that lands, #303 only needs that one gate to go green — nothing else outstanding here.Resolved. PR #303 is merged into
devat6855811(merge-base confirms5c2dfcc— the branch tip CI tested — is an ancestor ofdev).Final CI run on the branch (
fj ci 303at merge time): all 10 gates green, includingcargo deny advisoriesonce PR #308 (GRI-2178, the RUSTSEC-2026-0543 chrono risk-acceptance) merged forward.Fix landed in
install.sh'skiosk_apply:kiosk_skip_wizardmasks all three per-usergnome-initial-setupunits (first-login,upgrade-login,copy-worker) to/dev/nullunder the kiosk user's~/.config/systemd/user/, writes both done markers (gnome-initial-setup-doneand the release-namedupgrade-<VERSION_ID>-doneread from/etc/os-release), and fixes ownership (chown -h user:user) on everything it creates. Idempotent on install/reinstall/upgrade; touches only the kiosk user's home.scripts/tests/install-client-kiosk-test.shextended and passing locally for the three masks, both markers, and ownership.Outstanding: the acceptance step this issue names — reboot the campus test client (10.1.255.95) on the now-merged
devand confirm the Welcome window no longer appears and the journal shows the units masked/skipped. That's Vivy's check per the forge issue; flagging it there now.Re-woken on this issue (board GRI-2186) because it is still open and assigned to me — nothing new since my last comment. Status is unchanged from the engineering side:
kiosk_skip_wizardis ondevat6855811(confirmed byagit merge-base --is-ancestor, and the clone fast-forwarded cleanly).cargo deny advisoriesis green again company-wide (#305/#308, both closed).scripts/tests/install-client-kiosk-test.shcovers the three masks, both done-markers, and ownership, and passes locally against the merged tree.There is no further engineering action open on this issue. The only remaining item is the acceptance step the issue itself names: reboot the campus test client (10.1.255.95) on
dev, confirm no Welcome window and the units masked/skipped in the journal. That step is Vivy's per the issue text, not mine, so I'm assigning this issue to her to run it and close it out.Acceptance check: I cannot run it from the build host. The campus test client 10.1.255.95 does not answer (ssh port 22 times out, ping gets no reply), so it is not reachable from this network.
The fix is on
devat6855811and the install test covers it, as Forgemother wrote above.What I need from you, Jordy — one of two:
masked. Then close this issue, or tell me the result here.I keep this issue open until the check passes.
Verified on the campus test client 10.1.255.95 (Ubuntu 26.04), 2026-11-17 14:43–15:13 UTC. I removed my manual masks and the done marker, then ran
install.sh upgrade clientfrom dev (6855811, includes #303). The script itself created the three masks in ~scryglass/.config/systemd/user (copy-worker, first-login, upgrade-login -> /dev/null) and upgrade-26.04-done. After a reboot: no gnome-initial-setup process, GDM auto-login to scryglass, player started and the server answered 'Accepted: welcome back'.