Skip to content
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] Decky / Plugins not loading correctly on Startup #697

Open
4 tasks done
CreeperofDoom opened this issue Sep 2, 2024 · 6 comments
Open
4 tasks done

[BUG] Decky / Plugins not loading correctly on Startup #697

CreeperofDoom opened this issue Sep 2, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@CreeperofDoom
Copy link

Please confirm

  • I have searched existing issues
  • This issue is not a duplicate of an existing one
  • I have checked the common issues section in the readme file
  • I have attached logs to this bug report (failure to include logs will mean your issue may not be responded to).

Bug Report Description

When booting my Steam Deck Decky Itself either doesn't load on Startup or one random plugin will show an Error on the bottom right. It's rare for these NOT to occur anymore. I cannot access Decky / Plugin Settings and Store as well

Expected Behaviour

For Decky Loader and the installed Plugins to load and function correctly

SteamOS version

3.5.7 Stable

Selected Update Channel

Stable

Have you modified the read-only filesystem at any point?

No

Backend Logs

deckylog.txt

Frontend Logs

cef_log.txt

@CreeperofDoom CreeperofDoom added the bug Something isn't working label Sep 2, 2024
@TrainDoctor
Copy link
Member

Unless you attach the CEF logs we cannot really debug what's going on here. The issue does not appear to be occurring in the backend as the logs show plugins loading properly. If you can recreate the behavior and provide the frontend cef logs then we are far more likely to be able to recreate and diagnose the issue.

@CreeperofDoom
Copy link
Author

cef_log.txt
cef_log.previous.txt
here they are.

@TrainDoctor
Copy link
Member

cef_log.txt cef_log.previous.txt here they are.

Can you provide a list of your installed plugins? I think you might be using some out of date or deprecated plugins.

@CreeperofDoom
Copy link
Author

All Plugins are up to date according to Decky itself. but:

Audio Loader
AutoFlatpaks
CSS Loader
Emuchievements
Playtime
SteamGridDB.

Mostly when turning on the Steam Deck one of the Plugins will error and so will Decky with it not functioning. Sometimes when booting the device it will work perfectly fine, All Plugins seem to be working when it does

@TrainDoctor
Copy link
Member

All Plugins are up to date according to Decky itself. but:

Audio Loader AutoFlatpaks CSS Loader Emuchievements Playtime SteamGridDB.

Mostly when turning on the Steam Deck one of the Plugins will error and so will Decky with it not functioning. Sometimes when booting the device it will work perfectly fine, All Plugins seem to be working when it does

As in none of these plugins are from the testing store?

Next time you have a plugin fail please capture the error it shows and grab the logs. The info you've provided should be pretty helpful but we need to catch it as it occurs in terms of logs.

@jurassicplayer
Copy link
Contributor

jurassicplayer commented Sep 6, 2024

Adding my logs here too for another reference.

This steamloopback.host-1725620236079.log is from a where everything worked as normal.

Decky-Loader v3.0.0-Pre12
SteamOS Beta v3.6.12 - build 20240905.101
SteamClient Stable v1721173382

I haven't spent a bunch of time reproducing the error, but it seems to occur due to DFL attempting to initialize Steam interfaces too early (seems to always be Navigation?). I've noticed that with lower initialization times reported by the DFL's Webpack Module Init, decky tends to hit the issue though it could just be coincidence. Out of the 7 times I've tried reproducing the error, webpack module initialization taking less than 50ms always seems to fail to get Navigation.
Timings that I've seen:

  • Failed to get Navigation: 36.4ms, 44.20ms, 39.30ms, 49ms, 47ms, 36.5ms
  • Obtained Navigation: 55.7ms

It may also be related to why plugins sometimes show the failure notification on start.

v3.0.0-Pre14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🆕 New
Development

No branches or pull requests

4 participants