-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
[Bug]: Settings inaccessible #3594
Comments
happening to me too. @TheEvilSkeleton @mirkobrombin @jntesteves is a major regression. how did it pass testing? |
A possible workaround involves downloading some |
This comment was marked as off-topic.
This comment was marked as off-topic.
Important checks were removed... |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
I think the bigger problem is that it's trying to load things that aren't installed. |
I had the exact same problem. But why was NVAPI set in my case? I have an AMD and dont even use it. |
In my opinion... that's not the problem, as things like this can happen for various reasons(from corrupted files to moved bottle folders)... and the settings screen needs to be accessible regardless of anything(so... any error that could occur needs to be prevented). |
Emphasis on "the bigger problem". I apologize for being unclear; I didn't mean to dismiss the problem, rather I was stating that it's naively picking values when it shouldn't |
Closed by #3600 |
@TheEvilSkeleton @mirkobrombin thank you for fixing this! |
I still see blank screens in two Global Preferences tabs (the ones for managing runners and dll components) Maybe a 51.18 release is in order? |
Describe the bug
Settings page of a bottle is inaccessible using latest version
To Reproduce
Package
Flatpak from Flathub
Distribution
Manjaro KDE Plasma
Debugging Information
Troubleshooting Logs
Additional context
Last error message log line appears on 'Settings' click
The text was updated successfully, but these errors were encountered: