Originally created by @Jaehaks on GitHub (Aug 16, 2024).
Describe the bug
In the middle of using komorebi, sometimes the keymaps don't work. komorebi.exe and whkd.exe process is still running. komorebi works fine. because terminal command works when the problem invoked.
But I think whkd missed some connection with komorebi.
It can be restore after I kill the whkd process and restart with komorebi start --whkd while komorebi is running.
But the problem is issued again.
I don't know what makes this situation exactly
All behaviors what I did are moving between stacks and capturing some picture and moving between workspace.
I think the problem occurs more fast When I move between stacks a lot.
Although the problem occurs, komorebi check said that komorebi found the whkdrc.
To Reproduce
Steps to reproduce the behavior:
move between stacked window
move between workspaces
capture some screenshots
Expected behavior whkd doesn't loss connection with komorebi
Screenshots and Videos
Operating System
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.19044 N/A build 19044
komorebic check Output
Provide the output of komorebic check
For example:
KOMOREBI_CONFIG_HOME detected: C:\Users\USER\.config\Dotfiles\komorebi
Looking for configuration files in C:\Users\USER\.config\Dotfiles\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\USER\.config\Dotfiles\komorebi\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Additional context
Originally created by @Jaehaks on GitHub (Aug 16, 2024).
**Describe the bug**
In the middle of using `komorebi`, sometimes the keymaps don't work.
`komorebi.exe` and `whkd.exe` process is still running.
`komorebi` works fine. because terminal command works when the problem invoked.
But I think `whkd` missed some connection with `komorebi`.
It can be restore after I kill the whkd process and restart with `komorebi start --whkd` while komorebi is running.
But the problem is issued again.
I don't know what makes this situation exactly
All behaviors what I did are moving between stacks and capturing some picture and moving between workspace.
I think the problem occurs more fast When I move between stacks a lot.
Although the problem occurs, `komorebi check` said that komorebi found the whkdrc.
**To Reproduce**
Steps to reproduce the behavior:
1. move between stacked window
2. move between workspaces
3. capture some screenshots
**Expected behavior**
`whkd` doesn't loss connection with komorebi
**Screenshots and Videos**
**Operating System**
```
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.19044 N/A build 19044
```
**`komorebic check` Output**
Provide the output of `komorebic check`
For example:
```
KOMOREBI_CONFIG_HOME detected: C:\Users\USER\.config\Dotfiles\komorebi
Looking for configuration files in C:\Users\USER\.config\Dotfiles\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\USER\.config\Dotfiles\komorebi\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
```
**Additional context**
adam
added the bug label 2026-01-05 14:50:48 +01:00
It seems to be not solved yet although I use the nightly version which is comitted at 7f0b54c
The similar issues occurs like #1132, and @LGUG2Z said it was solved. but This didn't work for me.
I raised this issue in whkd#49 because I thought it is whkd issue, but It seems not. This issue is happened also when I use .ahk.
I think progress is being made to resolve it.
@Jaehaks commented on GitHub (Dec 5, 2024):
@Lunala666
It seems to be not solved yet although I use the nightly version which is comitted at [7f0b54c]([https://github.com/LGUG2Z/komorebi/commit/7f0b54c35e932e5fc753d5e24738de703763dcc)
The similar issues occurs like #1132, and @LGUG2Z said it was solved. but This didn't work for me.
I raised this issue in [whkd#49](https://github.com/LGUG2Z/whkd/issues/49) because I thought it is whkd issue, but It seems not. This issue is happened also when I use `.ahk`.
I think progress is being made to resolve it.
Similar issue for me where workspace related keybinds won't work after a while. Other keybinds (like for opening terminal) still work though. Edit: Restarting whkd doesn't fix it, requires komorebi itself to be restarted.
@gursuj commented on GitHub (Dec 12, 2024):
Similar issue for me where workspace related keybinds won't work after a while. Other keybinds (like for opening terminal) still work though. Edit: Restarting whkd doesn't fix it, requires komorebi itself to be restarted.
At now, the nightly version seems not occur the issue in my old PC although I try swap window iteratively.
But I cannot be sure about komorebic fixed it.
@Jaehaks commented on GitHub (Mar 6, 2025):
@adamparzi
At now, the nightly version seems not occur the issue in my old PC although I try swap window iteratively.
But I cannot be sure about komorebic fixed it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Jaehaks on GitHub (Aug 16, 2024).
Describe the bug
In the middle of using
komorebi, sometimes the keymaps don't work.komorebi.exeandwhkd.exeprocess is still running.komorebiworks fine. because terminal command works when the problem invoked.But I think
whkdmissed some connection withkomorebi.It can be restore after I kill the whkd process and restart with
komorebi start --whkdwhile komorebi is running.But the problem is issued again.
I don't know what makes this situation exactly
All behaviors what I did are moving between stacks and capturing some picture and moving between workspace.
I think the problem occurs more fast When I move between stacks a lot.
Although the problem occurs,
komorebi checksaid that komorebi found the whkdrc.To Reproduce
Steps to reproduce the behavior:
Expected behavior
whkddoesn't loss connection with komorebiScreenshots and Videos
Operating System
komorebic checkOutputProvide the output of
komorebic checkFor example:
Additional context
@Gal456-cyber commented on GitHub (Sep 30, 2024):
also happens to me simply after komorebi runs for more than 30 min to an hour
@Lunala666 commented on GitHub (Dec 4, 2024):
Did you manage to solve this problem, and if so how?
@Jaehaks commented on GitHub (Dec 5, 2024):
@Lunala666
It seems to be not solved yet although I use the nightly version which is comitted at 7f0b54c
The similar issues occurs like #1132, and @LGUG2Z said it was solved. but This didn't work for me.
I raised this issue in whkd#49 because I thought it is whkd issue, but It seems not. This issue is happened also when I use
.ahk.I think progress is being made to resolve it.
@gursuj commented on GitHub (Dec 12, 2024):
Similar issue for me where workspace related keybinds won't work after a while. Other keybinds (like for opening terminal) still work though. Edit: Restarting whkd doesn't fix it, requires komorebi itself to be restarted.
@adamparzi commented on GitHub (Feb 28, 2025):
Still have the issue, any fix?
@Jaehaks commented on GitHub (Mar 6, 2025):
@adamparzi
At now, the nightly version seems not occur the issue in my old PC although I try swap window iteratively.
But I cannot be sure about komorebic fixed it.