screen artifacts in gamescope-session on the V3
An odd screen artifact is showing up for me on my Minisforum V3 after updating to the latest bazzite. It only affects gamescope-session, it disappears on desktop mode.
I think I've seen some ROG Ally X users report a similar issue previously, so perhaps it's related to VRR screens.
I updated from 07/23 to 07/28
edit: workarounds below, any of these should work:
- suspend-resume cycle makes it go away
- restart steam client also makes it go away
- reboot device
- rollback to 07/22 OS version
129 Replies
I'll check the 07/26 and 07/25 images to see if the issues are there too
@Kyle Gospo I’m going to spin up a vanilla Gamescope rpm on copr for testing situations like this, with the amount of patches we have it’s going to get hard to narrow down upstream issues or patch issues.
or other issues entirely
also it looks similar to that dude with the Ally x who thought it was a hardware thing
present on 07/26
for to replicate the bug, you need to go back and forth between desktop + gamescope-session at least once
ok, not present on 07/23
accidentally skipped 07/25, let me check it now
@Kyle Gospo confirmed 07/25 introduced the bug
so last known good image is 07/23
nice, Ill revert gamescope for now
I don't know if this will be the same for the Ally X
for anybody who has this issue, temp workaround is for to rollback + reboot to 07/22
bazzite-rollback-helper rebase 40-stable-20240722
note that this will lock you to the 07/22 bazzite version.
If you want to resume regular OS updates in the future once bugs are fixed, run:
bazzite-rollback-helper rebase stable@PubisDeciusMons
Oh yeah that’s the exact same thing. I finally don’t feel like the only person to have seen a UFO anymore!!
is that on the version aru said to rebase to until gamescope is reverted
How do i see the version?
rpm-ostree status
you can use the commands aru mentioned to easily rebase to older versions and back to stable once the problem is fixedYep i can confirm I have the 7/28 version
rebase to 7/23
bazzite-rollback-helper rebase 40-stable-20240723
it will lock you to 7/23 until you rebase back to stableOK and that command locks it so it won't auto update to 7/28
yep
aru confirmed that version isnt affected
aru is testing reverting gamescope atm i believe so next stable release might have it solved
ok just reboot is ok or does it need hard power off/turn back on
Got it, rebooted and hopefully all good! Thanks you guys are absolutely top notch!
could you swap between game mode and desktop mode a few times, and see if the bug pops up or not?
sure
just to be clear when i was experiencing that bug, it would come and go in spurts. For example if it happened, it could be repeated consistently multiple times. Then hours later or the next day, i could switch back and forth without the bug occurring, only for it to pop again. so it was always intermittent.
for me it always pops up after swapping between desktop and game mode at least once
i was wondering if it was the same on the Ally X
Ok, so switched it 2x and the problem did not recur. However everything is running a bit sluggishly as it re-verifies the steam installation and stuff - i assume that is normal for awhile after rolling back.
aight, let us know if you run into the problem again, or other problems.
Will do. This was the single most noticeable/scariest issue, everything I've had feels like the garden variety minor bug that gets fixed in future updates type.
Have you noticed that gaming mode is running extremely slowly after roll-back? like i just fired up Baldurs Gate 3 and it's taken 10 minutes and it still hasn't finished "processing Vulkan shaders". When I ran it the first time it took less than 2 min to finish the initial load/startup process before going into the game.
you can generally skip vulkan shader processing nowadays
there's been improvements in the kernel for AMD GPUs that basically makes the shader processing optional for most games
are you noticing long load times for everything though? if gaming mode is this slow throughout i might just go back to 7/28 and live in Gaming mode without switching to desktop until a new stable version comes out that fixes the gamescope bug.
let me try real quick, gimme a few mins
ok, so it took me a bunch of tries, but artifacting popped up for me on 07/23
which means the bug was introduced earlier
Argh
Looks like the slow performance issue is resolved by rebooting a 2nd time after the inital reboot into 7/23
I'm guessing that it's best to just leave my Ally X in 7/23, live in gaming mode, until the bug is fixed. Sounds like you guys are not far along from fixing it anyway.
that'd be the easiest for you, yeah
and tbh, there is the off chance that the bug I'm encountering is different from yours
since I'm seeing this on my minisforum V3 tablet
i suspect they're the same though, considering how my tablet also has a VRR screen
too much of a coincidence that both your Ally X and my V3 tablet have the same issue
my bug happens when its not connected to a monitor as well as when it is
Does the OG Ally NOT have a VRR screen?
yep, it does
strangely enough, no reports of this bug from OG Ally users
I didn't notice it happening until after I connected it to my external monitor. Maybe that's some sort of a trigger. But once it starts it will happen when the device is on its own.
i'm about to test bazzite version 07/12
let's see how it goes
🤔 Initial ROG Ally X support was added later I think, so unfortunately older Bazzite versions might not be possible to use on the Ally X
That's ok, antheas kind of convinced me that it's ok to live in Gaming mode for awhile as most people are not flipping back and forth between gaming and desk top mode.
I frequently do b/c i use the device as a laptop lite, and I can only stream youtube/netflix etc in desktop mode
you could add your browser directly to game mode, or heck, you can even add desktop as an app to game mode (see nested desktop)
Hmm i see i still have much to learn lol
ok, 07/22 tentatively seems good so far. i'm going to test it more thoroughly this time
so far, can't replicate the issue on 07/22
on 07/23 i was able to replicate it, but it took a lot of attempts
on 07/25 and later, it was trivially easy to reproduce on my device
but i'll keep testing 07/22
@PubisDeciusMons have you seen the issue at all since rolling back?
nope, not once. however i will add that i have been switching to desktop much less than when i was trying to troubleshoot that and other issues. i have probably switched back and forth maybe 6 or 7 times since the 30th.
aight, danke for the update 🙂
as an fyi, it seems that a suspned-resume cycle also clears out the artifacting
or restarting steam (believe you need to have developer mode enabled in gamemode to see that option)
Yeah I figured out early on that sleeping then resuming will clear the artifacts. Anything that turns the screen off will clear it.
I assume there is still a fix expected in the next update?
Tbh I'm not sure we even know what's causing the artifacting, so not sure?
Interesting... earlier someone said it was a likely Gamescope issue or some such but now maybe it is less clear?
We suspect it's a gamescope issue, but tbh we're not completely sure.
Another artifacting report: https://discord.com/channels/1072614816579063828/1087140957096517672/1269454103155576913
another artifact report: https://discord.com/channels/1072614816579063828/1271966821523656734
another report of the issue: https://discord.com/channels/1072614816579063828/1087140957096517672/1271996259812769842 this is a LGO attached to a non-VRR external monitor
My display connected to my machine was also a non-VRR display. I'm starting to see a pattern that the issue only occurs to AMD handhelds and systems that use similar hardware as said handhelds...
I had initially thought it was just VRR devices since the initial reports were on the Minisforum V3 and ROG Ally X
but now that there's reports of it on non-VRR, it seems to be something else
i've rolled back to 07/22 for now on my V3, haven't seen it since.
anyway gamescope version can be rolled back in the latest stable until this is resolved?
We're not sure it's gamescope
yeah, we don't know where the bug is coming from
To add a tiny "something" that may or may not help, but I suppose the more info tue better. The square artifact brightens in game mode when the onscreen mouse dissappears once you stop moving it around.
when the mouse is visible gamescope is compositing, so different render path
explains the brightness change
does mean that artifact is in a layer that gamescope renders
Figured that was the case, but didn't know enough to put it in those words 👍
@Kyle Gospo is there an environment variable you know of to force compositing off? i wouldnt mind seeing artifact in gamemode, my issue is im seeing it inside of games like ghost of tsushima, though admittedly its not a square, its more like the entire lower half of the screen artifacts, but only in the menu. The artifact scrolls up and down the lower half of the screen in my case. If there is a way to try turning off compositing on a per game basis, i can give that a try to see if it fixes the problem im seeing
you can't
no compositing, no cursor, no mangohud, no overlay
oh i get you, thats what you meant by layers
depending on gpu you should be able to get scan-out by disabling hdr while keeping mangohud and the overlay. the cursor + hdr are what make amd gpus start compositing usually.
but you need the qr debugger squares to tell for sure
just a quick update that i have not yet seen this artifact again since reverting to the older version of Bazzite. It is definitely rarer on the older version.
I can also confirm that I have yet to see it on 07/22
so something changed that started introducing the artifacting bug, we just don't know what it is
same here, ghost of tsushima is fine on 7/22
No issues on 7/22 either
for anybody that ran into the artifacting issue, can you try running the latest testing build and see if you can replicate it?
bazzite-rollback-helper rebase testingbet i'll try rn
Switched between desktop to gaming mode 10 times and not once has the artifacting appeared
Did it a dozen more times and as far as I can tell, theres no artifacting anymore!
that'll land on stable tomorrow night
wow was that really it 😭
What black magic did yall do
Tested earlier, but fell asleep! Testing on Legion Go, on a non-VRR 1080p monitor at 60hz, 15 attempts to go back and forth from desktop to gaming, no artifacts occurred.
Repeated on roommates 4k vrr 144hz monitor 5 times, no artifacting occurred. 👍
(Even did 3 or 4 tests o. Legion Go native screen on the device itself, no external monitors, no artifacts, but that was never an issue. )
Thanks for testing and confirming 🙂
Once the bug fix is released, you can go back to stable with
bazzite-rollback-helper rebase stableWhomever the code monkey was that figured it out, thank you!
wow so is this fix live now? i can just roll back to stable with the command you posted?
works for me now thanks
Issue randomly came back for me on the deck stable image
Sorry for the bump don't know if I should just open a new post
thanks for the followup. Probably better to keep tracking it here
did any of the workarounds work to clear it out? e.g. a suspend-resume cycle
Well I have suspend disabled on this machine (desktop PC with a 6700XT) but restarting steam sometimes works
ah, so this is on a desktop? interesting
there was another report of this here: https://discord.com/channels/1072614816579063828/1279199295085613137
so i guess the bug is still around
perhaps just harder to trigger it
Yeah fwiw I noticed moving the mouse cursor temporary makes the corrupt graphic disappear
But it comes back as soon as the mouse cursor auto hides
Edit: just saw this was already mentioned
Fwiw I have vrr enabled in steam settings and my tv
Fwiw
This is my device info
https://paste.centos.org/view/0a1c7d8b
if you see the issue again, just in case, could you post gamescope logs?
ujust post-gamescope-logs
i doubt the gamescope logs will provide any more insight, but doesn't hurt to have it just in caseArgh 😤 now that I WANT it to happen I can't reproduce it 😂
I'll try running that next time I see it
I did see it briefly on one attempt and then it went away as soon as steam fully loaded
welcome to software debugging :clueless:
so just to document zany's device info, since the fpaste will expire
reporduced it but wasn't abel to get anything usefull from the gamesope logs
why is it looking in root :thonk:
those log paths should be from $HOME
maybe its because when I ran
ujust post-gamescope-logs it asked me to re run as root so i did let me run it without rootseems like a script error then or something, idk. probably needs root for those first fields and then continues to look in root afterwards
but the logs should exist in your home
yup had to run it as my user now it shows the logs https://paste.centos.org/view/f8dc2b76
btw this is the output I got saying to run as root
hmm, maybe doesn’t like the juggling between connectors in your case. not sure. sounds like a scan-out issue. in your case, it’ll most likely go away if you enable Developer settings and enable Force Composition
the mouse “fixing” it for you is because Gamescope starts compositing
it could very well be that.
I use a HDMI -> DP adapter to get around the lack of HDMI 2.1 and gamescope REALLY doesn't like that for some reason. Sometimes it will fail to output and I will have to switch between tty and/or poweroff and then power on my tv. (fully by either unpluging it or I have a app on the tv which forces a reboot)
Point is I think when I most noticed the corrupt graphics issue is when I am also haveing that issue.
when I reboot my tv gamescope momentalry goes to my other display (i have 3) and when it comes back on my tv thats when i am seeing the corrupt graphic I think
You should check if trying to reduce the monitor resolution via the Gamescope system display menu has any effect
Or TV in your case
I’m hitting a different bug with VRR right now that has quite a few conditional factors
One is a certain resolution and hz being exceeded
hrm, that ujust script should not require root
Yeah I'll try .
What makes this harder to test though is the instability of the connection to the TV when using gamescope session
Any change in display settings can cause my tv to have a fit and not display anything
Until I forcefully reboot the TV
Like I said I do notice the corrupt graphic more when I am having the display issue but idk if it's a coincidence
Got the issue again seems like the log got some more stuff this time
https://paste.centos.org/view/6c9f5f18
Interestingly lowering the resolution to 1080p 60 gets rid of the graphic going back to 4k 120 it shows up again
Also shows up on 4k 60
So looks like it only happens on higher resolutions like 4k
turn on composite debug in developer settings and check both of those resolutions, I’ll bet 4K is when it starts compositing and you’ll see squares in the top left corner while 1080p uses scanout
but it’s the first time I would be hearing of this happening and not the reverse of this :thonk:
And can you take a picture or something?
This is at 4k composite debug is enabled and isn't showing anything on the top left
Interesting, good to know
This is at 1080 and again it doesn't look like it's composting
If I move the mouse I see the white squares on the top left though at both resolutions
yeah that’s normal
if you use a cursor Gamescope always starts compositing
Interesting at 1440p I get a line instead of a square
What about disabling color management in dev settings? It’s normal for it to look super dark with the setting just fyi
Just makes the square darker porb doesn't show to well in the picture but the red is less vivid
hmmmm
I’m really not sure tbh :/ bazzite seems to be the only place I’ve ever seen people with this specific issue
bit of a Hail Mary but are you using the custom bazzite game mode intro video or the normal steamos one
Well I shuffle through several including the bazzite one
On this particular boot I think I got the turret factory from the points shop
I also use the custom decky vids
yeah I’m out of ideas here, without a way to reliably reproduce this on other setups I’m not sure what else there might be for me to try. Sorry.
no worries. it looks like a really hard to repoduce bug . I just randomly got agai today after a few days of not seeing it (and I was going back and forth between desktop and gamemode these past few days)
but restarting the steam client is a quick fix
also forcing compositon in steam dev settings work
I’ve had scan out issues at higher resolutions somewhat similar to this but they’re always transient, ie pop up for .5 seconds and then go away
Never persistent
And also reproable
I’d be inclined to say driver issue at this point but then you’d expect it to always be broken
on the latest steam stable I can 100% always reproduce this if I have HDR enabled
Restarting the steam client or going to sleep then waking up does not fix it
Reddit
From the Bazzite community on Reddit: Strange phantom menu keeps po...
Explore this post and more from the Bazzite community
More screen artifacts 😵
I really hope it could be fixed because I was having issue on my Ally X when I used VRR on Bazzite few days ago.
does the suspend-resume workaround work for you? a suspend-resume cycle should clear out the artifact
I’ve still literally never seen this in Gamescope before on any rig running any OS so I’d be cautious in saying its definitely a Gamescope memory corruption issue
what should we tell them
when I get some time I’ll try to install bazzite and check, but this is almost certainly going to be some bazzite tweak that gets made
all i know is it was not me
hehe
they want to move sunshine builds to COPR so I need to reinstall Fedora anyway
Huh interesting just realized hiding the performance overlay gets rid of the issue
Re-enabling the overlay causes the corrupt graphic again
Who is "they"?
ah the actual sunshine maintainers
unrelated to this issue lol
interesting that it only happens with the overlay in use
Still present on the Ally X when returning to gaming mode from Desktop
This still does the trick
I’ve been unable to repro this so far :dispair:
Fresh install, switching from desktop to game mode repeatedly
am I missing any steps? Still nothing yet
I’ve tested repeatedly both with HDR (no direct scan-out) and without HDR
We might be on a slightly older version of MangoHUD at this time, I will try updating it.
But I haven't been able to reproduce this either...
I’m on testing atm with mangohud set to preset 4 and to show in the steam menu
also using the bazzite Steam loading theme since that was one of my initial guesses for what might be going wrong
Me and Mr Dante have it, we both are on a 8845h
we sadly cannot suspend. closing the laptops lid completely turns off the os
just got screen artifacts on latest testing branch.
LG OLED TV
5600x + 6700xt
no ryzenadj used on this system, which rules that out
suspend-resume cycle cleared it out
Do you have a custom animation set when resuming or no
everything default that comes with bazzite