stable

pipewire-0.3.24-1.fc34

FEDORA-2021-2c994d0609 created by wtaymans 3 years ago for Fedora 34

Update to 0.3.24

How to install

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-2c994d0609

This update has been submitted for testing by wtaymans.

3 years ago

This update's test gating status has been changed to 'ignored'.

3 years ago

This update's test gating status has been changed to 'waiting'.

3 years ago

wtaymans edited this update.

3 years ago

This update's test gating status has been changed to 'ignored'.

3 years ago

This update has been pushed to testing.

3 years ago
User Icon pwalter commented & provided feedback 3 years ago
karma

Works

This update can be pushed to stable now if the maintainer wishes

3 years ago
karma

This update has been submitted for stable by wtaymans.

3 years ago
User Icon ndim commented & provided feedback 3 years ago
karma

This update has broken sound on my system.

Before this update, I had modified /etc/pipewire/{jack,pipewire,pipewire-pulse.conf} adding log.level = 3 to help with finding a rarely occurring problem.

Updating to pipewire-0.3.24-1.fc34 kept 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-pulse does not run properly, and every time a client tries to connect (mpv, pavucontrol, etc.) it just hangs indefinitely.

Renaming the *.rpmnew files to the the proper file names, re-applying my log.level = 3 edits, and rebooting fixes the issue.

This update has been pushed to stable.

3 years ago
User Icon adamwill commented & provided feedback 3 years ago

@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.


Please login to add feedback.

Metadata
Type
bugfix
Karma
2
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
14 days
Dates
submitted
3 years ago
in testing
3 years ago
in stable
3 years ago
modified
3 years ago
BZ#1789358 bluetooth headset microphone does not work
0
1
BZ#1844859 Bluetooth headsets not properly supported on linux - bad quality or mic not working at all
0
0
BZ#1916942 Pipewire doesn't see my bluetooth headset's microphone
0
0
BZ#1925790 Unable to listen to audio on bluetooth headphone (A2DP)
0
0
BZ#1925810 Constantly consumes a significant amount of CPU time if speech-dispatcher is running
0
0
BZ#1926505 Firefox doesn't produce any audio output on Pipewire -pulseaudio
0
0
BZ#1927891 Pipewire-pulseaudio does not detect microphone
0
0
BZ#1928257 update to 0.3.21-2 killed audio input support
0
0
BZ#1930459 [abrt] pipewire-pulseaudio: flush_items(): pipewire-pulse killed by SIGSEGV
0
0
BZ#1932677 volume control and bluetooth device
0
0
BZ#1933111 Audio locking after system suspends
0
0
BZ#1933128 [abrt] pipewire-pulseaudio: flush_items(): pipewire-pulse killed by SIGSEGV
0
0
BZ#1933496 [abrt] pipewire: pw_array_clear(): pipewire killed by SIGSEGV
0
0
BZ#1934286 no sound on HDMI TV
0
0
BZ#1937713 [abrt] pipewire-pulseaudio: client_cleanup_stream(): pipewire-pulse killed by SIGSEGV
0
0
BZ#1937821 Sound output stops after a while of using the system
0
0
BZ#1938026 [abrt] pipewire-pulseaudio: pw_proxy_remove(): pipewire-pulse killed by SIGABRT
0
0
BZ#1940187 [abrt] pipewire: spa_list_remove(): pipewire-media-session killed by SIGSEGV
0
0
BZ#1940190 Lot of "Broken pipe" errors on Fedora 34
0
0
BZ#1940311 Orca, the screen reader, does not speak after log in screen, and volume controls cannot be found
0
0

Automated Test Results