Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starting in an awake/prompt visible state #161

Open
NathanC opened this issue Nov 7, 2022 · 0 comments
Open

Starting in an awake/prompt visible state #161

NathanC opened this issue Nov 7, 2022 · 0 comments

Comments

@NathanC
Copy link

NathanC commented Nov 7, 2022

I'd like to have it so that, when invoking xsecurelock, it starts in an awake state where the prompt can be seen and then timing out (or making it so it does not timeout on startup, alternatively).

I've tried adding XSECURELOCK_BLANK_TIMEOUT as both 5 and -1, and neither work, despite the docs saying The time is measured since the closing of the auth window or xsecurelock startup, but maybe I'm misunderstanding that options?

I've also looked into these directions, but they're more for waking a pre-existing secure lock session it looks like.

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

No branches or pull requests

1 participant