https://bugs.kde.org/show_bug.cgi?id=512429
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #40 from [email protected] --- I think I figured out what causes this problem. There was a recent change in KPipeWire (which is what Spectacle uses when recoding on Wayland) that fixed hardware encoding. However, now KPipeWire tries using hardware encoding with nvidia-vaapi-driver. This is because nvidia-vaapi-driver has a bug in the function getConfigAttributes, where it doesn't check whether the config attributes request is for decoding or encoding and always announces all GPU capabilities, making KPipeWire use it for encoding by mistake. I have created a pull request to fix this, which I have tested locally and fixes the issue for me: https://github.com/elFarto/nvidia-vaapi-driver/pull/423 So, in my opinion, this is neither a bug in Spectacle or KPipeWire, but a bug in nvidia-vaapi-driver that was exposed due to a recent change in KPipeWire. -- You are receiving this mail because: You are watching all bug changes.
