What am I doing wrong when setting display_index_preferences? komorebi.exe will hang if I give a specific monitor a new id.

[llinfeng]

I have the following monitor setup, but will get stuck with running komorebi.exe alone if I assign monitor 2 to have a unique index in display_index_preferences.

Specifically, giving the last monitor index 4 as below will leave komorebi.exe to hang with some 25% CPU usage, and it will hang there indefinitely.

  "display_index_preferences": {
    "0": "DELA0B9-5&65461ac&1&UID8450",
    "1": "DELA0B9-5&65461ac&1&UID8448",
    "2": "DELA0B8-5&3a594c6b&0&UID4353",
    "3": "AUS14DA-5&3a594c6b&0&UID4355",
    "0": "LEN62A2-5&3a594c6b&0&UID4352",
    "4": "AUS2487-5&3a594c6b&0&UID4358",
  }

Here is the console output when running komorebi.exe alone.

2024-07-08T01:25:41.860355Z  INFO foreground_lock_timeout: komorebi::windows_api: current value of ForegroundLockTimeout is 0
2024-07-08T01:25:41.862966Z  INFO komorebi: creating window manager from static configuration file: C:\Users\llinfeng\komorebi.json
2024-07-08T01:25:41.868237Z  INFO init: komorebi::window_manager: initialising

---

Alternatively, reusing some existing indexes like below will get the komorebic start to run just fine.

  "display_index_preferences": {
    "0": "DELA0B9-5&65461ac&1&UID8450",
    "1": "DELA0B9-5&65461ac&1&UID8448",
    "2": "DELA0B8-5&3a594c6b&0&UID4353",
    "3": "AUS14DA-5&3a594c6b&0&UID4355",
    "0": "LEN62A2-5&3a594c6b&0&UID4352",
    "1": "AUS2487-5&3a594c6b&0&UID4358",
  }

Side note: I need to assign index "0" again for monitor "LEN62A2-5&3a594c6b&0&UID4352" (monitor 3) to get its custom_layout configuration to work. I could have given it index "4" and komoreb will launch just fine. Though, in this case, none of the monitors would load that custom_layout.

My full komorebi.json config

{
    "$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.25/schema.json",
    "app_specific_configuration_path": "$Env:USERPROFILE/applications.yaml",
    "mouse_follows_focus": false,
    "window_hiding_behaviour": "Cloak",
    "cross_monitor_move_behaviour": "Insert",
    "default_workspace_padding": 0,
    "default_container_padding": 0,
    "border": true,
    "border_width": 3,
    "border_offset": -1,
    "border_colours": {
        "single": "#42a5f5",
        "stack": "#00a542",
        "monocle": "#ff3399",
        "unfocused": "#808080"
    },
    "stackbar": {
        "height": 40,
        "mode": "OnStack",
        "tabs": {
            "width": 300,
            "focused_text": "#00a542",
            "unfocused_text": "#b3b3b3",
            "background": "#141414"
        }
    },
    "monitors": [
        {  // index=0
            "workspaces": [
                { "name": "LEN62A2-5&3a594c6b&0&UID4352",  "custom_layout": "c:/users/username/UltraWide_custom.json"}
            ]
        },
        {  // index=1
            "workspaces": [
                { "name": "Monitor3-workspace1", "layout": "HorizontalStack" }
            ]
        },
        {  // index=2
            "workspaces": [
                { "name": "Monitor4-workspace1", "layout": "HorizontalStack" }
            ]
        },
        {  // index=3
            "workspaces": [
                { "name": "AUS2487-5&3a594c6b&0&UID4358", "layout": "VerticalStack" }
            ]
        },
        { // index=4
            "workspaces": [
                { "name": "Monitor2-workspace1", "layout": "HorizontalStack" }
            ]
        },
        { // index=5
            "workspaces": [
                { "name": "Monitor1-workspace1", "layout": "HorizontalStack" }
            ]
        }
    ],
  "display_index_preferences": {
    "0": "DELA0B9-5&65461ac&1&UID8450",
    "1": "DELA0B9-5&65461ac&1&UID8448",
    "2": "DELA0B8-5&3a594c6b&0&UID4353",
    "3": "AUS14DA-5&3a594c6b&0&UID4355",
    "0": "LEN62A2-5&3a594c6b&0&UID4352",
    "1": "AUS2487-5&3a594c6b&0&UID4358",
  }
}

And, what goes in UltraWide_custom.json:

[
  {
    "column": "Secondary",
    "configuration": {
      "Horizontal": 2
    }
  },
  {
    "column": "Primary",
    "configuration": {
        "WidthPercentage": 50
    }
  },
  {
    "column": "Tertiary",
    "configuration": "Horizontal"
  }
]

[LGUG2Z]

Each key in display_index_preferences should refer to a unique index which corresponds to an index in the monitors array.

Side note: I need to assign index "0" again for monitor "LEN62A2-5&3a594c6b&0&UID4352" (monitor 3) to get its custom_layout configuration to work.

You should duplicate the configuration block for workspaces on that monitor instead of trying to refer to the same index.

[llinfeng]

[edited] I spotted a buggy monitor and was able to launch komorebi properly after giving it index 0. Not sure why this helped. With this "fixed", the custom lay is applied properly as well. Thank you!

[llinfeng]

In my case, komorebi.exe gets stuck in "initialising" state should I assign a specific monitor a large (>=3) index. For example, here is what I see in Task Manager with the following config:

  "display_index_preferences": {
    "0": "DELA0B9-5&65461ac&1&UID8450",
    "1": "DELA0B9-5&65461ac&1&UID8448",
    "2": "DELA0B8-5&3a594c6b&0&UID4353",
    "3": "AUS14DA-5&3a594c6b&0&UID4355",
    "0": "LEN62A2-5&3a594c6b&0&UID4352",
    "4": "AUS2487-5&3a594c6b&0&UID4358",
  }

---

Solution: assigning index "0" to the problematic monitor will solve the launch problem. In my case, AUS2487-5&3a594c6b&0&UID4358 is the buggy monitor.

    "0": "AUS2487-5&3a594c6b&0&UID4358",
    "1": "DELA0B9-5&65461ac&1&UID8450",
    "1": "DELA0B9-5&65461ac&1&UID8448",
    "2": "DELA0B8-5&3a594c6b&0&UID4353",
    "3": "AUS14DA-5&3a594c6b&0&UID4355",
    "4": "LEN62A2-5&3a594c6b&0&UID4352",

---

PS: All monitors are connected to graphic cards. Two cards were used to power the 6 monitors.