lytedev/nix
1
0
Fork 2
Code Pull requests 9 Activity Actions

feat(greeter): make noctalia-greeter the fleet default #1135

Open
lytedev wants to merge 1 commit from propose/noctalia-greeter-default into main
pull from: propose/noctalia-greeter-default
merge into: lytedev:main
Conversation 0 Commits 1 Files changed 4 +11 -20
lytedev commented 2026-08-31 09:31:41 -05:00
Owner
Copy link

Follows the shell default onto the login screen. The launch path is picked automatically from niri.osk, so no host can end up keyboard-less without an OSK; the Steam Decks enable no greeter at all so it is inert there. Please review the commit.

Follows the shell default onto the login screen. The launch path is picked automatically from niri.osk, so no host can end up keyboard-less without an OSK; the Steam Decks enable no greeter at all so it is inert there. Please review the commit.
feat(greeter): make noctalia-greeter the fleet default
All checks were successful
/ check-format (push) Successful in 10s
Details
/ build (push) Successful in 16m29s
Details
a73d0460af 
Follows the shell default onto the login screen, so a host looks the same from
boot menu to desktop, and drops the now redundant per-host overrides on dragon,
flab and foxtrot.

Safe on every host because nothing about it is chosen by hand: greeter.nix
picks the launch path from niri.osk. An osk host runs the greeter as a plain
Wayland client inside the minimal niri session alongside wvkbd; a keyboard host
gets upstream/s bundled compositor, which has no layer-shell and so no room for
an on-screen keyboard. There is no combination an operator can select that
leaves a keyboard-less machine without a way to type.

I had argued against this default on the grounds that noctalia-greeter is "only
safe on keyboard-less hosts through the niri path", which was both backwards and
overstated. Checking the fleet rather than asserting: no host is exposed. The
laptops all have keyboards, and the two devices that lack one — the Steam Decks —
do not enable a greeter at all (greeter.enable = false, services.greetd.enable =
false), so this default is inert on exactly the machines it could have hurt.
The real reservation was only that eight hosts have never been watched booting
into it, which is a reason to roll out on each host/s next rebuild rather than a
reason not to change the default.

Tested: thinker resolves to the bundled-compositor path and fennec to the
niri-hosted one, and both build; the Decks resolve to noctalia but with
greeter.enable false, so the whole block is inert there.
All checks were successful
/ check-format (push) Successful in 10s
Required
Details
/ build (push) Successful in 16m29s
Required
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin propose/noctalia-greeter-default:propose/noctalia-greeter-default
git switch propose/noctalia-greeter-default
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something is wrong

  
enhancement
New feature

  
question
Awaiting information

  
scary
Potentially problematic change

  
upstream
Awaiting upstream changes

No labels
bug
enhancement
question
scary
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
lytedev/nix!1135
No description provided.