BSPWM bar fails to be displayed unless killed and restarted #2699
Replies: 1 comment 1 reply
-
|
Is the polybar process actually running bspwm launches? This would tell us whether polybar failed to start or is just not visible. Also, what do the logs show? |
Beta Was this translation helpful? Give feedback.
-
|
@patrick96 Ok, so looking at the logs polybar does start but appears to be stuck in loading module pulseaudio Killing polybar and restarting causes it to succeed with the logs And then proceeds to load other modules. I am not sure what is going on that causes the initial launch of polybar to be stuck at pulseaudio. I think previously I was using Alsa so it worked fine, but now that it got deprecated, I switched to pulseaudio and this is causing an issue. EDIT Looking at the other discussion #2697 Seems like we both have the same issue, polybar seems to be stuck at loading pulseuadio. Somehow restarting polybar seems to make it load it correctly. No idea why |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So following the setup described here: https://github.com/polybar/polybar/wiki#launching-the-bar-in-your-wms-bootstrap-routine
When I launch bspwm i don't see the bar at all. KIlling the bar and restarting it again after login seems to work.
The original bar does not respond to
polybar-msg cmd quiteither. I am not sure how to debug or what's causing the issues. The logs show no error at all before or after restarting.Beta Was this translation helpful? Give feedback.
All reactions