I recently got the Deck and installed everything, it went great. However, I apparently made the mistake of updating SteamOS before Decky got an update.
Now I can’t access certain settings and it will give me some error and have to restart.
Do I just have to wait until Decky gets an update or… having to reinstall?
The latest SteamOS update did break Decky quite a bit.
So, I’ve been looking into this for myself and it looks like what’s broken is the MagicPods module in deckyloader. If you previously installed that, you can try uninstalling decky and then re-installing it and leave that module out of the reinstall/setup process and see if that works.
At this point I’m gonna leave decky uninstalled on my system mostly because I’m pretty tired of it breaking.
Don’t think I have that installed. The plugins I have installed are;
- EmuDeck
- SteamGridDB
- CheatDeck
- CSS loader
- PlayTime
- PauseGames*
Did you try uninstalling and reinstalling?
Also, perhaps just checking for updates? When I checked for updates I could see that there was a new update for decky loader but at that point I had decided to uninstall it anyway to prevent future problems.
Haven’t tried reinstalling yet but I have tried;
- Changing from stable to pre-release and back to stable (since it didn’t change anything).
- Checking for updates but already was on the latest (3.20).
Don’t think I’ll reinstall because it would mean also reinstalling the plugins (bit lazy for that). I’ll probably wait it out until there’s an update.
Uninstalling allowed grub to boot Bazzite normally with no errors for me so right now that’s maybe the best we can hope for. I also don’t want to re-install all my plugins.
you can run the installer again to either redownload the latest stable or their beta version, which might fix your issue, you can also uninstall decky this way, should the issues persist.
Thanks, I will try redownloading it!
If you’re on steamOS beta/steam client beta, you have to also be on the pre release version of decky (you can select this when running the decky installer).
Even then, new updates to the deck/client can break decky and extensions. Decky will usually be updated to fix any broken updates within a day or so, but plugins can be broken much longer before they get an update. You’ll often find that you have to uninstall a specific plugin for a couple weeks.
Anyways if you want decky to work pretty smoothly, I’d suggest sticking to stable. If you don’t mind some troubleshooting and brief down periods, you can make it work on beta. I’d recommend getting on the Steam Deck Homebrew discord server so that whenever something breaks you can easily find out why and what you need to do about it.
I’m on stable version of SteamOS and I assume stable version of Decky. It happened after updating SteamOS. Reading here and there, I’ll just need to wait this out.
Thank you for the discord server but I’m a bit bummed out that they force verification by phone number. I’m very cautious and suspicious about that kind of stuff. I joined it but won’t be chatting, I suppose.
That’s fair. I’m surprised you’re still having crashes on stable though, it might be worth updating to pre-release and see if that fixes it.
There were several plugins that broke awhile back with Steam client changes, I know at least SteamGridDB, MagicBlack, Brightness Bar all broke, and I think one about managing airpods broke too. I know SteamGridDB is working again, but I haven’t gotten around to reinstalling the other ones yet. The SteamGridDB fix specifically required a decky update and not an update to the plugin to fix, so hopefully the other plugins are all fixed on the pre-release build of decky as well.
I used Decky in the past and it was NOT recommended to have Steam (client) Beta enabled. That was a deal breaker for me. Not sure if this is still the case. Do you happen to use Steam Beta (note Steam itself, not Decky).
I normally have to go in (uninstall just deckloader), and reinstall deckyloader when this happens. There’s no way that I have found to do it otherwise and it’s happened to me at least three times now.
I’m sure there probably is another way, but I haven’t had success with anything but the uninstall/reinstall method.
