1. Please describe the problem: After kernel update from 6.4.15-200 to 6.5.5-200 videos and audio stutter. 2. What is the Version-Release number of the kernel: 6.5.5-200 3. Did it work previously in Fedora? Yes If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 6.5.5-200 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes, just reboot with kernel 6.5.5-200 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: No 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Reproducible: Always
Created attachment 1991996 [details] Kernel logs
By the way, the parameters for VMware in pipewire.conf and 50-alsa-config.lua look like this: pipewire.conf: # These overrides are only applied when running in a vm. vm.overrides = { default.clock.rate = 19200 default.clock.quantum = 1024 default.clock.min-quantum = 32 default.clock.max-quantum = 2048 default.clock.quantum-limit = 8192 } 50-alsa-config.lua: ["vm.node.defaults"] = { ["api.alsa.period-size"] = 1024, ["api.alsa.headroom"] = 8192, }, These parameters work with kernel 6.4.15-200.
An upgrade to kernel 6.5.6-200 solved the problem. But there is still the same problem when I upgrade pipewire to version 0.3.81.
I have this problem but for me the only cause was upgrading to pipewire-0.3.81-1 (F37, F38 and F39) but it seems to happen only in a VirtualBox guest. For me kernels have not played a role in this. On at least one native system that version of pipewire is working. Problem visible when trying to play a video on Youtube... nothing in a VM will play with pipewire-0.3.81-1. Downgrading to pipewire-0.3.80-1 fixes all VMs (Fedora 37, 38 and 39 guests).
This should probably be reassigned to pipewire.
I downgraded to pipewire-0.3.67-1 which works as well. Are there other parameters in pipewire or wireplumber which I can try with pipewire-0.3.81-1 in VMware?
(In reply to Heinrich Bauer from comment #6) > Are there other parameters in pipewire or wireplumber which I can try with > pipewire-0.3.81-1 in VMware? No idea myself. Sadly looks like it's not just virtual machines failing, I now have an example of a native system failing, a laptop running Fedora 39 beta branch. Downgrading to pipewire-0.3.80-1 fixes playing Youtube videos. Hardware: ASUS G750JS 1 x Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) NVIDIA Corporation GK104M [GeForce GTX 870M] (rev a1)
Meanwhile I installed pipewire-0.3.80-1 locally which works for me as well.
Proposed as a Blocker for 39-final by Fedora user nixuser using the blocker tracking app because: pipewire-0.3.81-1 needs to be unpushed back to pipewire-0.3.80-1 or declared a blocker, since as it is now it's sitting as a 0-day bombshell for a lot of users. Seems to impact VirtualBox VMs 100%, VMWare (unknown %) and at least some native systems (I have a laptop example).
The update is not in stable, so this cannot be a release blocker. The blocker process has nothing to do with unpushing updates from the 0-day queue.
FEDORA-2023-e34dfbc923 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e34dfbc923
Yep, that's a fix, it's working for me again. Also the Rawhide scratch build fixes Rawhide also. Thanks for doing this so quickly.
The update works. Thanks a lot.
Please don't close bugs before updates go stable.
Sorry, is my first bug on Bugzilla. Next time I won't do it again.
no problem, it's easily fixed :) just letting you know for next time.
FEDORA-2023-e34dfbc923 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.