We believe the bug only affected non-Ubuntu kernels!
Ubuntu Desktop Developer | Launchpad profile
Very fortunate to have skilled programmers able to translate bug info datadumps (particularly my walls of text) into actionable patches - and so quickly too! lol It's damn impressive. Yes, pipewire 1.0.1-1ubuntu3 in noble-proposed is working well on 6.7.2 and now upstream 6.8rc2. I know this bug was only affecting non-stock ubuntu kernels, and 22.04 is still alpha - all all the implications that come with that (especially being part of the bug finding fun before release primetime!). I may be getting my wires crossed and this isn't totally applicable here as it was Pipewire using features not yet available in later kernels, but I feel some compulsion to express that (outside of whacky kernel config setups of course), to my mind distros should always still work reasonably with an upstream kernel. (IME they always have done: Ubuntu/Kubuntu have always done well with upstream kernels using configs trimmed down from ubuntu defaults.) I don't believe one should give a newly-introduced problem less weight simply that it wasn't with one of the stock kernels, unless a bug is solely an upstream regression. If 6.6.0-14-generic is working fine, we can't (shouldn't) stay on it forever or deem it less worthy if bugs are appearing on later kernels: the same problem would only rear its head or be discovered later when we do bump up a version. (Of course, it's also always been clear that ubuntu devs are not responsible to get every kernel working.) When bugs like this happen, I'm grateful a solution can be applied at the package level rather than fixes being limited to stock kernels only. It's very fortunate that this was sorted at the source in pipewire. There's a growing list of distros based on ubuntu (e.g. rhinolinux) who will use slightly (or completely) different kernels with their own patches yet still share Ubuntu's package repos, and they've been hit by a bug like this with 'non-ubuntu' kernels. I'm sure you'd agree but after all these years, I feel it would be very regrettable if we ever found ourselves in a position where a ()ubuntu user was ever confined to 'stock' provided kernels only (whenever they are pushed to the repo) and if they wanted a newer kernel (for a new feature/hardware support/bug fix) have no other option than to rely on acquiring specific distro patches for and patching an upstream kernel everytime. The freedom to build/test a recent kernel has always been very cherishable.
Last edited by Ubunterrific; January 29th, 2024 at 11:47 PM.
Disco ut intelligam. I learn, so that I may understand. https://launchpad.net/~linuxchemist
Originally Posted by 1fallen Actually I filed against apparmor for a different application here:https://ubuntuforums.org/showthread.php?t=2493479 Sounds like you will need to create a apparmor profile for your use. Oops, forgot to say thank you for the links, they didn't solve the particular bug but they were very informative and gave me stuff to try.
Originally Posted by jbicha We believe the bug only affected non-Ubuntu kernels! I'm on 6.6.0-14-generic...
Smask, I need more information about your situation. Could you file a bug as requested earlier in the thread? Did you happen to intentionally remove Snap?
Originally Posted by jbicha There is a fix in progress: https://launchpad.net/ubuntu/+source...1.0.1-1ubuntu3 Good to know, thanks!
Ryzen 9 7950X3D / NZXT Kraken Z63 / Gigabyte X670E Aorus Pro X / 64GB 6000mT/s C36 Kingston Fury Beast / Gigabyte RTX4080 Aero OC / 1TB Samsung 970 Evo / Asus Loki 1kW / Lian-Li O11D Mini / Samsung Odyssey G9 Neo / Win11 / Kubuntu 24.10
Yesterday, I chanced un-pinning the files I'd locked and ran an update. I'm happy to say that the latest versions caused no unwanted silence, and that this thread can now be considered [CLOSED]
check if pipewire-pulse,pipewire-alsa, wireplumber are installed.. .. then do the following 2 commands. systemctl --user restart pipewire.socket pipewire-pulse.socket sudo alsa force-reload . restart may required. . . it fixed mine (temporarily and have to do it at most restart), god knows yours. . . .. . good luck
So I upgraded to 24.04.1 Ubuntu and now all my HDMI devices are unable to produce sound. I am using default kernel that came with this version. So it seems that this bug is not affecting also normal kernels... I installed wireplumber gui and I can see all me HDMI devices (the one connected and the ones not connected) and none of them seems to be "Audio" supported. So I have 2 HDMI devices connected, 1 is monitor which doesn't have Audio support, but other is TV which has Audio supported (that worked before I upgraded). Not sure if the problem is tied to kernel or to wireplumber or even pipewire itself.
View Tag Cloud
Ubuntu Forums Code of Conduct