Skip to content

Remove PrefersNonDefaultGPU from desktop file #5405

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Jan200101
Copy link

Agreement

By creating a pull request in stk-code, you hereby agree to dual-license your contribution as
GNU General Public License version 3 or any later version and
Mozilla Public License version 2 or any later version.

This includes your previous contribution(s) under the same name of contributor.

PrefersNonDefaultGPU is currently very broken, see ValveSoftware/steam-for-linux#9940

@qwertychouskie
Copy link
Contributor

I agree that it's somewhat broken by design, but removing it would break STK on more systems. Laptops with a dual-GPU setup are much more common than desktops with a dual-GPU setup. Until a better mechanism exists, this should remain.

@Jan200101
Copy link
Author

I disagree, most CPUs these days have a GPU integrated, combined with a full dedicated GPU you run into this issue.

@Jan200101
Copy link
Author

it might also be worth noting that the Fedora maintainer of the stk package has decided to patch the key out to address a bug report

https://src.fedoraproject.org/rpms/supertuxkart/c/8e143f6cd414e7f9559565f920a9b30b72cfc452?branch=rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=2346005

@Alayan-stk-2
Copy link
Collaborator

The entire design of this setting is appalling. It's a pick your poison situation...

@Jan200101
Copy link
Author

the right solution to this would be to fix the issue itself instead of trying to remove the key, however my patches have thus far not gone anywhere
https://gitlab.freedesktop.org/hadess/switcheroo-control/-/merge_requests/69

on the off-chance you know anyone that can help with this it might be worth sharing this with them
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/5PUGDWKQJQ7LZNAUXAINVITTNWWGZKN7/

@Alayan-stk-2
Copy link
Collaborator

the right solution to this would be to fix the issue itself instead of trying to remove the key, however my patches have thus far not gone anywhere

That would be the best outcome indeed

on the off-chance you know anyone that can help with this it might be worth sharing this with them

I don't have such contacts unfortunately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants