otter-greeter

otter-greeter runs before your user compositor session starts.

Components

Binary	Role
`otter-greeterd`	Root daemon: PAM, logind seats, AccountsService, IPC, session launch
`otter-greeter-ui`	Unprivileged Wayland login UI

The greeter UI runs on Hyprland for the login screen only. Your session compositor is separate.

After pikman install otter-shell, enable the systemd service:

sudo systemctl enable otter-greeter.service

System files installed:

A dedicated system user otter-greeter is created during package installation.

Main config: /etc/otter-shell/otter-greeter.conf

Setting	Default
Greeter compositor	`/usr/bin/start-hyprland -- --config /etc/otter-shell/otter-greeter-hyprland.conf`
Display VT	`7`
State path	`/var/lib/otter-greeter/state.conf`
Runtime sockets	`/run/otter-greeter/<seat>.sock`

Wayland sessions are discovered from configured .desktop directories. X11 sessions are ignored.

PAM handles password authentication
Fingerprint auth is PAM-controlled (via fprintd when configured)
Autologin runs once per daemon process per seat; failure falls back to interactive login
Expired-password flows use PAM conversation prompts on the auth surface
User listing prefers AccountsService; falls back to /etc/passwd for normal login users

otter-greeter depends on otter-wallpaper (same version), Hyprland (greeter compositor only), accountsservice, and adduser.