Wellington Wallace

>What about WP? Is it 0.5.5? Yes. >Ah, and do you have several sinks to choose? I do. Yes. Besides the optical port of my onboard card I also use...

>By the way, I have this in my ~/.config/wireplumber/wireplumber.conf.d/10-defaults.conf And I do not see how the settings you've made could cause the problem you are facing. Maybe some kind of...

>The PW crash bug that I've linked to is a complete disaster and it only has 3 upvotes including mine Somehow I do not remember having ever seen PipeWire crashing....

In any case like I said in the other issue the patches I did only do something if a target node is set by the stream https://github.com/wwmm/easyeffects/blob/c1b678a11846aa6eb9a3392a5332e8c1c5dab713/src/pipe_manager.cpp#L342. That is why...

>However, I just did a quick search for target in pw-dump while playing a Youtube video in Firefox and got "target.object": "jack_out" in the node of FF. Same goes for...

>I strongly suspect there are race conditions going on. For a long time I suspected that this bug was related to the fact we linked and unlinked our filters based...

>I'm not qualified to say whether or not the EE's "ad-hoc" way of handling PW graph is ad-hoc or PW is simply missing the right infra, but something there does...

>PW was reading original PA's configs in ~/.config/pulse which were made before PW even existed and contained lines like load-module module-jack-sink & set-default-sink jack_out for the original jackd. No wonder...

@LebedevRI also try to install the pacakge with EasyEffects debug symbols and run `sudo coredumpctl info` right after a crash so we can have some idea about what it is...

>From the little bit of poking at it I did do when I first noticed it happening, it seems to only crash if I try to open the Native Window...