[BUG]: Komorebi will not start with a custom applications.yaml #440

New Issue

2026-01-05T14:50:45+01:00

adam commented

2026-01-05 14:50:45 +01:00

Originally created by @hexxdgrl on GitHub (Aug 2, 2024).

I was trying to define a badly behaving app (AIMP) in applications.yaml and when komorebi is restarted it throws the following message:

`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
Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again

Running komorebi.exe directly for detailed error output

Error:
0: ←[91m.[10].identifier: invalid type: sequence, expected struct IdWithIdentifier at line 92 column 3←[0m

Location:
←[35mkomorebi-core\src\config_generation.rs←[0m:←[35m132←[0m

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1: ←[32mBaseThreadInitThunk←[0m←[90m←[0m
at ←[35m←[0m:←[35m←[0m
2: ←[91mRtlUserThreadStart←[0m←[90m←[0m
at ←[35m←[0m:←[35m←[0m

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

when the applicition rules are removed from applications.yaml, it starts just fine. am i doing something incorrectly to add rules?

Originally created by @hexxdgrl on GitHub (Aug 2, 2024). I was trying to define a badly behaving app (AIMP) in applications.yaml and when komorebi is restarted it throws the following message: `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 Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again Running komorebi.exe directly for detailed error output Error: 0: ←[91m.[10].identifier: invalid type: sequence, expected struct IdWithIdentifier at line 92 column 3←[0m Location: ←[35mkomorebi-core\src\config_generation.rs←[0m:←[35m132←[0m ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1: ←[32mBaseThreadInitThunk←[0m←[90m<unknown>←[0m at ←[35m<unknown source file>←[0m:←[35m<unknown line>←[0m 2: ←[91mRtlUserThreadStart←[0m←[90m<unknown>←[0m at ←[35m<unknown source file>←[0m:←[35m<unknown line>←[0m Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering. Run with RUST_BACKTRACE=full to include source snippets.` when the applicition rules are removed from applications.yaml, it starts just fine. am i doing something incorrectly to add rules?

adam added the bug label 2026-01-05 14:50:45 +01:00

adam closed this issue

2026-01-05 14:50:46 +01:00

adam commented

2026-01-05 14:50:46 +01:00

@LGUG2Z commented on GitHub (Aug 2, 2024):

It's hard to say without seeing exactly what you're trying to add; from the error you posted it looks like what you added isn't matching the expected schema.

Generally it's suggested that users make individual changes to komorebi.json first (to ignore, force manage etc.), get a feeling for whether these changes make sense to be defaults, and then submit a PR with changes to applications.yaml to the asc repo, especially because whatever changes individuals make to applications.yaml locally will be clobbered when they update the file with komorebic fetch-asc.

@LGUG2Z commented on GitHub (Aug 2, 2024): It's hard to say without seeing exactly what you're trying to add; from the error you posted it looks like what you added isn't matching the expected schema. Generally it's suggested that users make individual changes to `komorebi.json` first (to [ignore](https://lgug2z.github.io/komorebi/common-workflows/ignore-windows.html), [force manage](https://lgug2z.github.io/komorebi/common-workflows/force-manage-windows.html) etc.), get a feeling for whether these changes make sense to be defaults, and then submit a PR with changes to `applications.yaml` to [the asc repo](https://github.com/LGUG2Z/komorebi-application-specific-configuration), especially because whatever changes individuals make to `applications.yaml` locally will be clobbered when they update the file with `komorebic fetch-asc`.

adam commented

2026-01-05 14:50:46 +01:00