On Mon, 25 Apr 2022 06:46:16 -0500 Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > I'd rather not have to go to that extent for what should be a somewhat > common use case. You're right, this should happen automatically. Alsa allows referencing sound devices by name, instead of the slot they were put into. That *should* allow pipewire to know which device to use no matter which slot it is put in at boot, so it shouldn't be necessary. In my case, it is legacy, so it just keeps propagating. > Is it possible you have some leftover configuration around that is > > causing problems? This would probably be in your home > > directory, and only if you upgrade to new fedora versions. > > > > Maybe, I don't think I've done a "fresh" install since Fedora 14. I looked and I still have a .pulse directory in ~/, and it doesn't seem to be hurting anything, so this is probably not the issue. I do find a pipewire directory in ~/.config, and in media-session.d there are 4 files that configure pipewire. I see a default set, but the device names don't seem to correspond to the alsa device names. Maybe the next time this happens, you could check if those have changed. Perhaps back them up when pipewire is working, and then you can compare, and restore if it breaks. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
