Originally created by @nlaocs on GitHub (Jul 9, 2025).
Summary
When using komorebi bar while connected to Mullvad VPN, the following error occurs.
.\komorebi-bar.exe
2025-07-09T01:17:19.370243Z INFO komorebi_bar: found configuration file: C:\Users\nlaocs\komorebi.bar.json
2025-07-09T01:17:19.381580Z INFO komorebi_bar: watching configuration file for changes
2025-07-09T01:17:19.626251Z INFO komorebi_bar::bar: attempting
to add custom font family: JetBrains Mono NFP
2025-07-09T01:17:19.640441Z INFO komorebi_bar: subscribed to komorebi notifications: "komorebi-bar-subapical"
2025-07-09T01:17:19.928924Z WARN komorebi_bar::bar: couldn't find the monitor index of this bar, if the bar is starting up this is normal until it receives the first state from komorebi.
2025-07-09T01:17:19.929087Z INFO komorebi_bar::bar: widget configuration options applied
2025-07-09T01:17:19.929165Z INFO komorebi_bar::bar: attempting
to add custom font family: JetBrains Mono NFP
2025-07-09T01:17:19.990526Z WARN komorebi_bar::bar: couldn't find the monitor index of this bar, if the bar is starting up this is normal until it receives the first state from komorebi.
2025-07-09T01:17:19.990662Z INFO komorebi_bar::bar: widget configuration options applied
2025-07-09T01:17:19.999320Z INFO komorebi_bar::bar: Found this
bar's monitor. The bar will be enabled!
2025-07-09T01:17:21.655071Z INFO komorebi_bar::bar: attempting
to add custom font family: JetBrains Mono NFP
2025-07-09T01:17:21.714139Z INFO komorebi_bar::bar: work area offset applied to monitor: 0
2025-07-09T01:17:21.714303Z INFO komorebi_bar::bar: widget configuration options applied
2025-07-09T01:17:21.715836Z INFO komorebi_bar::bar: updated bar position
2025-07-09T01:17:21.716019Z INFO komorebi_bar::bar: updated bar position
The application panicked (crashed).
Message: assertion `left == right` failed
left: 0
right: 6
Location: C:\Users\runneradmin\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\netdev-0.34.0\src\interface\windows.rs:44
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
When I launch the bar with VPN enabled, it crashes immediately. Even if I disable VPN before launching and then enable it after launching, it still crashes.
Version Information
OS name: Microsoft Windows 11 Pro
OS version: 10.0.26100 N/A ビルド 26100
(Extracted manually because the language setting is Japanese.)
PS C:\Users\nlaocs> komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\nlaocs
Looking for configuration files in C:\Users\nlaocs
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\nlaocs\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Originally created by @nlaocs on GitHub (Jul 9, 2025).
### Summary
When using komorebi bar while connected to Mullvad VPN, the following error occurs.
```
.\komorebi-bar.exe
2025-07-09T01:17:19.370243Z INFO komorebi_bar: found configuration file: C:\Users\nlaocs\komorebi.bar.json
2025-07-09T01:17:19.381580Z INFO komorebi_bar: watching configuration file for changes
2025-07-09T01:17:19.626251Z INFO komorebi_bar::bar: attempting
to add custom font family: JetBrains Mono NFP
2025-07-09T01:17:19.640441Z INFO komorebi_bar: subscribed to komorebi notifications: "komorebi-bar-subapical"
2025-07-09T01:17:19.928924Z WARN komorebi_bar::bar: couldn't find the monitor index of this bar, if the bar is starting up this is normal until it receives the first state from komorebi.
2025-07-09T01:17:19.929087Z INFO komorebi_bar::bar: widget configuration options applied
2025-07-09T01:17:19.929165Z INFO komorebi_bar::bar: attempting
to add custom font family: JetBrains Mono NFP
2025-07-09T01:17:19.990526Z WARN komorebi_bar::bar: couldn't find the monitor index of this bar, if the bar is starting up this is normal until it receives the first state from komorebi.
2025-07-09T01:17:19.990662Z INFO komorebi_bar::bar: widget configuration options applied
2025-07-09T01:17:19.999320Z INFO komorebi_bar::bar: Found this
bar's monitor. The bar will be enabled!
2025-07-09T01:17:21.655071Z INFO komorebi_bar::bar: attempting
to add custom font family: JetBrains Mono NFP
2025-07-09T01:17:21.714139Z INFO komorebi_bar::bar: work area offset applied to monitor: 0
2025-07-09T01:17:21.714303Z INFO komorebi_bar::bar: widget configuration options applied
2025-07-09T01:17:21.715836Z INFO komorebi_bar::bar: updated bar position
2025-07-09T01:17:21.716019Z INFO komorebi_bar::bar: updated bar position
The application panicked (crashed).
Message: assertion `left == right` failed
left: 0
right: 6
Location: C:\Users\runneradmin\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\netdev-0.34.0\src\interface\windows.rs:44
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
```
When I launch the bar with VPN enabled, it crashes immediately. Even if I disable VPN before launching and then enable it after launching, it still crashes.
### Version Information
```
OS name: Microsoft Windows 11 Pro
OS version: 10.0.26100 N/A ビルド 26100
```
(Extracted manually because the language setting is Japanese.)
```
PS C:\Users\nlaocs> komorebic --version
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
```json
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.35/schema.bar.json",
"monitor": 0,
"font_family": "JetBrains Mono NFP",
"theme": {
"palette": "Base16",
"name": "Ashes",
"accent": "Base0D"
},
"left_widgets": [
{
"Komorebi": {
"workspaces": {
"enable": true,
"hide_empty_workspaces": false
},
"layout": {
"enable": true
},
"focused_window": {
"enable": true,
"show_icon": true
}
}
}
],
"right_widgets": [
{
"Update": {
"enable": true
}
},
{
"Media": {
"enable": true
}
},
{
"Storage": {
"enable": true
}
},
{
"Memory": {
"enable": true
}
},
{
"Network": {
"enable": true,
"show_total_data_transmitted": true,
"show_network_activity": true
}
},
{
"Date": {
"enable": true,
"format": "DayDateMonthYear"
}
},
{
"Time": {
"enable": true,
"format": "TwentyFourHour"
}
},
{
"Battery": {
"enable": true
}
}
]
}
```
### Hotkey Configuration
N/A
### Output of komorebic check
```
PS C:\Users\nlaocs> komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\nlaocs
Looking for configuration files in C:\Users\nlaocs
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\nlaocs\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
```
adam
added the bug label 2026-01-05 14:52:09 +01:00
I've been suspecting the default interface part of the network widget to be the culprit.
Could you also try with that disabled? Something like this:
{"Network":{"enable":true,"data_refresh_interval":2,"show_default_interface":false,// this one here
"show_total_activity":false,"show_activity":true}},
@CtByte commented on GitHub (Jul 10, 2025):
I've been suspecting the `default interface` part of the network widget to be the culprit.
Could you also try with that disabled? Something like this:
```json
{
"Network": {
"enable": true,
"data_refresh_interval": 2,
"show_default_interface": false, // this one here
"show_total_activity": false,
"show_activity": true
}
},
```
If any of the network settings are set to true, the bar will crash.
If only enable is set to true, the bar will not crash (although this is meaningless).
@nlaocs commented on GitHub (Jul 10, 2025):
If any of the network settings are set to true, the bar will crash.
If only enable is set to true, the bar will not crash (although this is meaningless).
I use different VPNs for work and the bar does not crash, but I have also seen issues with other VPNs in the past 🤔
One solution could be to silently "disable" the widget on any error, instead of letting it crash the whole bar. I will keep this in mind and when I get the time will look into it.
@CtByte commented on GitHub (Jul 10, 2025):
That is interesting, thank you for testing this.
I use different VPNs for work and the bar does not crash, but I have also seen issues with other VPNs in the past 🤔
One solution could be to silently "disable" the widget on any error, instead of letting it crash the whole bar. I will keep this in mind and when I get the time will look into it.
@nlaocs Hi there, would it be possible for you to test if this version still fails for you?
@CtByte commented on GitHub (Oct 5, 2025):
@nlaocs Hi there, would it be possible for you to test if [this version](https://github.com/LGUG2Z/komorebi/actions/runs/18235052593) still fails for you?
The bar no longer crashes when launched with a VPN enabled.
I tested this after reverting the config to the state where it crashed in the previous version.
Thank you so much for fixing it!
@nlaocs commented on GitHub (Oct 6, 2025):
The bar no longer crashes when launched with a VPN enabled.
I tested this after reverting the config to the state where it crashed in the previous version.
Thank you so much for fixing it!
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 @nlaocs on GitHub (Jul 9, 2025).
Summary
When using komorebi bar while connected to Mullvad VPN, the following error occurs.
When I launch the bar with VPN enabled, it crashes immediately. Even if I disable VPN before launching and then enable it after launching, it still crashes.
Version Information
(Extracted manually because the language setting is Japanese.)
Hotkey Configuration
N/A
Output of komorebic check
@CtByte commented on GitHub (Jul 10, 2025):
can you try with the network widget disabled?
@nlaocs commented on GitHub (Jul 10, 2025):
It started up fine without the network widget.
@CtByte commented on GitHub (Jul 10, 2025):
I've been suspecting the
default interfacepart of the network widget to be the culprit.Could you also try with that disabled? Something like this:
@nlaocs commented on GitHub (Jul 10, 2025):
If any of the network settings are set to true, the bar will crash.
If only enable is set to true, the bar will not crash (although this is meaningless).
@CtByte commented on GitHub (Jul 10, 2025):
That is interesting, thank you for testing this.
I use different VPNs for work and the bar does not crash, but I have also seen issues with other VPNs in the past 🤔
One solution could be to silently "disable" the widget on any error, instead of letting it crash the whole bar. I will keep this in mind and when I get the time will look into it.
@CtByte commented on GitHub (Oct 5, 2025):
@nlaocs Hi there, would it be possible for you to test if this version still fails for you?
@nlaocs commented on GitHub (Oct 6, 2025):
The bar no longer crashes when launched with a VPN enabled.
I tested this after reverting the config to the state where it crashed in the previous version.
Thank you so much for fixing it!