V1.2.0 blank description

[steamgriddb]

V1.2.0 blank description

[doZennn]

What version of decky-loader are you on?

[craigz]

• Decky Loader Version: 2.6.2
• Decky Update Channel: Stable
• Plugin Store Channel: Default

[doZennn]

Please post the log located here ~/homebrew/logs/decky-steamgriddb/plugin.log

[ManedCalico]

I'm having the same experience after updating. I also tried uninstalling/reinstalling 1.2.0, but the result was the same.

I can provide my log as well, if having two would be helpful. Let me know, thanks!

[craigz]

I performed some actions in the working version 1.1.1 (changed a game's capsule image) in hopes of seeing something write to the log file, but it did not. I'd then uninstalled 1.1.1 and shut down & restarted the steam deck. After reboot i then installed v1.2.0 and walked thru the same steps as initially reported, with the same results (nothing in the plug-in info pane and nothing loading after selecting 'Change Artwork'). I tried the 'reload' plugin action from decky loader and repeated the initial actions, with again identical results.

After that i uninstalled 1.2.0 and reinstalled 1.1.1 and following the same path, viewed the plugin info page and then again changed a game's capsule image.

I then grabbed another copy of the logfile but they appear to be identical. i've attached the latest, although other than load/unload there isn't much there, perhaps it has greater meaning that i am aware of 🤷
plugin.log

[doZennn]

I can provide my log as well, if having two would be helpful. Let me know, thanks!

Yes please!

[peaceful-octopus]

I experienced this on the initial installation (this is the first plugin I've installed for Decky) but after rebooting my Deck it works properly.

[craigz]

Having just seen @peaceful-octopus comment, i updated the (working) 1.1.1 install to 1.2.0 then shutdown the steam deck. After booting back up everything again works as expected. I've changed the capsule image for the same game i used as a test subject yesterday, via both methods. From the main library window as well as by finding 'change artwork' in the settings option on the detail page selected from the library.

rebooting is the cure! (so far.)

[doZennn]

Anything new in the logs for either of you?

[craigz]

@doZennn nothing new although there are new entries and the timestamp has updated, but the content remains a batch of

• [INFO]: Attempting to unload with plugin SteamGridDB's "_unload" function.
• [INFO]: Unloaded SteamGridDB

WIth the latest 3 lines all being [INFO]: Unloaded SteamGridDB.

[peaceful-octopus]

My log is completely empty.

[reconbot]

Just installed for the first time with the latest everything same issue

[doZennn]

I'm going to need plugin loader service log right after installing the plugin (and confirming its broken):

sudo journalctl -u plugin_loader.service > loader.log

[ManedCalico]

Hi @doZennn!

I have three logs for you.

Log 1 is after updating from 1.1.1 to 1.2.0. The plugin was broken both after the update and after generating the log in Desktop Mode and returning to Gaming Mode:
loader_1.log

Log 2 is after uninstalling 1.2.0 and reinstalling it through the plugin storefront. It was also still broken both before and after creating the log:
loader_2.log

Log 3 is after a restart. The plugin is working now after the restart and also after coming back to Gaming Mode:
loader_3.log

Hope this helps, thanks!

Edit: forgot to mention that these were all exported using the Konsole method in your last post, rather than the SGDB plugin log in the homebrew folder.

[doZennn]

Thanks, looks like this was a Decky issue. Should be fixed if you install the new 2.6.3 that just released.

[reconbot]

I don't have anything setup to get my logs off my steamdeck but I see the same exceptions as loader_1.log

[NBOOK]

Thanks, looks like this was a Decky issue. Should be fixed if you install the new 2.6.3 that just released.

Hello, I'm using 1.2.4 and decky loader v2.7.0. I'm having exactly the same issue. Could you please kindly confirm it?

---

Update: after checking the log I saw a bunch of "permission denied" errors, so I gave 777 to the homebrew folder and did a reboot. Problem solved! Although I haven't figured out what exactly the problem is but obviously it has something to do with the permission...