Skip to content

Pulseaudio module can get stuck if started alongside pulseaudio #2707

@patrick96

Description

@patrick96

Discussed in #2699

Originally posted by vikigenius April 26, 2022
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 quit either. I am not sure how to debug or what's causing the issues. The logs show no error at all before or after restarting.

See also #2697

The issue is that polybar waits for a signal from its callback function but if the signal is sent before pa_threaded_mainloop_wait is called in the module constructor, the signal is lost and the module (and thus polybar) waits forever (see 6d7a7c0).

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions