https://bugs.kde.org/show_bug.cgi?id=459609
--- Comment #1 from Prajna Sariputra <putr...@gmail.com> --- After further investigation it appears that it is just about anything that wants an EGL context that triggers the issue rather than anything Wayland related, since `eglinfo` also turns on the dGPU, and GTK3 apps (like `gtk3-demo`) don't touch the dGPU at all unless I try the OpenGL example in it (which I guess is why I never noticed the issue when I was using GNOME, as it was when most apps still use GTK3). So, at this point I'm not sure if I should report this issue elsewhere (Mesa?) or if it is just how EGL is designed and there is no way around it, any advice would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
