Operating System
OS Name: Microsoft Windows 11 Home Single Language
OS Version: 10.0.22631 N/A Build 22631
komorebic check Output
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\omarj
Looking for configuration files in C:\Users\omarj
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\omarj.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Additional context
My config is the same one in the documentation.
I tried testing it on 2 different PCs, but the issue continues.
What if I pressed ALT + SHIFT + l in the first workspace? Everything works as expected the programs switch places.
Assuming we have 2 workspaces:
The first workspace contains 2 program
The second workspace contains 1 program
When going to the second workspace and pressing ALT + SHIFT + l it breaks ALT + N, so I can't go back to the first workspace by pressing ALT + 1.
Originally created by @H7ioo on GitHub (May 27, 2024).
**Describe the bug**
ALT + N stops working after using ALT + SHIFT + l on a workspace with one program
**To Reproduce**
Steps to reproduce the behavior:
1. Follow the documentation and install komorebi
1. Run komorebi by typing "komorebic start --whkd" in the terminal
2. Open 3 programs and send one of them to another workspace by pressing ALT + SHIFT + 2
3. Go to the second workspace if you are not there by pressing ALT + 2
4. Press ALT + SHIFT + l
5. Press ALT + 1 -> Bug
**Expected behavior**
It should navigate to N workspace without any issues.
**Screenshots and Videos**
https://github.com/LGUG2Z/komorebi/assets/37945078/1b603afb-3822-4d3a-acc4-dd5b0d756db4
**Operating System**
OS Name: Microsoft Windows 11 Home Single Language
OS Version: 10.0.22631 N/A Build 22631
**`komorebic check` Output**
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\omarj
Looking for configuration files in C:\Users\omarj
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\omarj\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
**Additional context**
My config is the same one in the documentation.
I tried testing it on 2 different PCs, but the issue continues.
What if I pressed ALT + SHIFT + l in the first workspace? Everything works as expected the programs switch places.
---
Assuming we have 2 workspaces:
The first workspace contains 2 program
The second workspace contains 1 program
When going to the second workspace and pressing ALT + SHIFT + l it breaks ALT + N, so I can't go back to the first workspace by pressing ALT + 1.
adam
added the bug label 2026-01-05 14:50:19 +01:00
I tried following these instructions step by step but I was not able to reproduce. alt + shift + l on ws2 triggers a noop error because it's the only window on that workspace, and then the switch back to ws1 succeeds:
2024-05-27T16:42:32.988895Z INFO process_command{MoveWindow(Right)}:move_container_in_direction{direction=Right}: komorebi::window_manager: moving container
2024-05-27T16:42:32.989375Z ERROR komorebi::process_command: there is no container or monitor in this direction
2024-05-27T16:42:36.877954Z INFO process_command{FocusWorkspaceNumber(0)}:focus_monitor{idx=0}: komorebi::window_manager: focusing monitor
2024-05-27T16:42:36.878710Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}: komorebi::window_manager: focusing workspace
2024-05-27T16:42:36.879230Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}:focus_workspace{idx=0}: komorebi::monitor: focusing workspace
2024-05-27T16:42:36.887953Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}:focus_window{idx=0}: komorebi::container: focusing window
2024-05-27T16:42:36.901505Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}:update_focused_workspace{follow_focus=false trigger_focus=true}: komorebi::window_manager: updating
2024-05-27T16:42:36.925552Z INFO process_command{FocusWorkspaceNumber(0)}: komorebi::process_command: processed
@LGUG2Z commented on GitHub (May 27, 2024):
I tried following these instructions step by step but I was not able to reproduce. `alt + shift + l` on ws2 triggers a noop error because it's the only window on that workspace, and then the switch back to ws1 succeeds:
```
2024-05-27T16:42:32.988895Z INFO process_command{MoveWindow(Right)}:move_container_in_direction{direction=Right}: komorebi::window_manager: moving container
2024-05-27T16:42:32.989375Z ERROR komorebi::process_command: there is no container or monitor in this direction
2024-05-27T16:42:36.877954Z INFO process_command{FocusWorkspaceNumber(0)}:focus_monitor{idx=0}: komorebi::window_manager: focusing monitor
2024-05-27T16:42:36.878710Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}: komorebi::window_manager: focusing workspace
2024-05-27T16:42:36.879230Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}:focus_workspace{idx=0}: komorebi::monitor: focusing workspace
2024-05-27T16:42:36.887953Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}:focus_window{idx=0}: komorebi::container: focusing window
2024-05-27T16:42:36.901505Z INFO process_command{FocusWorkspaceNumber(0)}:focus_workspace{idx=0}:update_focused_workspace{follow_focus=false trigger_focus=true}: komorebi::window_manager: updating
2024-05-27T16:42:36.925552Z INFO process_command{FocusWorkspaceNumber(0)}: komorebi::process_command: processed
```
I tried again on my laptop with a fresh install. I closed all the apps from the task manager and I tried again. The same issue happens and my cursor starts flickering. Also, I noticed that all the shortcuts stop working not just ALT + N.
@H7ioo commented on GitHub (May 27, 2024):
I tried again on my laptop with a fresh install. I closed all the apps from the task manager and I tried again. The same issue happens and my cursor starts flickering. Also, I noticed that all the shortcuts stop working not just ALT + N.
After playing around with it I figured out the constraints of the bug.
Only the second workspace causes the bug, other workspaces work fine.
The workspace should have only one program.
Only push to the right produces the bug (ALT + SHIFT + L)
Update:
Third space produces the bug when ALT + SHIFT + J is pressed
@H7ioo commented on GitHub (May 27, 2024):
After playing around with it I figured out the constraints of the bug.
1. Only the second workspace causes the bug, other workspaces work fine.
2. The workspace should have only one program.
3. Only push to the right produces the bug (ALT + SHIFT + L)
Update:
Third space produces the bug when ALT + SHIFT + J is pressed
I'm still not able to reproduce this, it looks like your desktop thinks there is another window in that workspace, or a window on a monitor in the selected direction.
Post your config file and an output of komorebic state immediately before triggering the panic, let's see if there are any clues in there
@LGUG2Z commented on GitHub (May 28, 2024):
I'm still not able to reproduce this, it looks like your desktop thinks there is another window in that workspace, or a window on a monitor in the selected direction.
Post your config file and an output of `komorebic state` immediately before triggering the panic, let's see if there are any clues in there
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 @H7ioo on GitHub (May 27, 2024).
Describe the bug
ALT + N stops working after using ALT + SHIFT + l on a workspace with one program
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should navigate to N workspace without any issues.
Screenshots and Videos
https://github.com/LGUG2Z/komorebi/assets/37945078/1b603afb-3822-4d3a-acc4-dd5b0d756db4
Operating System
OS Name: Microsoft Windows 11 Home Single Language
OS Version: 10.0.22631 N/A Build 22631
komorebic checkOutputNo KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\omarj
Looking for configuration files in C:\Users\omarj
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\omarj.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Additional context
My config is the same one in the documentation.
I tried testing it on 2 different PCs, but the issue continues.
What if I pressed ALT + SHIFT + l in the first workspace? Everything works as expected the programs switch places.
Assuming we have 2 workspaces:
The first workspace contains 2 program
The second workspace contains 1 program
When going to the second workspace and pressing ALT + SHIFT + l it breaks ALT + N, so I can't go back to the first workspace by pressing ALT + 1.
@LGUG2Z commented on GitHub (May 27, 2024):
I tried following these instructions step by step but I was not able to reproduce.
alt + shift + lon ws2 triggers a noop error because it's the only window on that workspace, and then the switch back to ws1 succeeds:@H7ioo commented on GitHub (May 27, 2024):
I tried again on my laptop with a fresh install. I closed all the apps from the task manager and I tried again. The same issue happens and my cursor starts flickering. Also, I noticed that all the shortcuts stop working not just ALT + N.
@H7ioo commented on GitHub (May 27, 2024):
Error from the log:
@H7ioo commented on GitHub (May 27, 2024):
After playing around with it I figured out the constraints of the bug.
Update:
Third space produces the bug when ALT + SHIFT + J is pressed
@LGUG2Z commented on GitHub (May 28, 2024):
I'm still not able to reproduce this, it looks like your desktop thinks there is another window in that workspace, or a window on a monitor in the selected direction.
Post your config file and an output of
komorebic stateimmediately before triggering the panic, let's see if there are any clues in there@H7ioo commented on GitHub (May 29, 2024):
Config
State
@H7ioo commented on GitHub (May 29, 2024):
New constraint:
VerticalStack -> ALT + SHIFT + l breaks it
HorizontalStack -> ALT + SHIFT + j breaks it
@LGUG2Z commented on GitHub (May 31, 2024):
Should be fixed here ^