[Framework 16 dGPU] Steam window crashing in a loop
I've just updated bazzite to the latest stable version (41.20250314 (2025-03-14T08:02:55Z)). Compared to my previous version (41.20250301.1 (2025-03-03T05:05:01Z)) I'm now unable to launch steam.
When loading, the tray icon loads successfully, but the main window renders black, then crashes. After the crash, it tries again, looping.
When running
bazzite-steam from the terminal, this behaviour only seems to occur when using the dGPU, with DRI_PRIME=1. Is this a known issue?21 Replies
Looking into this
Unfortunately I am not able to reproduce this on my framework 16
Try resetting steam with
ujust fix-reset-steam
This will not harm your games or save filesRunning that command gets it running on the iGPU. Once again, launching it from the taskbar or with ‘DRI_PRIME=1’ causes the black window looping issue
I rolled back to (41.20250301.1 (2025-03-03T05:05:01Z)) and it resolved the issue. Definitely something wrong that’s happened between then and now.
I am also experiencing this
yes, i can replicate this as well with
DRI_PRIME=1 and DRI_PRIME=0.
additionally this affects the steam.desktop file because of the following options
PrefersNonDefaultGPU=true
X-KDE-RunOnDiscreteGpu=true
the temporary workaround is to launch from the terminalI'm having this same problem on my asus laptop. Opening the system monitor reveals steam trying to use 25% of cpu.
this makes steam run on the iGPU though
This is true, but you should be able to launch your games with the params
DRI_PRIME=1 as part of the launch option
But I'll admit I haven't thoroughly testedYeah that should work fine. I'm just gonna stick to rolled-back myself 😅
just updating that I tried
ujust fix-reset-steam and it didn't work for me either@Kyle Gospo Given that this issue is now affecting multiple users, any chance of looking again? Or alternatively, what diagnostics could I provide to help diagnose?
just out of curiosity, @Fenaer which batch were you? I half-wonder how many of my issues are because I was batch 1
the device I actually received might've been a batch 2 or 3 tho, due to issues
I was batch 3. I’ve seen a lot of the problems from early batches in the forums but I haven’t taken the time to benchmark my thermals etc.
luckily I have benchmarked my thermals and they're a-ok. My original device from Batch 1 had bad thermals though
Batch 9 here, I don't think it's a batch issue
That's a relief at least. I get paranoid 😅
Another report of the same issue
https://discord.com/channels/1072614816579063828/1355146451734495232
What is the difference between running 'steam' and 'bazzite-steam'? When I am trying to figure out when a cloud upload is stuck or some other steam issue I run 'steam' to see what the log is saying and didn't even know 'bazzite-steam' was a thing. Checking my autostarts it is using bazzite-steam however.
I am not using DRI_PRIME at all and when I am on the desktop with steam in the task tray my 7700S is using 1 watt and iGPU is using ~15 watt. When I launch a game the 7700S is engaged using ~98 watts. I thought DRI_PRIME has not been necessary for a while now and checking just now still does not seem necessary unless I am missing something.
So if you use the launcher, it will select your GPU by default. bazzite-steam is probly a bash script or smth
Might even just have the GPU selector stuff in the desktop file instead
But I don't think bazzite steam is the problem, since running DRI_PRIME=1 steam also doesn't work
Another instance of the same issue
https://discord.com/channels/1072614816579063828/1355870376252539050
from testing, there is no difference (for reproducing this bug) between
steam and bazzite-steam it's only the dGPU being used
@Fenaer can you see if this works for you too? https://discord.com/channels/1072614816579063828/1355870376252539050/1356008042344349808
I think I got it working