Skip to content

Give the lock screen longer before it blanks the display - #8561

Open
robouk wants to merge 2 commits into
omacom:quattrofrom
robouk:lock-blank-timeout
Open

robouk wants to merge 2 commits into
omacom:quattrofrom
robouk:lock-blank-timeout

Conversation

@robouk

@robouk robouk commented Aug 27, 2026 •

Copy link
Copy Markdown

idleBlankTimer turns the display off five seconds after the last input on the lock screen. That is shorter than it takes to wake the machine, focus the password field and start typing, so the panel goes dark mid-entry and has to be nudged awake again, often more than once per unlock.

Raise the interval to thirty seconds. Activity still re-arms the timer, so an untouched lock screen blanks one interval after the last input.

idleBlankTimer turns the display off five seconds after the last input on
the lock screen. That is shorter than it takes to wake the machine, focus
the password field and start typing, so the panel goes dark mid-entry and
has to be nudged awake again, often more than once per unlock.

Raise the interval to thirty seconds. Activity still re-arms the timer, so
an untouched lock screen blanks one interval after the last input.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WDCXKUYgyKMb1ACcoBAbro
Copilot AI balanced review requested due to automatic review settings August 27, 2026 09:45

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Raises the lock-screen display blanking delay from 5 to 30 seconds.

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

Changes:

  • Extends the idle blank timer.
  • Documents the timing rationale.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

// Long enough to wake the machine, read the field and type a password
// without the panel going dark mid-entry. Any activity re-arms it, so an
// untouched lock screen still blanks one interval after the last input.
interval: 30000

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added an interval assertion to lock-blank-fingerprint-test.sh. Confirmed it fails when the interval goes back to 5000.

Pins the thirty second interval so a revert to five seconds fails
./test/shell rather than passing silently.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WDCXKUYgyKMb1ACcoBAbro
@prabhatCH

Copy link
Copy Markdown

Hardware report: Dell XPS 15 9500, Goodix 27c6:533c, Omarchy 4.0.6-1, fprintd 1.94.5-2, libfprint-tod 1.95.2+tod1-1, and libfprint-goodix-53xc 0.0.6-2.

Additional real-hardware evidence for the 5-to-30-second change: after opening the lid, the owner saw a password field on a black background, followed by the panel turning completely off. A key press restored the full lock screen, making the sequence feel like flicker or a failed wake.

We changed the local lock plugin's blank timeout from 5 to 30 seconds, together with fingerprint resume coordination (preserve known enrollment, delay rearming by 1.5 seconds after resume, and clear the display-blanked state). After explicitly restarting the unlocked shell, the owner confirmed the resulting lid-open / fingerprint unlock flow works without keyboard or mouse input.

The timeout change was not tested independently, so this is supporting UX evidence, not proof that this PR alone fixes the fingerprint/resume issue. The longer window gives the user time to see the restored lock screen and present a finger before blanking. Related resume work: #9919.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants