Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: The default systemd preset for unlisted services (such as pipewire-pulse.socket) is disabled. This results in not working sound after replacing pulseaudio with pipewire-pulseaudio. See https://bodhi.fedoraproject.org/updates/FEDORA-2020-4fbf4c6152 for details. Therefore, I suggest to add pipewire-pulse.socket to /usr/lib/systemd/user-preset/90-default-user.preset.
*** Bug 1904241 has been marked as a duplicate of this bug. ***
Shouldn't this be target at F34+ instead?
Well, F33 allows you to swap pulseuadio and pulseaudio-pipewire just fine (since pipewire 0.3.17), so I do not really see a reason why not to target F33. But sure, if you think this is a "risky" change, one can defer it to F34.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #2) > Shouldn't this be target at F34+ instead? It would make it easier for people on F33 testing pipewire-pulseaudio if they ever have to install/remove the package multiple times. I know the symlink stays there when the package is removed, but if for some reason the unit file is renamed you'd have to run systemctl again to re-enable it. There won't be any change for those who stay on PulseAudio, since it and pipewire-pulseaudio are mutually exclusive. PipeWire's main unit already has a preset.
I think this dropped off everyone's radar... Can you use the template: https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices/#_how_to_enable_a_service_by_default and let us know what releases and services/sockets you still need?
Did the minimal install of F34 today and couldn't get sound working ultimately removed pipewire with pipewire-pulse to run pulseaudio, then reinstalled pipewire and pipewire-pulse to find out after much work that the socket was not enabled o begin with
* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? No. * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? No (It's an UNIX fs socket). * Is the service non-persistent (i.e. run once at startup and exit)? No. * What is the exact name (or names) of the systemd unit files to be enabled? pipewire-pulse.socket * Is this request for all Fedora deliverables or only for some Editions (list them)? All. The enablement of this should match pipewire.socket, which is currently enabled globally. https://src.fedoraproject.org/rpms/fedora-release/pull-request/187 (f34) https://src.fedoraproject.org/rpms/fedora-release/pull-request/188 (rawhide)
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This was done in F34+.