Bug 1943867
| Summary: | pipewire-pulse.service starts before pipewire.service | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ian Stapleton Cordasco <sigmavirus24> |
| Component: | pipewire | Assignee: | Wim Taymans <wtaymans> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | brunovern.a, information, sigmavirus24, vquintans, wtaymans |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-30 18:27:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I think this can be fixed by altering /usr/lib/systemd/user/pipewire-pulse.service to include Wants=pipewire.service After=pipewire.service In the [Unit] section. See this diff as an example --- /usr/lib/systemd/user/pipewire-pulse.service 2021-03-18 09:42:38.000000000 -0500 +++ pipewire-pulse.service.fixed 2021-04-02 15:10:02.241976931 -0500 @@ -15,6 +15,8 @@ # socket-service relationship, see systemd.socket(5). Requires=pipewire-pulse.socket ConditionUser=!root +Wants=pipewire.service +After=pipewire.service [Service] LockPersonality=yes I have pushed this upstream: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/78db493d0d4659e8b3cc21df5818f66c27ed17bb Thank you! I've been running with that patch and my audio has been flawless across restarts! 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 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. Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: On Fedora 33, I'm trying out pipewire in anticipation of Fedora 34 stabilizing and upgrading. I ran sudo dnf swap --allowerasing pulseaudio pipewire-pulseaudio systemctl --user daemon-reload killall pulseaudio systemctl --user enable pipewire.service pipewire.socket pipewire-pulse.service pipewire-pulse.socket I then logged out and logged back in and audio wasn't working for me (Spotify from Flathub, Firefox from Fedora repos playing videos - nothing produced audio). I ran systemctl --user status pipewire pipewire-pulse And I noticed that the pid for /usr/bin/pipewire-pulse was newer than the pid for /usr/bin/pipewire but older than /usr/bin/pipewire-media-session. When I ran pipewire-media-session from a terminal, audio worked, so I restarted pipewire-pulse.service and audio works. Version-Release number of selected component (if applicable): 0.3.24 How reproducible: Every time the services start on login so far Steps to Reproduce: 1. Swap pulseaudio for pipewire-audio 2. Enable pipewire related services with systemctl 3. Log out and back in and observe audio not working; restart pipewire-pulse.service to get audio working Actual results: Audio doesn't work by default Expected results: Audio just works Additional info: