Update to 0.3.24
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-2c994d0609Please login to add feedback.
| 0 | 1 | Test Case PipeWire ALSA backend |
| 0 | 1 | Test Case PipeWire Bluetooth Devices |
| 0 | 0 | Test Case PipeWire Jack Applications |
| 0 | 0 | Test Case PipeWire Jack Midi Routing |
| 0 | 1 | Test Case PipeWire Pavucontrol Add Remove |
| 0 | 1 | Test Case PipeWire Pavucontrol Basics |
| 0 | 0 | Test Case PipeWire Pavucontrol Mixing |
| 0 | 0 | Test Case PipeWire Pavucontrol Recording |
| 0 | 1 | Test Case PipeWire PipeWire CLI |
| 0 | 1 | Test Case PipeWire PipeWire default |
| 0 | 1 | Test Case PipeWire Selected Applications Playback |
This update has been submitted for testing by wtaymans.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
wtaymans edited this update.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Works
This update can be pushed to stable now if the maintainer wishes
Tests works for me.
This update has been submitted for stable by wtaymans.
This update has broken sound on my system.
Before this update, I had modified
/etc/pipewire/{jack,pipewire,pipewire-pulse.conf}addinglog.level = 3to help with finding a rarely occurring problem.Updating to
pipewire-0.3.24-1.fc34kept these three config files as they were and saved the new ones as/etc/pipewire/{jack,pipewire,pipewire-pulse.conf}.rpmnew.Apparently, the configuration file format has changed, though. Now 0.3.24-1 misinterprets the old config files,
pipewire-pulsedoes not run properly, and every time a client tries to connect (mpv, pavucontrol, etc.) it just hangs indefinitely.Renaming the
*.rpmnewfiles to the the proper file names, re-applying mylog.level = 3edits, and rebooting fixes the issue.This update has been pushed to stable.
@wtaymans please note above feedback. I believe we know of similar issues upgrading from previous releases.
Can we please avoid this kind of thing in future? It's really really bad if a core thing like pipewire flat out dies trying to read its own config file from a previous version. This just should not be necessary with proper planning and design.