Skip to content

No login screen: the session starts locked - #81

Merged
henrikklee merged 5 commits into
mainfrom
login-starts-locked
Nov 19, 2026
Merged

henrikklee merged 5 commits into
mainfrom
login-starts-locked

Conversation

@henrikklee

Copy link
Copy Markdown
Contributor

The lock and the login screen looked the same but were two programs that could drift apart. Now there is one: the tablet logs straight in at boot and the session starts locked. The PIN screen you see at boot is the lock.

What changes for a user

  • Boot shows the lock, the same screen as after Power or a closed cover, with the PIN check the installer set up for the lock.
  • After the PIN, the desktop is there at once: the shell and apps load behind the lock, not after the PIN.
  • Logout stays (it's upstream's entry). It closes every app and starts a fresh desktop behind the lock instead of going back to a separate login screen.
  • Nothing of the desktop shows before the PIN. The compositor's startup cover only lifts once the lock is drawn; if the lock can't be taken (no PIN check configured), the screen stays covered.

How

  • greetd logs the tablet user in once per boot (initial_session) through a new PAM service, greetd-autologin, that admits only the tablet user and has no password step. greetd 0.10 reads the auto-login's service from [general].
  • Session script: arch-ipad-login-session sets OMARCHY_START_LOCKED, and restarts labwc after a logout or crash. Three immediate failures in a row stop it, and greetd's fallback (omarchy-session-failed) logs why; serial and SSH are available as always.
  • The lock service takes the lock at start, lifts the startup cover once the lock is drawn, and writes the installer's readiness record, /run/omarchy-session/ready.json. Orchard reads that path from the release manifest, so orchard needs no change.
  • Removed: the login screen's shell, its labwc config, its theme snapshot and the publishing behind it. An update deletes the old snapshot.

Tested

In the Orchard simulator, with greetd restarted to simulate a boot:

  • starts locked, ready record after about 3 s
  • the PIN unlocks
  • Logout lands back on the lock in the same login session
  • the guard against an immediately failing desktop stops after three tries
  • the PAM service refuses root and greeter

Not yet on a real tablet. Tests pass apart from the image-picker tests that need Linux.

Follow-up for orchard, not blocking: the installer still writes the PIN check into /etc/pam.d/greetd, which nothing uses any more.

greetd logs the tablet in at boot without a prompt (its initial session,
PAM service greetd-autologin: no password step, the tablet user only) and
the session starts locked: the shell takes the lock as soon as its PIN
check is known, and Labwc's startup cover lifts only once the lock is
drawn, so nothing of the desktop shows before the PIN. Without a PIN
check the lock cannot be taken and the cover stays.

- Logout (and a crashed desktop) starts Labwc again behind the lock, in
  the same login session. Three immediate ends in a row stop it; greetd's
  default session (omarchy-session-failed) then says so in the journal,
  and serial and SSH stay as always.
- The installer's ready record is the lock's first drawn frame:
  /run/omarchy-session/ready.json, named in the release manifest.
- Gone: the login screen's shell, its Labwc config, its theme snapshot
  and the publishing behind it; an update removes the old snapshot.

The lock and the login screen were one view in two programs; now there is
one, which the status cluster and later disk encryption build on.

Assisted-by: LLM
omarchy-system logout shows its OSD after 2 s and waits for the session to
go down. A logout now ends only the desktop and the next one starts behind
the lock in the same login session, where the delayed OSD landed and
stayed. Once Labwc is told to exit, the delayed OSD is cancelled.

Assisted-by: LLM
A logout only restarts the desktop behind the lock, which is almost always
quicker than upstream's 2 s before its OSD, so nothing showed. Logout now
shows it at once, until the desktop is gone; reboot and shutdown keep the
delay.

Assisted-by: LLM
@henrikklee
henrikklee merged commit 569600a into main Nov 19, 2026
9 checks passed
@henrikklee
henrikklee deleted the login-starts-locked branch November 19, 2026 21:07
@henrikklee
henrikklee restored the login-starts-locked branch November 19, 2026 21:07
@henrikklee
henrikklee deleted the login-starts-locked branch November 19, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant