Description of problem: When installing pipewire-pulseaudio for the first time, the pipewire-pulse.socket is first enabled, and then immediately disabled again. Version-Release number of selected component (if applicable): pipewire-pulseaudio-0.3.18-1.fc33.x86_64 Steps to Reproduce: 1. dnf install pipewire-pulseaudio # Or "dnf swap" if removing pulseaudio too Actual results: First output from systemctl linking pipewire-pulse.socket to /etc, and then removing it again. Additional info: The scripts section first has a command which enables this, with a comment it should be removed when distro defaults are updated. This will enable the socket. Then there is a command to do a "preset" of the socket. This will remove the socket again unless the default is already updated. If the workaround is to have any effect during installation, it needs to be done AFTER the preset. (With the current scripts, a later update will enable the socket again, in case it isn't done manually in the meantime.)
I think this is fixed now that the system defaults are updated?
FEDORA-2021-f279349372 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f279349372
FEDORA-2021-f279349372 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f279349372` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f279349372 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-f279349372 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
I wasn't quick enough to reply before this BZ was closed by the errata, but better late than never. I've now verified by updating a different machine to the latest versions of everything, and then swap from pulseaudio to pipewire. pipewire-pulse.socket was indeed enabled after that, so this bug is fixed. Thanks for your efforts!