[BUG]: Komorebi Bar cut in half #478

New Issue

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

adam commented

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

Originally created by @eqbirvin on GitHub (Oct 2, 2024).

Upon installing and loading more recent release (0.129) that include the Komorebi Bar, the bar itself is cut in half, only displaying the top side of the bar and leaving space for the desktop to show through.

To Reproduce
Start Komorebi via: 'komorebic start --whkd --bar' with default settings
Observe status bar being cut in half

Expected behavior
Upon stating komorebi, it should by default display the full status bar with no artifacts.

Screenshots and Videos

Operating System
Microsoft Windows 11 Home
10.0.22631 Build 22631

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

Looking for configuration files in C:\Users\ebish

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

Found C:\Users\ebish.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 have tried playing with font size and frame settings but when I try to input the frame settings, the bar just never shows after stopping and restarting komorebi.

Originally created by @eqbirvin on GitHub (Oct 2, 2024). Upon installing and loading more recent release (0.129) that include the Komorebi Bar, the bar itself is cut in half, only displaying the top side of the bar and leaving space for the desktop to show through. **To Reproduce** Start Komorebi via: 'komorebic start --whkd --bar' with default settings Observe status bar being cut in half **Expected behavior** Upon stating komorebi, it should by default display the full status bar with no artifacts. **Screenshots and Videos** ![image](https://github.com/user-attachments/assets/0f12dcd9-6e24-4477-ade0-397d32feddc9) ![image](https://github.com/user-attachments/assets/d121b70a-00f6-4a29-b548-4b8723051825) **Operating System** Microsoft Windows 11 Home 10.0.22631 Build 22631 **`komorebic check` Output** PS C:\Users\ebish> komorebic check No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\ebish Looking for configuration files in C:\Users\ebish Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\ebish\.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 have tried playing with font size and frame settings but when I try to input the frame settings, the bar just never shows after stopping and restarting komorebi.

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

adam closed this issue

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

adam commented

2026-01-05 14:51:00 +01:00

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

The desired size of the bar from the starting position (usually monitor width x desired height)

This is the setting you'll want to play with to get things working for your particular setup.

https://komorebi-bar.lgug2z.com/schema#viewport_inner_size

@LGUG2Z commented on GitHub (Oct 2, 2024): ``` The desired size of the bar from the starting position (usually monitor width x desired height) ``` This is the setting you'll want to play with to get things working for your particular setup. https://komorebi-bar.lgug2z.com/schema#viewport_inner_size

adam commented

2026-01-05 14:51:00 +01:00

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

I would be curious to know some key information that was left out of your bug report:

What is your screen resolution?
What scaling factor do you have set on your device?
What is the physical size of your display device?

@LGUG2Z commented on GitHub (Oct 2, 2024): I would be curious to know some key information that was left out of your bug report: * What is your screen resolution? * What scaling factor do you have set on your device? * What is the physical size of your display device?

adam commented

2026-01-05 14:51:00 +01:00

@eqbirvin commented on GitHub (Oct 2, 2024):

Thank you so much! I hate to be a bother but what is that section supposed to look like when adding it to the config file? Do you have a sample? I tried it myself with no luck, the bar just doesn't start since I have something wrong.

Resolution on display is: 2560 x 1600
Scale is: 125%
16inch (Asus Zephyrus g16 2024 - oled model)

@eqbirvin commented on GitHub (Oct 2, 2024): Thank you so much! I hate to be a bother but what is that section supposed to look like when adding it to the config file? Do you have a sample? I tried it myself with no luck, the bar just doesn't start since I have something wrong. Resolution on display is: 2560 x 1600 Scale is: 125% 16inch (Asus Zephyrus g16 2024 - oled model)

adam commented

2026-01-05 14:51:00 +01:00

@WaldoJoubert-GH commented on GitHub (Oct 2, 2024):

I have the same issue:
Resolution: 1920x1080
Scale: 100%
Refresh rate: 165Hz
24" AOC

@WaldoJoubert-GH commented on GitHub (Oct 2, 2024): I have the same issue: Resolution: 1920x1080 Scale: 100% Refresh rate: 165Hz 24" AOC ![image](https://github.com/user-attachments/assets/7aede533-0059-41dc-a0e9-60d86ae0c855)

adam commented

2026-01-05 14:51:00 +01:00

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

  "viewport": {
    "inner_size": {
      // for example, my resolution is 5120x2160 scaled to 125%
      // and I want the bar to take up the full width of the screen so
      // I set x to 5120
      "x": 5120,
      
      // 20 is the default value for the height; if you want to increase the height you can try
      // doubling the y value as a starting point and then iterating from there
      "y": 20,
    }
  }

@LGUG2Z commented on GitHub (Oct 2, 2024): ```jsonc "viewport": { "inner_size": { // for example, my resolution is 5120x2160 scaled to 125% // and I want the bar to take up the full width of the screen so // I set x to 5120 "x": 5120, // 20 is the default value for the height; if you want to increase the height you can try // doubling the y value as a starting point and then iterating from there "y": 20, } } ```

adam commented

2026-01-05 14:51:00 +01:00

@eqbirvin commented on GitHub (Oct 2, 2024):

Thank you, @LGUG2Z! That worked! Now I just need to fiddle with monitors

@eqbirvin commented on GitHub (Oct 2, 2024): Thank you, @LGUG2Z! That worked! Now I just need to fiddle with monitors

adam commented

2026-01-05 14:51:01 +01:00

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

https://github.com/LGUG2Z/komorebi/commit/20f370a51d110c7820319d8c2968ca863c61219b

This should help with these sorts of DPI issues, it will be in the next Nightly

@LGUG2Z commented on GitHub (Oct 5, 2024): https://github.com/LGUG2Z/komorebi/commit/20f370a51d110c7820319d8c2968ca863c61219b This should help with these sorts of DPI issues, it will be in the next Nightly

adam referenced this issue

2026-01-05 14:53:30 +01:00

[PR #478] [MERGED] chore(deps): bump quote from 1.0.28 to 1.0.29 #944

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#478