Skip to content

Add fingerprint authentication support via AuthPrompt signals - #28

Draft
nestor-lobo-work wants to merge 1 commit into
nick-redwill:mainfrom
nestor-lobo-work:nestor-lobo-work-add-fingerprint-support
Draft

Add fingerprint authentication support via AuthPrompt signals#28
nestor-lobo-work wants to merge 1 commit into
nick-redwill:mainfrom
nestor-lobo-work:nestor-lobo-work-add-fingerprint-support

Conversation

@nestor-lobo-work

Copy link
Copy Markdown

Motivation

The extension's blur/pause effects only activate when the password prompt is shown, but GNOME's lock screen also supports fingerprint authentication via fprintd. Users with fingerprint readers don't get the visual effects during biometric verification.

Approach

Hooks into the lock dialog's AuthPrompt signals to detect fingerprint activity:

  • authPrompt.next signal -- fires when the auth prompt transitions to fingerprint verification (e.g. "Place your finger on the reader"), triggering the same _onPromptShow() blur/pause effects as the password prompt.
  • _onVerificationComplete override -- ensures prompt effects apply during a successful fingerprint unlock transition before the screen fully unlocks.
  • Cleanup -- disconnects the authPrompt signals in disable() to avoid leaks.

This means fingerprint auth now behaves identically to password auth regarding all prompt-related settings (blur change, pause, grayscale).

Listen to the lock dialog's AuthPrompt 'next' signal to detect when
fingerprint verification is active (e.g. 'Place your finger' message),
triggering the same blur/pause effects as the password prompt.

Also hooks into _onVerificationComplete to apply prompt effects during
successful fingerprint unlock transitions.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@nick-redwill

nick-redwill commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Hi @nestor-lobo-work, and thanks for your contribution!

Unfortunately, I can't verify whether it works since I don't have a fingerprint scanner to test it with.

That said, after looking through the code, I noticed a few issues. In particular, _onVerificationComplete doesn't appear to exist. On the other hand, the authPrompt.next signal does exist, so that part of the implementation looks legitimate if it's working on your setup.

If it genuinely works as expected on your setup, and you remove the redundant code, I'll merge it into the main branch.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants