starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: komorebic monitor-info panic on v0.1.38 #677

New Issue
Closed
opened 2026-01-05 14:52:21 +01:00 by adam · 2 comments
adam commented 2026-01-05 14:52:21 +01:00
Owner
Copy Link

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:

Image

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

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

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
adam closed this issue 2026-01-05 14:52:21 +01:00
adam commented 2026-01-05 14:52:22 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Sep 19, 2025):

komorebi needs to be running in order to process the command you are sending

@LGUG2Z commented on GitHub (Sep 19, 2025): komorebi needs to be running in order to process the command you are sending
adam commented 2026-01-05 14:52:22 +01:00
Author
Owner
Copy Link

@pettys commented on GitHub (Sep 23, 2025):

Got it, thx.

@pettys commented on GitHub (Sep 23, 2025): Got it, thx.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#677
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?