Open DylanRJohnston-FZ opened 9 months ago
Decky loader plugins that don't have python backends like HLTB
work just fine.
The CEF
console within Decky-Loader's developer tools is full of errors about being unable to connect to a websocket which appears to be the main way Decky-Loader's front-end communicates with its backend https://github.com/SteamDeckHomebrew/decky-loader/blob/44e6f03b0655a9f1e87530141ad907b9553744cc/backend/src/plugin.py#L163.
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.
It tries to report the size of steam files here. It uses environ["HOME"]
which is set up by decky-loader
here. Based on this, you can fix it by changing the decky-loader user to your username e.g. dylanj
.
Vibrant Deck fails with errors, being unable to find xprop
, I've tried adding xorg.xprop
to the extraPackages
option in the decky-loader module, and while this does get correctly written to the service definition in /etc/systemd/system/decky-loader.service
, for some reason it's not in the PATH when I look via htop. Something in-between must be modifying the PATH of the process.
Should I start putting some documentation together on which plugins work and what the workarounds are if any?
I also wonder if decky-loader
upstream would welcome a DEBUG logging mode to help make tracking down these problems a lot easier.
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 extraPackages
configuration option is not functioning correctly as something else is setting the PATH for the systemd service.
here is how I handle the deckyloader mess https://github.com/Cloudef/nixos-flake/blob/master/modules/steamdeck-experience.nix#L65-L103
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