-
-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Description
- Create listener (10-15s)
- Launch hypridle
- Inhibit locking within those 10-15s
- Wait & observe
Expected result:
Either:
- Hypridle would check if locking is inhibited every so often. If not, any previously inhibited listeners would be immediately run; or
- Once the inhibit condition is lifted, all previously inhibited listeners are reset to 0.
Observed result:
Once a listener is inhibited, it is not checked again even after the inhibit condition is no longer present.
My scenario:
KDE connect inhibits locking while my phone is connected. If I leave to the store, I expect to come back with my computer locked. This does not happen because the listener, once inhibited, is not revisited even after the phone is no longer connected.
Metadata
Metadata
Assignees
Labels
No labels