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]: Inconsistent multi-monitor behaviors #490

New Issue
Closed
opened 2026-01-05 14:51:04 +01:00 by adam · 5 comments
adam commented 2026-01-05 14:51:04 +01:00
Owner
Copy Link

Originally created by @whaaaley on GitHub (Oct 14, 2024).

Summary

I'm unable to focus or move windows after I reconfigured my monitor setup over the weekend. Previously everything was perfect, but I had a weird configuration for my extra monitors, using a mix of onboard and dedicated ports. Over the weekend I moved everything to dedicated by plugging my two bottom monitors into a hub.

Now I can't move or focus windows in monitor 4. Moving windows or focusing down only goes to 3. Is there something I need to do? I'm wondering if they're getting reported as a single monitor to Komorebi due to the hub, rather than individual.

image

Version Information

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

komorebic 0.1.29
tag:v0.1.29
commit_hash:818ac340
build_time:2024-09-28 01:48:31 +00:00
build_env:rustc 1.81.0 (eeb90cda1 2024-09-04),stable-x86_64-pc-windows-msvc

Komorebi Configuration

{
  "$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.29/schema.json",
  "app_specific_configuration_path": "$Env:USERPROFILE/applications.yaml",
  "window_hiding_behaviour": "Cloak",
  "cross_monitor_move_behaviour": "Insert",
  "mouse_follows_focus": false,
  "default_workspace_padding": 36,
  "default_container_padding": 12,
  "border": true,
  "border_width": 2,
  "border_offset": 0,
  "border_style": "Square",
  "border_colours": {
    "single": {
      "r": 255,
      "g": 168,
      "b": 60,
      "a": 0
    },
    "stack": {
      "r": 255,
      "g": 168,
      "b": 60,
      "a": 0
    },
    "monocle": {
      "r": 255,
      "g": 168,
      "b": 60,
      "a": 0
    },
    "unfocused": {
      "r": 0,
      "g": 0,
      "b": 0,
      "a": 255
    }
  },
  "stackbar": {
    "height": 40,
    "mode": "OnStack",
    "tabs": {
      "width": 300
    }
  },
  "display_index_preferences": {
    "0": "SAM0E14-5&1796117&0&UID4355",
    "1": "SAM0E14-5&1796117&0&UID4357",
    "2": "HHS1400-5&1796117&0&UID4650",
    "3": "HHS1400-5&1796117&0&UID4651"
  },
  "monitors": [
    {
      "workspaces": [
        {
          "name": "I",
          "layout": "VerticalStack"
        }
      ]
    }
  ]
}

Hotkey Configuration

Default

Output of komorebic check

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

Looking for configuration files in C:\Users\dustin

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

Found C:\Users\dustin\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag

Output of komorebic monitor-information

{
  "HHS1400-5&1796117&0&UID4650": {
    "left": 640,
    "top": 1440,
    "right": 1920,
    "bottom": 1200
  },
  "HHS1400-5&1796117&0&UID4651": {
    "left": 2560,
    "top": 1440,
    "right": 1920,
    "bottom": 1200
  },
  "SAM0E14-5&1796117&0&UID4355": {
    "left": 0,
    "top": 0,
    "right": 2560,
    "bottom": 1440
  },
  "SAM0E14-5&1796117&0&UID4357": {
    "left": 2560,
    "top": 0,
    "right": 2560,
    "bottom": 1440
  }
}
Originally created by @whaaaley on GitHub (Oct 14, 2024). ### Summary I'm unable to focus or move windows after I reconfigured my monitor setup over the weekend. Previously everything was perfect, but I had a weird configuration for my extra monitors, using a mix of onboard and dedicated ports. Over the weekend I moved everything to dedicated by plugging my two bottom monitors into a hub. Now I can't move or focus windows in monitor 4. Moving windows or focusing down only goes to 3. Is there something I need to do? I'm wondering if they're getting reported as a single monitor to Komorebi due to the hub, rather than individual. ![image](https://github.com/user-attachments/assets/d817efb3-0d06-4264-b13c-3ae676d200c3) ### Version Information ``` OS Name: Microsoft Windows 11 Pro OS Version: 10.0.22631 N/A Build 22631 ``` ``` komorebic 0.1.29 tag:v0.1.29 commit_hash:818ac340 build_time:2024-09-28 01:48:31 +00:00 build_env:rustc 1.81.0 (eeb90cda1 2024-09-04),stable-x86_64-pc-windows-msvc ``` ### Komorebi Configuration ```json { "$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.29/schema.json", "app_specific_configuration_path": "$Env:USERPROFILE/applications.yaml", "window_hiding_behaviour": "Cloak", "cross_monitor_move_behaviour": "Insert", "mouse_follows_focus": false, "default_workspace_padding": 36, "default_container_padding": 12, "border": true, "border_width": 2, "border_offset": 0, "border_style": "Square", "border_colours": { "single": { "r": 255, "g": 168, "b": 60, "a": 0 }, "stack": { "r": 255, "g": 168, "b": 60, "a": 0 }, "monocle": { "r": 255, "g": 168, "b": 60, "a": 0 }, "unfocused": { "r": 0, "g": 0, "b": 0, "a": 255 } }, "stackbar": { "height": 40, "mode": "OnStack", "tabs": { "width": 300 } }, "display_index_preferences": { "0": "SAM0E14-5&1796117&0&UID4355", "1": "SAM0E14-5&1796117&0&UID4357", "2": "HHS1400-5&1796117&0&UID4650", "3": "HHS1400-5&1796117&0&UID4651" }, "monitors": [ { "workspaces": [ { "name": "I", "layout": "VerticalStack" } ] } ] } ``` ### Hotkey Configuration Default ### Output of `komorebic check` ``` PS C:\Users\dustin> komorebic check No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\dustin Looking for configuration files in C:\Users\dustin Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\dustin\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag ``` ### Output of `komorebic monitor-information` ``` { "HHS1400-5&1796117&0&UID4650": { "left": 640, "top": 1440, "right": 1920, "bottom": 1200 }, "HHS1400-5&1796117&0&UID4651": { "left": 2560, "top": 1440, "right": 1920, "bottom": 1200 }, "SAM0E14-5&1796117&0&UID4355": { "left": 0, "top": 0, "right": 2560, "bottom": 1440 }, "SAM0E14-5&1796117&0&UID4357": { "left": 2560, "top": 0, "right": 2560, "bottom": 1440 } } ```
adam added the bug label 2026-01-05 14:51:04 +01:00
adam closed this issue 2026-01-05 14:51:04 +01:00
adam commented 2026-01-05 14:51:05 +01:00
Author
Owner
Copy Link

