Stage 22 — Hold Bindings & Session Exit

What it is. Physical keys can trigger an action only after remaining pressed for a configured duration, and 0xinctl quit provides a clean, compositor-owned session exit.

Gate: Holding the FP5 power key for two seconds opens a fuzzel session menu. Releasing it early does nothing. Choosing logout returns to Phrog.

Hold mappings

hold = , XF86PowerOff, 2000, spawn, session-menu

The format is MODS, KEY, MILLISECONDS, ACTION[, ARG]. Durations from 100 through 60000 milliseconds are accepted. A press arms a Wayland event-loop timer; release cancels it. Both events are consumed so applications never see an unmatched power-key press or release.

This mechanism is general input mapping and is not FP5-specific. If a chord has both bind and hold mappings, release before the threshold runs the normal bind; reaching the threshold runs only the hold action. The FP5 profile currently uses only the two-second session-menu action and reserves short press for a touch-capable secure lock client.

Clean session exit

0xinctl quit

The control request asks 0xin to terminate its Wayland display loop normally. The FP5 wrapper then exits and greetd/Phrog regains control. This is the supported interactive equivalent of terminating 0xin from an SSH recovery shell.

The included FP5 menu is a small fuzzel dmenu script with logout, reboot, shutdown, and cancel choices. Reboot and shutdown call systemctl so logind and the system policy layer remain responsible for authorization. The script replaces the earlier Hyprland-specific hypr-phone-menu, whose logout action depended on hyprctl dispatch exit.

Secure locking is implemented separately through ext-session-lock-v1; see Stage 23.