Hey people,
KDE recently merged in more support for discrete GPUs through swicheroo-control and I noticed that the logic both KDE and Gnome use does not probe if the GPU is actually discrete/dedicated or not, only if it was used at startup.
On Desktop setups, it's not uncommon to see a discrete/dedicated GPU as the default and an integrated GPU on the side, which both desktop environments would assume to be the better one, with Gnome even adding a context option to "Launch using Dedicated Graphics Card" when in reality it would use the integrated GPU.
I've looked into contributing to fix the issue, but from the outside, it appears that RedHat is no longer interested in spending resources on it, essentially leaving it unmaintained for the time being.
This issue isn't new and has been bothering users for a while: https://github.com/ValveSoftware/steam-for-linux/issues/8074 https://github.com/flathub/com.valvesoftware.Steam/issues/784 https://github.com/ValveSoftware/steam-for-linux/issues/8069 https://github.com/ValveSoftware/steam-for-linux/issues/8179 https://github.com/ValveSoftware/steam-for-linux/issues/8983 https://github.com/bottlesdevs/Bottles/issues/2967 https://github.com/NixOS/nixpkgs/issues/246007 etc.
Does anyone know if there is something that can be done about this?
Jan
Jan Drögehoff composed on 2023-08-14 19:19 (UTC+0200):
I've looked into contributing to fix the issue, but from the outside, it appears that RedHat is no longer interested in spending resources on it, essentially leaving it unmaintained for the time being.
What would you like to bet this is related to Fedora's commitment to Wayland that leaves its X11 users languishing with a two year old Xorg server version 1.20.14 even in Rawhide? Tumbleweed, Mageia 9 and Arch on 21.1.8, Bookworm 21.1.7.
What would you like to bet this is related to Fedora's commitment to Wayland that leaves its X11 users languishing with a two year old Xorg server version 1.20.14 even in Rawhide? Tumbleweed, Mageia 9 and Arch on 21.1.8, Bookworm 21.1.7.
This has absolutely nothing to do with Wayland or X11, both are affected by this (Wayland even more so because of other outstanding bugs)