[BUG]: Following Documentation, But Unable to Start Komorebi #297

New Issue

2026-01-05T14:49:33+01:00

adam commented

2026-01-05 14:49:33 +01:00

Originally created by @snize on GitHub (Feb 16, 2024).

Describe the bug
I am setting up according to the Getting started in the documentation, but I am failing to start komorebi.

To Reproduce
Steps to reproduce the behavior:

Enabled long path support.
Installed komorebi and whkd with winget.
Download configuration files with komorebic quickstart
Then start komorebi with komorebic start --whkd
See bug

Expected behavior
I might be overlooking something, but I am proceeding as per the documentation and expect komorebi to start.

Screenshots and Videos

PowerShell 7.4.1
PS C:\Users\snize> komorebic start --whkd
Start-Process 'komorebi.exe' -WindowStyle hidden
Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again
Start-Process 'komorebi.exe' -WindowStyle hidden
Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again
Start-Process 'komorebi.exe' -WindowStyle hidden

I tried to call the binary directly to check the cause of the stop, referring to https://github.com/LGUG2Z/komorebi/discussions/499#discussioncomment-6489907.

PS C:\Users\snize> komorebi -c "$Env:USERPROFILE\komorebi.json"
2024-02-16T13:15:08.628937Z  INFO foreground_lock_timeout: komorebi::windows_api: current value of ForegroundLockTimeout is 0
2024-02-16T13:15:08.632253Z  INFO komorebi: creating window manager from static configuration file: C:\Users\snize\komorebi.json
Error:
   0: ソケット操作によりネットワークの停止が検出されました。 (os error 10050)

Location:
   komorebi\src\static_config.rs:770

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   1: BaseThreadInitThunk<unknown>
      at <unknown source file>:<unknown line>
   2: RtlUserThreadStart<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.

Operating System

OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22631 N/A Build 22631

komorebic check Output

PS C:\Users\snize> komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\snize

Looking for configuration files in C:\Users\snize

Found komorebi.json; this file can be passed to the start command with the --config flag

Found C:\Users\snize\.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
I tried to start komorebi after rebooting the PC and without doing any other work, but the situation did not change and it did not start. I can't think of any other possible causes.

Originally created by @snize on GitHub (Feb 16, 2024). **Describe the bug** I am setting up according to the Getting started in the documentation, but I am failing to start komorebi. **To Reproduce** Steps to reproduce the behavior: 1. Enabled long path support. 2. Installed komorebi and whkd with winget. 3. Download configuration files with `komorebic quickstart` 4. Then start komorebi with `komorebic start --whkd` 5. See bug **Expected behavior** I might be overlooking something, but I am proceeding as per the documentation and expect komorebi to start. **Screenshots and Videos** ``` PowerShell 7.4.1 PS C:\Users\snize> komorebic start --whkd Start-Process 'komorebi.exe' -WindowStyle hidden Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again Start-Process 'komorebi.exe' -WindowStyle hidden Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again Start-Process 'komorebi.exe' -WindowStyle hidden ``` I tried to call the binary directly to check the cause of the stop, referring to https://github.com/LGUG2Z/komorebi/discussions/499#discussioncomment-6489907. ``` PS C:\Users\snize> komorebi -c "$Env:USERPROFILE\komorebi.json" 2024-02-16T13:15:08.628937Z INFO foreground_lock_timeout: komorebi::windows_api: current value of ForegroundLockTimeout is 0 2024-02-16T13:15:08.632253Z INFO komorebi: creating window manager from static configuration file: C:\Users\snize\komorebi.json Error: 0: ソケット操作によりネットワークの停止が検出されました。 (os error 10050) Location: komorebi\src\static_config.rs:770 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1: BaseThreadInitThunk<unknown> at <unknown source file>:<unknown line> 2: RtlUserThreadStart<unknown> at <unknown source file>:<unknown line> Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering. Run with RUST_BACKTRACE=full to include source snippets. ``` **Operating System** ``` OS Name: Microsoft Windows 11 Pro OS Version: 10.0.22631 N/A Build 22631 ``` **`komorebic check` Output** ``` PS C:\Users\snize> komorebic check No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\snize Looking for configuration files in C:\Users\snize Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\snize\.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** I tried to start komorebi after rebooting the PC and without doing any other work, but the situation did not change and it did not start. I can't think of any other possible causes.

adam added the bug label 2026-01-05 14:49:33 +01:00

adam closed this issue

2026-01-05 14:49:33 +01:00

adam commented

2026-01-05 14:49:34 +01:00

@LGUG2Z commented on GitHub (Feb 16, 2024):

I believe there may have been a change in behaviour in newer Windows versions where folders inside of ~\AppData\Local do not get automatically created.

Can you try running mkdir "$Env:LOCALAPPDATA\komorebi" -ea 0 to ensure that folder is created first, and then try starting again? 🙏

@LGUG2Z commented on GitHub (Feb 16, 2024): I believe there may have been a change in behaviour in newer Windows versions where folders inside of `~\AppData\Local` do not get automatically created. Can you try running `mkdir "$Env:LOCALAPPDATA\komorebi" -ea 0` to ensure that folder is created first, and then try starting again? 🙏

adam commented

2026-01-05 14:49:34 +01:00

@LGUG2Z commented on GitHub (Feb 16, 2024):

I have confirmed with another user that this does fix the issue reported here, so I've updated the docs for now: https://lgug2z.github.io/komorebi/installation.html#local-data-directory

Will keep this issue open until I push a commit ensuring that this directory is created by the komorebic quickstart command in the future.

@LGUG2Z commented on GitHub (Feb 16, 2024): I have confirmed with another user that this does fix the issue reported here, so I've updated the docs for now: https://lgug2z.github.io/komorebi/installation.html#local-data-directory Will keep this issue open until I push a commit ensuring that this directory is created by the `komorebic quickstart` command in the future.

adam commented

2026-01-05 14:49:34 +01:00

@snize commented on GitHub (Feb 17, 2024):

The issue has been resolved. Thank you for your quick response and assistance!

@snize commented on GitHub (Feb 17, 2024): The issue has been resolved. Thank you for your quick response and assistance!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#297