EDIT
It seems that "on-click" isn't working on any of the modules for some reason. I had several set for custom modules and they suddenly aren't working.
All scripts invoke sudo as they aren't compatible with pam. They worked as recently as a few days ago. There are no journalctl errors listed. I'm not sure how to debug this.
I've noticed that everytime I adjust style.css and then refresh sway, the entire system freezes - again with no journalctl errors listed. I have to hard reset each time this happens. If I log out of sway and log back in this doesn't happen. I can otherwise refresh sway repeatedly and it won't crash unless I've edited style.css.
After restarting I used a different script and it's working properly. There must be something conflicting in my sway config that isn't allowing it to pop-up correctly. This is not a bug in waybar - sorry.
EDIT - THIS IS AN ISSUE WITH SWAY CONFIG AND NOT WAYBAR -- DISREGARD
config
EDIT It seems that "on-click" isn't working on any of the modules for some reason. I had several set for custom modules and they suddenly aren't working.
All scripts invoke sudo as they aren't compatible with pam. They worked as recently as a few days ago. There are no journalctl errors listed. I'm not sure how to debug this.
I've noticed that everytime I adjust style.css and then refresh sway, the entire system freezes - again with no journalctl errors listed. I have to hard reset each time this happens. If I log out of sway and log back in this doesn't happen. I can otherwise refresh sway repeatedly and it won't crash unless I've edited style.css.