-
-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Network module does not update ramp-signal when disconnected #2805
Comments
Hmm, from a quick look at the code, it seems like the code updating the signal values may not run at all, leaving the signal value at the old value. Just as a sanity check, what polybar command are you using? Are you by chance using the Also, can you add the |
I have only been running "polybar" with no flags on both startup, and when I run it from the terminal. When I add |
Checklist
Steps to reproduce
format-disconnected = <ramp-signal> <label-disconnected>
<ramp-signal>
does not update toramp-signal-0
, instead staying as the last<ramp-signal>
icon it had before going offline. It WILL update to the proper icon when the wifi is switched back on however.polybar
from the terminal WILL display the proper<ramp-signal>
icon (ramp-signal-0
).Minimal config
Polybar log
Expected behavior
When I use
Fn + PrtScr
my laptop disconnects the wifi. I should see the emoticon representative of my connection switch to one with x's for eyes, indicating there is no connection.Actual behavior
The icon stays as whatever my last signal strength was before going offline.
Opening the terminal and launching a 2nd polybar on top of the first shows the proper signal icon. In either case, hitting
Fn + PrtScr
again to go back online WILL update the icon to reflect my online signal strength. It's only switching to offline that I get this issue.Images attatched
Window Manager and Version
KWin 5.25.4
Linux Distribution
Arch 5.19.5
Polybar version
polybar 3.6.3
Additional Context / Screenshots
Intended output:
Actual output:
The text was updated successfully, but these errors were encountered: