Screen turns off 30 seconds before it locks #43
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos#43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
iso/airootfs/etc/skel/.config/hypr/hypridle.conf: DPMS off at 480 s, lock at 510 s. For those 30 seconds, moving the mouse wakes an unlocked desktop, which feels like it should have been locked.Fix
Lock at or before DPMS off (e.g. lock 470 s, DPMS off 480 s), or make the DPMS listener run
loginctl lock-sessionfirst.Acceptance
When the screen wakes from DPMS-off, it's always locked.
Source: BOS v0.6.2 source review (tag dated 2026-09-19). Read AGENTS.md first. One issue per branch/PR. Add a CHANGELOG
[Unreleased]entry.PR: #62
Moved the idle lock timeout to 470 seconds, before DPMS turns the display off at 480 seconds, and added a changelog entry.
git diff --checkpasses. I checked the installed Hypridle CLI; it has no config-only validation option, so I did not start it in the active session.Reviewed PR #62 at head
d7c648322245555b6114773618fe9b4fea82cb7f.Acceptance map:
iso/airootfs/etc/skel/.config/hypr/hypridle.conf:27-31movesloginctl lock-sessionto 470 seconds, before the DPMS-off listener at:20-25(480 seconds). The 10-second lead satisfies the requested ordering, and activity waking the display after the DPMS timeout still returns to the already locked session.[Unreleased].CHANGELOG.md:19-21adds the corresponding entry.There are no tests in the diff. This is a declarative timeout-ordering change; the PR reports
git diff --checkpassed, but the idle daemon was not started for runtime validation. The latest head is based directly on currentmain; Forgejo reports it mergeable. No commit statuses are published, consistent with BOSAGENTS.md, which says ordinary PR pushes do not run CI.Verdict: Reviewed, looks ready to merge. BOS is on the release train, so I am leaving the merge to the user.