My linux config and rc files https://git.sommerfeld.dev/dotfiles/atom/dot_config/sway/executable_resume-lock-grace.sh?h=master 2026-05-13T12:43:36Z 2026-05-13T12:43:36Z sommerfeld sommerfeld@sommerfeld.dev 2026-05-13T12:43:36Z urn:sha1:54662c8b95ce260ad0a8718e14850c96a66242ef Replaces the resume-lock-grace.sh + after-resume hook from the previous commit with the simpler observation that sway already provides a wake grace for free: it pauses the idle counter during suspend and resets it on the first input event post-resume, so the existing timeout 300 lock naturally gives ~5min to interact before locking. Just dropping the before-sleep lock is enough; the script and after-resume directive were overcomplicating it. 2026-05-13T12:43:36Z sommerfeld sommerfeld@sommerfeld.dev 2026-05-13T12:43:36Z urn:sha1:d7fac4bbf607a894219065dc9b87f6d495d9ebab Two related session-idle improvements: 1. ScreenSaver inhibit bridge. Browsers (LibreWolf/Chromium flatpaks) ask the session not to idle via the legacy org.freedesktop.ScreenSaver D-Bus API during video calls and fullscreen video; swayidle only honors logind's BlockInhibited property. Add inhibridge as a user unit to translate the former into the latter, so e.g. a Google Meet tab now keeps the screen from locking, dimming and (downstream) suspending. 2. Post-resume grace period. Locking on before-sleep meant every wake demanded the password even for a quick check. Replace with: before-sleep -> only pause media after-resume -> resume-lock-grace.sh 30 The grace script runs a one-shot swayidle that locks iff the user stays idle for 30s after the wake, with a watchdog that exits as soon as swaylock comes up (or after a hard cap) so it never lingers alongside the main swayidle. The 5-min main idle-lock and explicit loginctl lock-session paths are unchanged.