Originally created by @pettys on GitHub (Sep 19, 2025).
Summary
I am trying komorebi for the first time; it was crashing a lot (twice in the first 10 minutes of use), so I thought maybe it was my multi-monitor setup, so tried to use monitor-info to configure it. It crashed, so I tried starting over with this series of commands:
> komorebic quickstart
The following example files were written:
C:\Users\nnn\komorebi.json
C:\Users\nnn\komorebi.bar.json
C:\Users\nnn\applications.json
C:\Users\nnn\.config\whkdrc
You can now run komorebic start --whkd --bar
> komorebic monitor-info
thread 'main' panicked at komorebic\src\main.rs:1526:23:
No connection could be made because the target machine actively refused it. (os error 10061)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> komorebic --version
komorebic 0.1.38
tag:v0.1.38
commit_hash:ffa76ea2
build_time:2025-09-13 18:40:25 +00:00
build_env:rustc 1.89.0 (29483883e 2025-08-04),stable-x86_64-pc-windows-msvc
I do have three monitors in an interesting configuration:
Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
Per the summary, it's the quickstart version of this file.
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\nnn
Looking for configuration files in C:\Users\nnn
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\nnn.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Originally created by @pettys on GitHub (Sep 19, 2025).
### Summary
I am trying komorebi for the first time; it was crashing a lot (twice in the first 10 minutes of use), so I thought maybe it was my multi-monitor setup, so tried to use `monitor-info` to configure it. It crashed, so I tried starting over with this series of commands:
```
> komorebic quickstart
The following example files were written:
C:\Users\nnn\komorebi.json
C:\Users\nnn\komorebi.bar.json
C:\Users\nnn\applications.json
C:\Users\nnn\.config\whkdrc
You can now run komorebic start --whkd --bar
> komorebic monitor-info
thread 'main' panicked at komorebic\src\main.rs:1526:23:
No connection could be made because the target machine actively refused it. (os error 10061)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> komorebic --version
komorebic 0.1.38
tag:v0.1.38
commit_hash:ffa76ea2
build_time:2025-09-13 18:40:25 +00:00
build_env:rustc 1.89.0 (29483883e 2025-08-04),stable-x86_64-pc-windows-msvc
```
I do have three monitors in an interesting configuration:
<img width="366" height="318" alt="Image" src="https://github.com/user-attachments/assets/9145bda3-4978-4a11-8cca-b97bc5be28ab" />
### Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
komorebic 0.1.38
tag:v0.1.38
commit_hash:ffa76ea2
build_time:2025-09-13 18:40:25 +00:00
build_env:rustc 1.89.0 (29483883e 2025-08-04),stable-x86_64-pc-windows-msvc
### Komorebi Configuration
```json
Per the summary, it's the quickstart version of this file.
```
### Hotkey Configuration
Per the summary, it's the quickstart version of this file.
### Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\nnn
Looking for configuration files in C:\Users\nnn
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\nnn\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
adam
added the bug label 2026-01-05 14:52:21 +01:00
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 @pettys on GitHub (Sep 19, 2025).
Summary
I am trying komorebi for the first time; it was crashing a lot (twice in the first 10 minutes of use), so I thought maybe it was my multi-monitor setup, so tried to use
monitor-infoto configure it. It crashed, so I tried starting over with this series of commands:I do have three monitors in an interesting configuration:
Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
komorebic 0.1.38
tag:v0.1.38
commit_hash:ffa76ea2
build_time:2025-09-13 18:40:25 +00:00
build_env:rustc 1.89.0 (29483883e 2025-08-04),stable-x86_64-pc-windows-msvc
Komorebi Configuration
Hotkey Configuration
Per the summary, it's the quickstart version of this file.
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\nnn
Looking for configuration files in C:\Users\nnn
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\nnn.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@LGUG2Z commented on GitHub (Sep 19, 2025):
komorebi needs to be running in order to process the command you are sending
@pettys commented on GitHub (Sep 23, 2025):
Got it, thx.