https://bugs.kde.org/show_bug.cgi?id=498535
--- Comment #14 from Ron <[email protected]> --- And, with all of that said, it turns out that I misread you saying that it *did* work with pipewire installed - somehow as that *it didn't work either*. So I'll add "never answer email before coffee" ... It's been quite a while since most desktoppy things (which any KDE app is, regardless of what DE you actually use) were happy with using raw device access (like direct alsa) because the days of having just one thing using your sound hardware at a time is long over. Pipewire isn't the same sort of trainwreck that PulseAudio was, and I think you are just going to have to bite the bullet that is having it installed even if you don't configure everything to use it as an intermediary to the low level alsa drivers. Kdenlive itself doesn't directly do anything with audio, that is all handled by other dependency libs (and by several of them depending on whether it's DE bling noises or video audio that is playing) - so even if it *is* possible to do something about this, it's probably not in our ballpark to be able to fix it anyway, it will be other deps that need fixing. If someone *really* cares about this enough to send a patch to eliminate the pipewire dependency to all the places that would need to be done, then it might get considered depending on what needs to be done. But it looks like this now really just boils down to "The AppImage depends on system pipewire" - and we can't really declare dependencies with those like we can with native packaging, so at best we can just document this requirement. It's 2026 and that's hardly the most onerous or ugly thing that running desktop graphical applications required you to have installed. Still sorry, but at least we've got to the bottom of it, so I'm closing this now as "expected" behaviour. -- You are receiving this mail because: You are watching all bug changes.
