Client install: the "Welcome to Ubuntu" wizard still opens on the kiosk screen after every install (Ubuntu 26.04 upgrade-user wizard) #301

Closed
opened 2026-11-17 12:10:27 +00:00 by vivy · 6 comments
Owner

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, dev d1a9bcb.)

Cause (measured on the test client, 2026-11-17)

install.sh:1017 already writes ~/.config/gnome-initial-setup-done for the kiosk user. That stops only one of the two wizards. Ubuntu 26.04 ships gnome-initial-setup 50.0 with two per-user systemd units:

unit runs when blocked by our done file
gnome-initial-setup-first-login.service (--existing-user) !~/.config/gnome-initial-setup-done yes
gnome-initial-setup-upgrade-login.service (--upgrade-user) ~/.config/gnome-initial-setup-done and !~/.config/gnome-initial-setup/upgrade-26.04-done no — our done file is the trigger

Journal of the scryglass session at 13:05 CET: first-login skipped, unmet condition; then Starting gnome-initial-setup-upgrade-login.service, process /usr/libexec/gnome-initial-setup --upgrade-user. The release number 26.04 is compiled into the binary (strings shows upgrade-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:

  1. Mask the wizard units in the user's own systemd directory, so no release can bring them back:
    ~/.config/systemd/user/{gnome-initial-setup-first-login,gnome-initial-setup-upgrade-login,gnome-initial-setup-copy-worker}.service -> /dev/null
  2. Keep writing gnome-initial-setup-done, and also write ~/.config/gnome-initial-setup/upgrade-<VERSION_ID>-done from /etc/os-release (belt and braces when a unit name changes).
  3. Every directory and link created owned by the kiosk user (chown -h user:user). Today ~/.config ends up scryglass:root, because chown "$user:" does not set the group as intended.
  4. upgrade re-applies it (idempotent). Never touch other users' homes, and do not remove or mask gnome-initial-setup system-wide: the admin's own account must keep working normally.

Acceptance

  • scripts/tests/install-client-kiosk-test.sh checks the three masks and the upgrade done file, and their owner.
  • On the test client 10.1.255.95: reboot, the player starts with no Welcome window; the session journal shows the units as masked/skipped. Vivy runs this check.
## 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, `dev` d1a9bcb.) ## Cause (measured on the test client, 2026-11-17) `install.sh:1017` already writes `~/.config/gnome-initial-setup-done` for the kiosk user. That stops only **one** of the two wizards. Ubuntu 26.04 ships `gnome-initial-setup` 50.0 with two per-user systemd units: | unit | runs when | blocked by our done file | |---|---|---| | `gnome-initial-setup-first-login.service` (`--existing-user`) | `!~/.config/gnome-initial-setup-done` | yes | | `gnome-initial-setup-upgrade-login.service` (`--upgrade-user`) | `~/.config/gnome-initial-setup-done` **and** `!~/.config/gnome-initial-setup/upgrade-26.04-done` | **no — our done file is the trigger** | Journal of the `scryglass` session at 13:05 CET: first-login *skipped, unmet condition*; then `Starting gnome-initial-setup-upgrade-login.service`, process `/usr/libexec/gnome-initial-setup --upgrade-user`. The release number `26.04` is compiled into the binary (`strings` shows `upgrade-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: 1. Mask the wizard units in the user's own systemd directory, so no release can bring them back: `~/.config/systemd/user/{gnome-initial-setup-first-login,gnome-initial-setup-upgrade-login,gnome-initial-setup-copy-worker}.service -> /dev/null` 2. Keep writing `gnome-initial-setup-done`, and also write `~/.config/gnome-initial-setup/upgrade-<VERSION_ID>-done` from `/etc/os-release` (belt and braces when a unit name changes). 3. Every directory and link created owned by the kiosk user (`chown -h user:user`). Today `~/.config` ends up `scryglass:root`, because `chown "$user:"` does not set the group as intended. 4. `upgrade` re-applies it (idempotent). Never touch other users' homes, and do not remove or mask `gnome-initial-setup` system-wide: the admin's own account must keep working normally. ## Acceptance - `scripts/tests/install-client-kiosk-test.sh` checks the three masks and the upgrade done file, and their owner. - On the test client 10.1.255.95: reboot, the player starts with no Welcome window; the session journal shows the units as masked/skipped. Vivy runs this check.
Member

Opened PR #303 (fix/GRI-2173-mask-gnome-initial-setup-wizards, c8230e3).

Fix: kiosk_apply's wizard step is now kiosk_skip_wizard, which for the kiosk user only:

  • masks all three per-user units (gnome-initial-setup-first-login, -upgrade-login, -copy-worker) to /dev/null under ~/.config/systemd/user/, so no future release can bring the upgrade-user wizard back by name alone
  • keeps writing gnome-initial-setup-done, and writes ~/.config/gnome-initial-setup/upgrade-<VERSION_ID>-done read from /etc/os-release (now $OS_RELEASE, overridable like the other path vars), belt and braces
  • chown -h "$user:$user" on every path created (directories, markers, the three symlinks) — the old chown "$user:" with no -h would have tried to chown the symlink targets, and left ~/.config as scryglass:root
  • runs on install, reinstall and upgrade; idempotent; touches only the kiosk user's home, never masks the units system-wide

scripts/tests/install-client-kiosk-test.sh extended 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).

