Update version to 0.3.50
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-2022-55a8e10ea8
Please login to add feedback.
0 | 0 | Test Case PipeWire ALSA backend |
0 | 1 | Test Case PipeWire Bluetooth Devices |
0 | 0 | Test Case PipeWire Gnome Control Center |
0 | 0 | Test Case PipeWire Jack Applications |
0 | 0 | Test Case PipeWire Jack Midi Routing |
0 | 0 | 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 | 0 | Test Case PipeWire PipeWire CLI |
0 | 0 | Test Case PipeWire PipeWire default |
0 | 0 | Test Case PipeWire Selected Applications Playback |
0 | 0 | Test Case PipeWire Video Conferencing |
This update has been submitted for testing by wtaymans.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
no issues
Works normally without issues.
This update has been submitted for stable by bodhi.
my sound works fine on Thinkpad P1 gen3
My audio seems to be working fine.
pipewire-jack-audio-connection-kit-0.3.50-1.fc36.x86_64.rpm makes
xorunalpp
crash on startup:Downgrading to pipewire-jack-audio-connection-kit-0.3.49-1.fc36.x86_64 fixes the crash. Also reproducible with
telegram-desktop
@tpmkranz I have the same version of
xournalpp
andpipewire-jack-audio-connection-kit
and this doesn't happen to me. Can you please create a ticket in Bugzilla and link it here? Ideally create the crash report using Abrt ("Problem reporting"), so that it can provide a full backtrace. Thanks.xournalpp works for me as well. Can you paste a more complete backtrace somewhere?
I'm so sorry for the noise. I've tried 0.3.50 again and can't reproduce the crashes anymore. I'd probably forgotten to reboot/re-login after the update and got the crashes when xournalpp and Telegram tried to use the 0.3.50 jack libraries to communicate with the still-running 0.3.49 pipewire (or something of the sort). Is there a way or even a requirement to take back my report as non-functioning? I've noticed that the update didn't install with just
dnf --refresh upgrade
– I hope that wasn't my fault.Works.
no regressions noted
This update has been pushed to stable.