Originally created by @tardyp on GitHub (Sep 27, 2024).
**Describe the bug**
I recently upgraded my wsl setup. Since that. komorebi started loosing track of certain window.
There is always the error message:
```
komorebi::process_event: The system could not find the environment option that was entered. (os error 203)
```
If I restart komorebi, the error disapear (so I don't think this is related to actual metadata of the window)
Then it reappears randomly after about 2 hours of normal work.
**Operating System**
```
OS Name: Microsoft Windows 11 Entreprise
OS Version: 10.0.22631 N/A Build 22631
```
**`komorebic check` Output**
no error in komorebi check
**Additional context**
I updated komorebi last week, well before the problem started happening.
```
$ komorebi --version
komorebi 0.1.28
tag:v0.1.28
commit_hash:0cdce8fc
build_time:2024-07-15 16:06:31 +00:00
build_env:rustc 1.79.0 (129f3b996 2024-06-10),stable-x86_64-pc-windows-msvc
```
adam
added the bug label 2026-01-05 14:50:57 +01:00
Related issue might be this bug:
I indeed have zscaler installed on that PC, that may be messing up with my proxy settings, and WSL might be indeed wanting to magically forward the proxy configuration. https://github.com/microsoft/WSL/issues/11523
But I am not sure how this could impact komorebi.
So a repro might be:
launch a wsl terminal
change the system proxy settings
start a new wsl terminal.
I cannot change manually my proxy settings on my corporate laptop, so I cannot really test this repro.
@tardyp commented on GitHub (Sep 27, 2024):
Related issue might be this bug:
I indeed have zscaler installed on that PC, that may be messing up with my proxy settings, and WSL might be indeed wanting to magically forward the proxy configuration.
https://github.com/microsoft/WSL/issues/11523
But I am not sure how this could impact komorebi.
So a repro might be:
- launch a wsl terminal
- change the system proxy settings
- start a new wsl terminal.
I cannot change manually my proxy settings on my corporate laptop, so I cannot really test this repro.
after recompiling with debug_assertion config I get a stack trace
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⋮ 10 frames hidden ⋮
11: core::convert::impl$3::into<std::io::error::Error,eyre::Report><unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\convert\mod.rs:759
12: komorebi::windows_api::impl$7::from<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:169
13: komorebi::windows_api::WindowsApi::window_text_w<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:746
14: komorebi::window::Window::title<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window.rs:379
15: komorebi::window_manager::WindowManager::enforce_workspace_rules<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window_manager.rs:462
16: komorebi::window_manager::WindowManager::process_event<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:160
17: komorebi::process_event::listen_for_events::closure$0<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:49
18: core::hint::black_box<unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\hint.rs:338
⋮ 14 frames hidden ⋮
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
Warning: SpanTrace capture is Unsupported.
Ensure that you've setup a tracing-error ErrorLayer and the semver versions are compatible
2024-09-30T11:06:49.070688Z ERROR komorebi::process_event:
0: The operation completed successfully. (os error 0)
Location:
komorebi\src\windows_api.rs:178
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⋮ 10 frames hidden ⋮
11: core::convert::impl$3::into<std::io::error::Error,eyre::Report><unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\convert\mod.rs:759
12: komorebi::windows_api::impl$7::from<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:169
13: komorebi::windows_api::WindowsApi::window_text_w<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:746
14: komorebi::window::Window::title<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window.rs:379
15: komorebi::window_manager::WindowManager::enforce_workspace_rules<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window_manager.rs:462
16: komorebi::window_manager::WindowManager::process_event<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:160
17: komorebi::process_event::listen_for_events::closure$0<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:49
18: core::hint::black_box<unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\hint.rs:338
⋮ 14 frames hidden ⋮
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
Warning: SpanTrace capture is Unsupported.
Ensure that you've setup a tracing-error ErrorLayer and the semver versions are compatible
2024-09-30T11:06:51.572608Z ERROR komorebi::process_event:
0: The system could not find the environment option that was entered. (os error 203)
Location:
komorebi\src\windows_api.rs:178
@tardyp commented on GitHub (Sep 30, 2024):
after recompiling with debug_assertion config I get a stack trace
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⋮ 10 frames hidden ⋮
11: core::convert::impl$3::into<std::io::error::Error,eyre::Report><unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\convert\mod.rs:759
12: komorebi::windows_api::impl$7::from<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:169
13: komorebi::windows_api::WindowsApi::window_text_w<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:746
14: komorebi::window::Window::title<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window.rs:379
15: komorebi::window_manager::WindowManager::enforce_workspace_rules<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window_manager.rs:462
16: komorebi::window_manager::WindowManager::process_event<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:160
17: komorebi::process_event::listen_for_events::closure$0<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:49
18: core::hint::black_box<unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\hint.rs:338
⋮ 14 frames hidden ⋮
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
Warning: SpanTrace capture is Unsupported.
Ensure that you've setup a tracing-error ErrorLayer and the semver versions are compatible
2024-09-30T11:06:49.070688Z ERROR komorebi::process_event:
0: The operation completed successfully. (os error 0)
Location:
komorebi\src\windows_api.rs:178
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⋮ 10 frames hidden ⋮
11: core::convert::impl$3::into<std::io::error::Error,eyre::Report><unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\convert\mod.rs:759
12: komorebi::windows_api::impl$7::from<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:169
13: komorebi::windows_api::WindowsApi::window_text_w<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\windows_api.rs:746
14: komorebi::window::Window::title<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window.rs:379
15: komorebi::window_manager::WindowManager::enforce_workspace_rules<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\window_manager.rs:462
16: komorebi::window_manager::WindowManager::process_event<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:160
17: komorebi::process_event::listen_for_events::closure$0<unknown>
at C:\Users\az02096\dev\komorebi\komorebi\src\process_event.rs:49
18: core::hint::black_box<unknown>
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081\library\core\src\hint.rs:338
⋮ 14 frames hidden ⋮
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
Warning: SpanTrace capture is Unsupported.
Ensure that you've setup a tracing-error ErrorLayer and the semver versions are compatible
2024-09-30T11:06:51.572608Z ERROR komorebi::process_event:
0: The system could not find the environment option that was entered. (os error 203)
Location:
komorebi\src\windows_api.rs:178
```
FWIW, I found out that the actual problem is related to
alacritty + WSL + Zscaler corporate proxy
If I remove either of them from the equation, I can't reproduce the issue.
If I launch the three of them at the same time, then I got those strange errors (but it does not affect only alacritty windows, it messes up everything randomly)
I ended up stopping using alacritty, as windows terminal is not that bad nowadays.
@tardyp commented on GitHub (Oct 14, 2024):
FWIW, I found out that the actual problem is related to
alacritty + WSL + Zscaler corporate proxy
If I remove either of them from the equation, I can't reproduce the issue.
If I launch the three of them at the same time, then I got those strange errors (but it does not affect only alacritty windows, it messes up everything randomly)
I ended up stopping using alacritty, as windows terminal is not that bad nowadays.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tardyp on GitHub (Sep 27, 2024).
Describe the bug
I recently upgraded my wsl setup. Since that. komorebi started loosing track of certain window.
There is always the error message:
If I restart komorebi, the error disapear (so I don't think this is related to actual metadata of the window)
Then it reappears randomly after about 2 hours of normal work.
Operating System
komorebic checkOutputno error in komorebi check
Additional context
I updated komorebi last week, well before the problem started happening.
@tardyp commented on GitHub (Sep 27, 2024):
Related issue might be this bug:
I indeed have zscaler installed on that PC, that may be messing up with my proxy settings, and WSL might be indeed wanting to magically forward the proxy configuration.
https://github.com/microsoft/WSL/issues/11523
But I am not sure how this could impact komorebi.
So a repro might be:
launch a wsl terminal
change the system proxy settings
start a new wsl terminal.
I cannot change manually my proxy settings on my corporate laptop, so I cannot really test this repro.
@tardyp commented on GitHub (Sep 30, 2024):
after recompiling with debug_assertion config I get a stack trace
@tardyp commented on GitHub (Oct 14, 2024):
FWIW, I found out that the actual problem is related to
alacritty + WSL + Zscaler corporate proxy
If I remove either of them from the equation, I can't reproduce the issue.
If I launch the three of them at the same time, then I got those strange errors (but it does not affect only alacritty windows, it messes up everything randomly)
I ended up stopping using alacritty, as windows terminal is not that bad nowadays.