bazzite
bazzite copied to clipboard
ublue-os
Desktop mode artifacts on Steam Deck OLED
Describe the bug
Desktop mode has weird artifacts (it's hard for me to explain). It happens most of the time but, what's curious to me, not always (on some boots, it's just okay). Here's a video of this:
https://youtu.be/9k3uq6hKn0I (please don't mind the audio issues, my microphone is currently broken)
What did you expect to happen?
I expected the bazzite to communicate with display properly.
Hardware
Steam Deck OLED
Extra information or context
This DOESN'T happen on steamos. The issue never occured to me when the desktop mode is on with the deck plugged to tv (I can't replicate the issue on external screen). (Obviously) I'm using gnome image.
I'm not layering any packages nor changing anything in the config. Not even in distrobox. Issue is present from fresh install.
Should be fixed soon, AMD Kernel bug.
Do you have any issue I can track or ETA when it will be fixed? Kernel changes can progress very slowly and while I can live without desktop mode, I would be happier having functional os
Same problem here. I also encounter heavily bitcrushed audio on Steam games (OBS does not record it but it is present with or without a headset) and gaming mode is barely functionning.
Same problem here. I also encounter heavily bitcrushed audio on Steam games (OBS does not record it but it is present with or without a headset) and gaming mode is barely functionning.
Audio issue is known, that is why we're not recommending OLED for most people right now.
Can you tell me more about the gaming mode issue? I've been playing games on mine all week and haven't come across anything like that.
Should be fixed soon, AMD Kernel bug.
Do you have any issue I can track or ETA when it will be fixed? Kernel changes can progress very slowly and while I can live without desktop mode, I would be happier having functional os
I don't at this time, there's a reason we're not recommending the OLED right now.
Audio issue is known, that is why we're not recommending OLED for most people right now.
No problem. I know what I was getting into. I'm happy to help solve problems.
Sorry, I'm don't speak english. In my next message, I will write without caring much about grammar and stuff...
#All of the pictures in this post are taken after a reboot of my steam deck OLED.
- Screen after rebooting
2. I click on Hollow Knight
3. Pressing B or the Steam button brings up the steam menu. Pressing the quick access menu button brings up the quick access menu. I can't click on anything on the steam menu. I can access everything on the quick access menu, except for decky loader that displays this error screen. If I reopen the quick access menu, decky isn't there anymore.
4. I click with the mouse or the touchpad on refresh, then I can go back in the home or in the settings (I noticed that the clicking sound of goings through games and stuff is gone, but not the other system sounds)
5. I click on Brawlhalla (same problem)
6. I can read news
7. I can access my library, the store, my media, etc...
- I did the system update and nothing changed (at least on gaming mode)
Good luck
Should be fixed soon, AMD Kernel bug.
Do you have any issue I can track or ETA when it will be fixed? Kernel changes can progress very slowly and while I can live without desktop mode, I would be happier having functional os
I don't at this time, there's a reason we're not recommending the OLED right now.
I completely understand. I may not know how things work but how exactly will it be fixed soon if no one even reported it yet? This may be a little digression from the issue but I genuinely don't understand what to expect here.
There's this issue: https://gitlab.freedesktop.org/drm/amd/-/issues/3361
Is this by any chance connected? Is it worth tracking this?
Issue seems to be solved with this addon:
https://addons.mozilla.org/en-US/firefox/addon/enhanced-h264ify/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search
That may be an issue with AV1 codec. I'm still testing it and will update if anything more comes up.
If someone could test with the latest Bazzite, and report back - we can then determine if this bug is still present. Thanks.
