Repository navigation
No login screen: the session starts locked - #81
Merged
Merged
Conversation
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
Assisted-by: LLM
This was referenced Nov 19, 2026
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
# Conflicts: # CHANGELOG.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
How
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].arch-ipad-login-sessionsetsOMARCHY_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./run/omarchy-session/ready.json. Orchard reads that path from the release manifest, so orchard needs no change.Tested
In the Orchard simulator, with greetd restarted to simulate a boot:
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.