-
Notifications
You must be signed in to change notification settings - Fork 55
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 frontend fails to load #387
Comments
Ugh, Steam caches that, and I guess the output is no longer deterministic. Try clearing the CEF cache, and we'll need a better solution... |
Tried removing |
Hmm, maybe we should just patch Decky to blow out the cache then... |
One thing maybe worth mentioning is that it seems that it's the Decky backend requesting that chunk from the frotend, which as I understand is the only part being built differently now, so maybe there's where that mismatch happens? At least it feels like the issue isn't really tied with the Steam client itself as much. |
No, it's Steam requesting it. |
They are not CEF cache, cef cache is located at |
Oh, awesome, that worked just fine! Thanks a ton, seems like a good workaround for the time being. |
Adding the bug/TODO labels assuming we should be doing what was said previously, and that it's the way forward to close this bug. |
Possibly related to changes from #386, Decky frontend now builds with different chunk.js files, which makes the frontend of the plugin (tab in QAM and its configuration) fail to load.
The backend along with decky plugins still load fine, but configuration UI is inaccessible as a whole.
NixOS + nixpkgs: unstable
00d80d13810dbfea8ab4ed1009b09100cca86ba8
(1/7/2024)System flake: https://github.com/Faupi/nixos-configs/tree/79231cc1dac3af2249b72ded53c3c0d4a6e772f4/nixos/cfgs/go
Hardware: Lenovo Legion Go
Logs of decky loader service:
To see if it was an issue with the mentioned PR, I checked the older cached build I still had on my system:
Older build (pre-386, you can still see the
chunk-6238f864.js
mentioned as not found in traceback):New build (post-386):
The text was updated successfully, but these errors were encountered: