SteamDeckHomebrew / decky-loader

A plugin loader for the Steam Deck.
https://decky.xyz
GNU General Public License v2.0
4.25k stars 154 forks source link

[BUG] Missing Decky Loader icon in QAM #640

Closed AkazaRenn closed 5 days ago

AkazaRenn commented 6 days ago

Please confirm

Bug Report Description

  1. Install the latest version of Steam Beta (ver. 1719420706 the one with Game Recording)
  2. Find that the Decky Loader icon is missing in QAM
  3. Note that the CSS plugin still functioned

Expected Behaviour

Decky Loader icon should appear in QAM

SteamOS version

SteamOS 3.6.7

Selected Update Channel

Prerelease

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

No

Backend Logs

deckylog.txt

Frontend Logs

cef_log.txt cef_log.previous.txt

AkazaRenn commented 6 days ago

https://deckthemes.com/themes/view?themeId=fa803fc3-a391-4cec-9721-7b6c33b13b74 This theme also stops working, might just be that they changed the class name.

dshk0718 commented 6 days ago

I was going to report this same issue.

Here are my logs:

Backend logs: plugin_loader.log

Frontend logs: cef_log.previous.txt cef_log.txt

Additionally, all the Decky plugins seem to have stopped working (with the exception of the CSS Loader plugin; probably because the CSS Loader plugin already injected the CSS?). For example, Audio Loader stopped playing background music and did not replace the default UI sounds.

lyndonguitar commented 6 days ago

Would like to report the same issue with mine. same version and all. However this is expected as this is a new beta update from Steam.

SubElement commented 6 days ago

Just wanted to chime in and say I’m experiencing the same issue.

PartyWumpus commented 6 days ago

Issue is being investigated, thank you all for your logs and for reporting this

AAGaming00 commented 5 days ago

Should be fixed in the latest prerelease, please test

lzq960605 commented 5 days ago

Should be fixed in the latest prerelease, please test

Fixed, testing completed

lzq960605 commented 5 days ago

You can close this issue now

SubElement commented 5 days ago

Should be fixed in the latest prerelease, please test

I can confirm this is fixed with 3.0.0pre1