https://bugs.kde.org/show_bug.cgi?id=469016
--- Comment #60 from pallaswept <pallasw...@proton.me> --- (In reply to Robert from comment #58) > Maybe the scrolling issue is related to previews having audio control. There is no evidence of reliance on both video and audio being manipulated, the issues will occur with one or the other alone. You can see this in the posts I made above where either audio alone or window captures with no audio, caused failures of the system to respond. > (In reply to pallaswept from comment #55) > > (In reply to nsane457 from comment #53) > > > The issue seems to reside in KPipeWire. > > > > Please see my comments above. It's clear that this is definitely a > > pipewire-related issue. > > Yes. I removed KPipeWire while keeping pipewire and haven't been able to > reproduce the issue. Yes of course, because you have removed KDE's library for interaction with pipewire. > KPipeWire is the specific library related to pipewire that is causing it. Correlation does not imply causation. Kpipewire's name is pretty self-explanatory. It is how KDE interfaces with pipewire via Qt. But removing it and seeing the fault gone doesn't directly imply that the issue resides in kpipewire itself. What if you remove pipewire and keep kpipewire? Or just deliberately avoid or invoke kpipewire by means such as the volume monitor or window previews? You've also then avoided or invoked pipewire itself, and wireplumber for that matter, not to mention Qt - and the result is the same. So how can you know that the issue is not within pipewire or even wireplumber or Qt, if you have ceased interaction between them all? It would be a mistake to reduce the issue to being specifically caused by kpipewire when there is no direct evidence to suggest it. See for example the other posters' related issues above, where KDE interacting with pipewire via kpipewire, caused KDE faults, and were fixed in pipewire. It's quite possible, even quite likely, that the issue resides in kpipewire, but I see no conclusive evidence yet that "kpipewire... is causing it". By removing kpipewire, and removing the fault, you've shown, as I did earlier, a direct relationship between the fault and interaction with pipewire, but not with kpipewire itself. -- You are receiving this mail because: You are watching all bug changes.
