https://bugs.kde.org/show_bug.cgi?id=476866
--- Comment #16 from Prajna Sariputra <putr...@gmail.com> --- I'm now on KDE Plasma 6.3.3 (including KPipeWire and Spectacle), and I just noticed that both Spectacle and KRdp now correctly use my integrated GPU for encoding without bothering the discrete GPU (which I can observe by the fact that running `lspci` or `nvtop` in a terminal soon after Spectacle now shows a delay indicating that those two terminal commands are waiting for the dGPU to start, while before they would not show a delay indicating that Spectacle powered on the dGPU already, plus `nvtop` also shows the iGPU's encoder is used when Spectacle is recording the screen or KRdp has an active connection). However, when looking into KPipeWire's code and commit history I didn't see any change that looks like they would be the fix to this bug, at least as far as my limited understanding goes. In particular, it looks like the code to select devices didn't change (https://invent.kde.org/plasma/kpipewire/-/blob/master/src/vaapiutils.cpp?ref_type=heads#L34) and is still just picking the first device to show up. The order the GPUs appear in the rest of the OS doesn't seem to have changed either, the command `vainfo --display drm` still reports the dGPU (unlike just `vainfo` which does report the iGPU like before) and /dev/dri/renderD128 is still the dGPU. So, I'm not certain if this is really fixed or if this is just a side effect of something else in the system. For what it's worth the KDE Frameworks version is 6.12.0 and the Linux kernel version is 6.13.7, on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
