-
Notifications
You must be signed in to change notification settings - Fork 56
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
Decky Loader plugins have mixed compatability #203
Comments
Decky loader plugins that don't have python backends like |
The |
So I did a bit more digging. Decky loader didn't appear to have any detailed logging so I forked it and added the fork as an overlay. This let me discover that it isn't a global problem, but a series of problems with different plugins. Storage ControlIt tries to report the size of steam files here. It uses Vibrant DeckVibrant Deck fails with errors, being unable to find Should I start putting some documentation together on which plugins work and what the workarounds are if any? |
I also wonder if |
Does appending the bin path of xorg.xprop to the PATH in the decky-loader script work? |
VibrantDeck is fundamentally a hack and should not be used, use Steam's native color management which is more correct. |
Hey K900, while that may be true, I was more proposing putting together a document detailing what decky-loader plugins work, and what, if any work-arounds are required for them. The entry for vibrant deck could be "Don't use it, use the native colour management instead" and would save people time trying to get it to work. Further more it appears that injecting new packages into PATH via the |
here is how I handle the deckyloader mess |
Adding plugin-specific details / hints in Something like a sub-section Each plugin section should start stating “information accurate as of YYYY-MM-DD”, and updated as information gets updated. Would that seem appropriate? |
Any decky loader plugin functionality backed by a python script doesn't appear to work at all, with the only hint of errors in the
deck-loader
service at startup.In particular this line
The text was updated successfully, but these errors were encountered: