Occasionally upon system startup pulseaudio-control returns "Pulseaudio not started" in polybar. If I run the commands manually from the terminal I do get the expected volume percentages. I have to restart polybar one or two times to get this to resolve.
When this occurs, my system CPU increases to 30%+ and top reports polybar's CPU utilization is something like 7-8% instead of it's normal 0.6-0.7%. Once I restart polybar and correct the "Pulseaudio not started" error, CPU utilization returns to normal.
This only seems to happen intermittently when I start up my system or when I wake from sleep. My assumption is that there is some race condition.
Seems to be two things happening here though:
pulseaudio-control listen is losing communication with pulseaudio, even though pulseaudio is running
Polybar or pulseaudio is going haywire when it is in this state.
Let me know what other information I can provide to help to identify what the issue is.
Occasionally upon system startup
pulseaudio-control
returns"Pulseaudio not started"
in polybar. If I run the commands manually from the terminal I do get the expected volume percentages. I have to restart polybar one or two times to get this to resolve.When this occurs, my system CPU increases to 30%+ and
top
reports polybar's CPU utilization is something like 7-8% instead of it's normal 0.6-0.7%. Once I restart polybar and correct the"Pulseaudio not started"
error, CPU utilization returns to normal.This only seems to happen intermittently when I start up my system or when I wake from sleep. My assumption is that there is some race condition.
Seems to be two things happening here though:
pulseaudio-control listen
is losing communication with pulseaudio, even though pulseaudio is runningLet me know what other information I can provide to help to identify what the issue is.
This is my setup