this post was submitted on 09 May 2026
10 points (100.0% liked)

Steam Hardware

22056 readers
847 users here now

A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Controller] - Steam Controller related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 4 years ago
MODERATORS
 

Has anyone had the css loader plugin for deckyloader make their QAM (quick access menu) not display properly? Some particular script (I don't know which one, or what would be the best way to narrow it down, because I installed several) made it where my QAM doesn't show. Functionally, it still works when I press the button, I can tell because the background blur effect still takes place and I can still navigate and change settings if I press the face buttons, but it's as if the menu display itself is invisible.

I was able to dig into the file system on desktop mode and delete the css folder (after copying it over to another location), and when I rebooted everything works fine again (sans css, of course)

I'm running Bazzite on a onexfly handheld, if that helps any.

Edit: in case anyone runs into this in the future, 'round main menu and QAM' was the script that caused the bug. You have to back out to the 'homebrew' folder where you will find another folder called 'themes' and that's where all the custom scripts you've installed will be located. You'll likely have to 'run as administrator' to do anything with the files. Just right click on a blank space inside the 'themes' folder and open/run as administrator should be an option. Type in your password and you should be good to go ('bazzite' would be the default password if you haven't set one up yet).

Edit 2: today I noticed I was having the issue again. I think the script I previously thought was the culprit actually wasn't. The new one that I tried removing is just called 'full screen menus'. So far so good, I'll come back and update again if the problem persists.

you are viewing a single comment's thread
view the rest of the comments
[–] Maiq@piefed.social 3 points 4 days ago (2 children)

The only things I can think of are starting steam in a terminal in desktop mode but I don't think you can access the QAM from desktop mode to test/trigger the css error if there is one.

The only thing I can really be sure that you can do to troubleshoot is disable all and reload one at a time till you find the problem.

I did see some settings in the developer options but since I'm not a dev i honestly don't know if any of those options would even help.

Might be able send each css file through a css online validator, might show an error somewhere.

[–] viral.vegabond@piefed.social 3 points 4 days ago (1 children)

Thanks for the comment.

If I were to try the 're-enable them one at a time' method how would I go about doing this? The only way I was able to get the QAM back was to delete the entire css plugin folder. I didn't really go into the folder to explore further though

[–] Maiq@piefed.social 4 points 4 days ago (1 children)

Are they just loose css files in a single folder without descriptive file names?

Might want to disable/uninstall any decky plugin that has anything to do with styling and reinstall them one at a time and testing. Thats probably a hell of alot easier than going through each css file.

I know it sucks as I have had to do this with hundreds of mods in skyrim/fo4 mods a few times.

[–] viral.vegabond@piefed.social 4 points 4 days ago (1 children)

I dug in a little deeper and found the problem. The one that was messing things up was called 'Round main menu and QAM,' coincidentally. The actual scripts were in a different folder which was called 'themes'

Thank you for the help!

[–] Maiq@piefed.social 3 points 4 days ago

Glad you got it sorted!

[–] Fubarberry@sopuli.xyz 3 points 4 days ago (1 children)

If you go into Big Picture mode in desktop, it's basically the regular deck UI, QAM menu included.

That said, you can also open steam console in game mode, and view any errors there. Go to Settings>Developer Menu>Misc>Steam Console. This will add a console item to the standard steam menu, that will show all console logs after adding the console. Then they should be able to open the QAM menu and see if any specific errors show up.

[–] viral.vegabond@piefed.social 3 points 4 days ago

Thanks for this information, that will be useful if I need to troubleshoot in the future.

The offending theme was 'round main menu and QAM.' After removing the folder everything works good again, and I still have all of my other customizations. I appreciate your help.