[BUG]: WSL window (wezterm) not managed #631

Closed
opened 2026-01-05 14:52:06 +01:00 by adam · 1 comment
Owner

Originally created by @rwijtvliet on GitHub (May 27, 2025).

Summary

I'm probably doing something wrong, otherwise I wouldn't be the first to report this :)

When I start Wezterm, which is installed on WSL (ubuntu), its window is not managed by komorebi. Stopping and starting komorebi (as suggested here) does not help.

Image

Image

Version Information

OS Name: Microsoft Windows 11 Enterprise
OS Version: 10.0.26100 N/A Build 26100
komorebic 0.1.37
tag:v0.1.37
commit_hash:00384ce3
build_time:2025-05-17 19:16:53 +00:00
build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc

Komorebi Configuration

My config is here

Hotkey Configuration

Here

Output of komorebic check

PS C:\Users\me> komorebic check
KOMOREBI_CONFIG_HOME detected: C:\Users\me.dotfiles\windowmanager\windows

Looking for configuration files in C:\Users\me.dotfiles\windowmanager\windows

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

No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard

Originally created by @rwijtvliet on GitHub (May 27, 2025). ### Summary I'm probably doing something wrong, otherwise I wouldn't be the first to report this :) When I start Wezterm, which is installed on WSL (ubuntu), its window is not managed by komorebi. Stopping and starting komorebi (as suggested [here](https://github.com/LGUG2Z/komorebi/issues/1054)) does not help. ![Image](https://github.com/user-attachments/assets/78b64684-809e-4494-b0c5-4cdf2c9fae1d) ![Image](https://github.com/user-attachments/assets/3c8837f4-c70d-4fbd-ba25-398bb4f33adc) ### Version Information OS Name: Microsoft Windows 11 Enterprise OS Version: 10.0.26100 N/A Build 26100 komorebic 0.1.37 tag:v0.1.37 commit_hash:00384ce3 build_time:2025-05-17 19:16:53 +00:00 build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc ### Komorebi Configuration My config is [here](https://github.com/rwijtvliet/dotfiles/blob/main/windowmanager/windows/komorebi.json) ### Hotkey Configuration [Here](https://github.com/rwijtvliet/dotfiles/blob/main/windowmanager/windows/hotkeys.ahk) ### Output of komorebic check PS C:\Users\me> komorebic check KOMOREBI_CONFIG_HOME detected: C:\Users\me\.dotfiles\windowmanager\windows Looking for configuration files in C:\Users\me\.dotfiles\windowmanager\windows Found komorebi.json; this file can be passed to the start command with the --config flag No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard
adam added the bug label 2026-01-05 14:52:06 +01:00
adam closed this issue 2026-01-05 14:52:06 +01:00
Author
Owner

@LGUG2Z commented on GitHub (May 27, 2025):

It's not you, it's Microsoft 🙂 There are already a few open issues in the WSLg repo about this - WSLg apps do not respond correctly to Win32 positioning API calls - this is unfortunately another issue that can only be solved by the Trillion Dollar Company ™️.

I suggest disabling WSLg and using VcXsrV to render Linux GUI apps in Windows instead.

@LGUG2Z commented on GitHub (May 27, 2025): It's not you, it's Microsoft 🙂 There are already a few open issues in the WSLg repo about this - WSLg apps do not respond correctly to Win32 positioning API calls - this is unfortunately another issue that can only be solved by the Trillion Dollar Company ™️. I suggest disabling WSLg and using VcXsrV to render Linux GUI apps in Windows instead.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#631