Lid Switch
#1660
Replies: 1 comment 1 reply
-
|
Hey there! Figured out that this config option fixed the issue because by saying it was the other thing I was activating something on the system that tricked it into thinking the touch-pad needs re-enabled. When that happened then the system also software bypassed the lid sensor and re-enabled the screen based on my hyprland config. Anyways hope this can help someone else! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Evening!
I love kanata as it has allowed me to get modtap functionality on a keyboard that has shoddy firmware and on my laptop easily.
I am however running into trouble while configuring hyprland on my fw13.
I've set a rule that says when the lidswitch turns on vs off that the laptop monitor turns off and on respectively.
This function works with kanata specifically disabled.
When I have kanata turned on any keypress seems to trigger overriding the lidswitch and triggers the rule re-enabling the monitor.
It seems like it has something to do with kanata since the behavior ceased upon turning this service off I just really like modding my caps key and am scared of losing that. Is this a feature I can configure to allow for this workflow or am I gonna be stuck with this?
Logs showing the input event that triggers the lidswitch without moving the lid shown below.

I'm assuming whatever libinput event 5 resume touchpad is causes the laptop to freak out and think I'm using the laptop keyboard so it must have a faulty signal or something of the like.
Beta Was this translation helpful? Give feedback.
All reactions