Opened [PR #303](https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/pulls/303) (`fix/GRI-2173-mask-gnome-initial-setup-wizards`, c8230e3). Fix: `kiosk_apply`'s wizard step is now `kiosk_skip_wizard`, which for the kiosk user only: - masks all three per-user units (`gnome-initial-setup-first-login`, `-upgrade-login`, `-copy-worker`) to `/dev/null` under `~/.config/systemd/user/`, so no future release can bring the upgrade-user wizard back by name alone - keeps writing `gnome-initial-setup-done`, and writes `~/.config/gnome-initial-setup/upgrade-<VERSION_ID>-done` read from `/etc/os-release` (now `$OS_RELEASE`, overridable like the other path vars), belt and braces - `chown -h "$user:$user"` on every path created (directories, markers, the three symlinks) — the old `chown "$user:"` with no `-h` would have tried to chown the symlink targets, and left `~/.config` as `scryglass:root` - runs on install, reinstall and upgrade; idempotent; touches only the kiosk user's home, never masks the units system-wide `scripts/tests/install-client-kiosk-test.sh` extended 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).
Member

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.

PR #303 is open: https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/pulls/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.
Member

Resolved. PR #303 is merged into dev at 6855811 (merge-base confirms 5c2dfcc — the branch tip CI tested — is an ancestor of dev).

Final CI run on the branch (fj ci 303 at merge time): all 10 gates green, including cargo deny advisories once PR #308 (GRI-2178, the RUSTSEC-2026-0543 chrono risk-acceptance) merged forward.

Fix landed in install.sh's kiosk_apply: kiosk_skip_wizard masks all three per-user gnome-initial-setup units (first-login, upgrade-login, copy-worker) to /dev/null under the kiosk user's ~/.config/systemd/user/, writes both done markers (gnome-initial-setup-done and the release-named upgrade-<VERSION_ID>-done read 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.sh extended 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 dev and 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.

Resolved. PR #303 is merged into `dev` at `6855811` (merge-base confirms `5c2dfcc` — the branch tip CI tested — is an ancestor of `dev`). Final CI run on the branch (`fj ci 303` at merge time): all 10 gates green, including `cargo deny advisories` once PR #308 (GRI-2178, the RUSTSEC-2026-0543 chrono risk-acceptance) merged forward. **Fix landed in `install.sh`'s `kiosk_apply`:** `kiosk_skip_wizard` masks all three per-user `gnome-initial-setup` units (`first-login`, `upgrade-login`, `copy-worker`) to `/dev/null` under the kiosk user's `~/.config/systemd/user/`, writes both done markers (`gnome-initial-setup-done` and the release-named `upgrade-<VERSION_ID>-done` read 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.sh` extended 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 `dev` and 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.
Member

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_wizard is on dev at 6855811 (confirmed by agit merge-base --is-ancestor, and the clone fast-forwarded cleanly).
  • cargo deny advisories is green again company-wide (#305/#308, both closed).
  • scripts/tests/install-client-kiosk-test.sh covers 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.

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_wizard` is on `dev` at `6855811` (confirmed by `agit merge-base --is-ancestor`, and the clone fast-forwarded cleanly). - `cargo deny advisories` is green again company-wide (#305/#308, both closed). - `scripts/tests/install-client-kiosk-test.sh` covers 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.
forgemother removed their assignment 2026-11-17 13:55:12 +00:00
Author
Owner

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 dev at 6855811 and the install test covers it, as Forgemother wrote above.

What I need from you, Jordy — one of two:

  1. Run the check yourself on 10.1.255.95 (about 2 minutes):
    sudo ./install.sh upgrade          # from dev, 6855811 or later
    sudo reboot
    # after login of the kiosk session:
    sudo -u scryglass XDG_RUNTIME_DIR=/run/user/$(id -u scryglass) systemctl --user is-enabled gnome-initial-setup-upgrade-login.service   # want: masked
    journalctl -b _UID=$(id -u scryglass) | grep -i initial-setup
    
    Pass = no Welcome window, and masked. Then close this issue, or tell me the result here.
  2. Or give the build host a path to the campus client (VPN/jump host and an ssh key), and I run it.

I keep this issue open until the check passes.

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 `dev` at `6855811` and the install test covers it, as Forgemother wrote above. **What I need from you, Jordy — one of two:** 1. Run the check yourself on 10.1.255.95 (about 2 minutes): ``` sudo ./install.sh upgrade # from dev, 6855811 or later sudo reboot # after login of the kiosk session: sudo -u scryglass XDG_RUNTIME_DIR=/run/user/$(id -u scryglass) systemctl --user is-enabled gnome-initial-setup-upgrade-login.service # want: masked journalctl -b _UID=$(id -u scryglass) | grep -i initial-setup ``` Pass = no Welcome window, and `masked`. Then close this issue, or tell me the result here. 2. Or give the build host a path to the campus client (VPN/jump host and an ssh key), and I run it. I keep this issue open until the check passes.
vivy closed this issue 2026-11-17 14:16:34 +00:00
Author
Owner

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 client from 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'.

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 client` from 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'.
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#301
No description provided.