konishi: autologin straight into hyprlock
CI / lint (push) Successful in 1m11s
CI / eval (push) Failing after 2m28s

SDDM auto-logs naps62 in and Hyprland locks immediately via hyprlock
(exec-once), so a cold boot lands on the themeable lock screen instead of
the SDDM greeter. Safe here (no FDE makes SDDM-vs-autologin marginal) and it
lets Moonlight reach the box after a cold boot, not just from suspend, since
Sunshine only runs once a session exists. konishi-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Miguel Palhas
2026-07-05 15:55:22 +01:00
parent 4f2438d383
commit 75198e4429
2 changed files with 19 additions and 0 deletions
+15
View File
@@ -43,6 +43,21 @@
${pkgs.xrandr}/bin/xrandr --dpi 160
'';
# Boot straight into a locked Hyprland instead of the SDDM greeter: SDDM
# auto-logs naps62 in, the session starts, and hyprlock (exec-once in the home
# config) immediately locks it — so the first thing you see is hyprlock, the
# one themeable lock screen. Safe on this box: no full-disk encryption means
# SDDM-vs-autologin is a marginal boundary anyway, and it also lets Moonlight
# reach the box after a *cold boot* (Sunshine is a user service that only runs
# once a session exists), not just from suspend. konishi-only — never arrakis.
services.displayManager = {
autoLogin = {
enable = true;
user = "naps62";
};
defaultSession = "hyprland";
};
networking.nameservers = [
"100.100.100.100"
"10.1.10.1"