mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: When I connect to Mullvad VPN, Bar crashes. #643
Reference in New Issue
Block a user
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?
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!