Patrick Ziegler

I can't reproduce this myself unfortunately. Which applications were running in your tray at the time? This behavior probably depends on how those applications interact with polybar. Looking at the...

Nice, thanks for testing. Glad this was an easy fix, tray stuff usually is anything but

Clarifying question: Are you using a compositor in these screenshots? I have narrowed it down to d743a228173e50b6dc98293e6db05eca962d334c triggering this issue. The problem is that we just don't interact too well...

I reverted the rendering change in #3091. Please try it out to see if it fixes your issue (it did work for me)

This looks very promising :D I unfortunately don't really have time to review this right now, any spare time I have, I want to put into finishing the next release....

Thanks for the detailed report. There is nothing obvious sticking out right now. I'll need to reproduce this myself. Just a few followup questions for that: * How did you...

Since I don't have dualshock controllers, this will be hard for me to reproduce. But what would be immensely helpful is a full thread dump of all the bars when...

Thanks :) Now we know where the bar is stuck. For some reason, the `ncspot-playpausestop` module is getting stuck while reading the script output for `hook-0`. Even with that knowledge,...

The restarted polybar is probably obscured by something, try setting `wm-restack = i3`. If that doesn't help please post the output of `xwininfo -tree -root` before (when it is working)...

I suggested setting `wm-restack = i3` since you don't have the setting in your config (`true` or `false` don't have a meaning here, that was an error on my part)