Comment 17 for bug 1975823

Yeah, you're right. But after I re-read the whole ticket (and especially the original report) I recognized I could have made a better job describing my actual problem and what the imagined fixed behaviour should be, instead of trying to find the cause myself.^^

Yes, if I add the configurations (which routes all Alsa output over Pipewire I guess?) the applications are behaving as intended, following the global system selected sink and volume.

And as far as I can tell, this was the default configuration of Ubuntu in the past with Pulseaudio for Alsa applications as well, but was just missed to do with Pipewire on the transition?