@whaaaley commented on GitHub (Oct 14, 2024):

I actually think this is the same issue as https://github.com/LGUG2Z/komorebi/issues/447, but in my configuration it prevents me touching monitor 4. I must have had an inconsistent layout in my previous configuration that allowed it to work due to imperfect coordinates.

@whaaaley commented on GitHub (Oct 14, 2024): I actually think this is the same issue as https://github.com/LGUG2Z/komorebi/issues/447, but in my configuration it prevents me touching monitor 4. I must have had an inconsistent layout in my previous configuration that allowed it to work due to imperfect coordinates.
adam commented 2026-01-05 14:51:05 +01:00
Author
Owner
Copy Link

@whaaaley commented on GitHub (Oct 16, 2024):

Shifting the bottom two monitors slightly to the right allows me to get access to monitor 4, although there's oddities.

[works] Left <---> right, between 1 and 2
[works] Left <---> right, between 3 and 4
[works] Top <---> bottom, between 1 and 3
[not working] Top ---> bottom, from 2 to 4, goes to 3 instead of 4
[not working] Bottom ---> Top, from 4 to 2, goes to 1 instead of 2

image

{
  "HHS1400-5&1796117&0&UID4650": {
    "left": 716,
    "top": 1440,
    "right": 1920,
    "bottom": 1200
  },
  "SAM0E14-5&1796117&0&UID4357": {
    "left": 2560,
    "top": 0,
    "right": 2560,
    "bottom": 1440
  },
  "HHS1400-5&1796117&0&UID4651": {
    "left": 2636,
    "top": 1440,
    "right": 1920,
    "bottom": 1200
  },
  "SAM0E14-5&1796117&0&UID4355": {
    "left": 0,
    "top": 0,
    "right": 2560,
    "bottom": 1440
  }
}

The behavior of going down from monitor 2 to 3, instead of 4, is still present even in the most drastic of scenarios:

image

@whaaaley commented on GitHub (Oct 16, 2024): Shifting the bottom two monitors slightly to the right allows me to get access to monitor 4, although there's oddities. [works] Left <---> right, between 1 and 2 [works] Left <---> right, between 3 and 4 [works] Top <---> bottom, between 1 and 3 [not working] Top ---> bottom, from 2 to 4, goes to 3 instead of 4 [not working] Bottom ---> Top, from 4 to 2, goes to 1 instead of 2 ![image](https://github.com/user-attachments/assets/e07b27f6-29ef-402b-8c0f-5130337e091a) ``` { "HHS1400-5&1796117&0&UID4650": { "left": 716, "top": 1440, "right": 1920, "bottom": 1200 }, "SAM0E14-5&1796117&0&UID4357": { "left": 2560, "top": 0, "right": 2560, "bottom": 1440 }, "HHS1400-5&1796117&0&UID4651": { "left": 2636, "top": 1440, "right": 1920, "bottom": 1200 }, "SAM0E14-5&1796117&0&UID4355": { "left": 0, "top": 0, "right": 2560, "bottom": 1440 } } ``` --- The behavior of going down from monitor 2 to 3, instead of 4, is still present even in the most drastic of scenarios: ![image](https://github.com/user-attachments/assets/e4fd26dd-d887-473d-9dff-76744f4c2160)
adam commented 2026-01-05 14:51:05 +01:00
Author
Owner
Copy Link

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

c0c3c81d69/komorebi/src/window_manager.rs (L465-L496)

This is the logic that needs to be updated ^

@LGUG2Z commented on GitHub (Oct 16, 2024): https://github.com/LGUG2Z/komorebi/blob/c0c3c81d69d43c4db3e3d26e674bffbfde8504e8/komorebi/src/window_manager.rs#L465-L496 This is the logic that needs to be updated ^
adam commented 2026-01-05 14:51:05 +01:00
Author
Owner
Copy Link

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

I don't have enough monitors to try this out but you can test this commit: e8e18a48ad

@LGUG2Z commented on GitHub (Oct 16, 2024): I don't have enough monitors to try this out but you can test this commit: https://github.com/LGUG2Z/komorebi/commit/e8e18a48ada1a76c68295ba5b25d63cc899d6a3c
adam commented 2026-01-05 14:51:05 +01:00
Author
Owner
Copy Link

@alex-ds13 commented on GitHub (Dec 26, 2024):

@whaaaley Can you check if this is still an issue on the latest releases?

@alex-ds13 commented on GitHub (Dec 26, 2024): @whaaaley Can you check if this is still an issue on the latest releases?
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#490
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?