I just put together my first dedicated Linux machine. Running Pop!_OS, and I’ve got a problem with Steam. I’ve tried installing it from the Pop Shop (i love that name), both the .deb and flatpak versions as well as sudo apt install steam. In both cases, when I open the app it will just blink at me. Like the window is trying to maximize but then minimizes before it can get that far. I made sure that all my drivers look good and was just playing Starfield, so I know it’s at least somewhat functional. What’s weird is that it launched once for me. Long enough to get signed in. But after a reboot, it will not open unless I type steam --reset from terminal. Then it opens just fine and acts like nothing happened. Of course if I close that terminal window, Steam closes. And if I don’t do a reset, it will go right back to flashing at me again.
I’ve also noticed that games show “Cloud Status: Unable to sync” in the app. The following games are installed currently:
- The Outer Worlds: Spacer’s Choice Edition
- Warhammer 40,000: Boltgun
- Starfield Premium edition All of these games show the cloud sync error. But when I checked the first two, the game save I had from my steam deck worked fine. But it still shows the error.
I tried opting into Beta to see if that might have some bleeding edge fix, nope. I’m still new to Linux and I’ll admit I’m not even sure where to look for Steam errors specifically to give more details.
Hardware (in case it helps):
- AMD Ryzen 5 7600X
- 32GB G.Skill Flare
- Gigabyte B650i Aurous ITX
- WD Black 1TB boot drive
- Samsung Evo Plus 2TB storage
- Cooler Master 850w gold SFX PSU
- XFX 6700XT 12GB
Any ideas on what I can try? Or where I can find logs to better understand? I asked in the Linux Gaming sub…lemmy? at least about the cloud sync, but got no traction.
This is an issue/bug with steam trying to open with the dGPU. In the steam.desktop file, change the PrefersDedicatedGPU (might not be exactly worded like this) parameter from true to false. Though after using this, you might have to use the DRI_PRIME=1 with your games to make them use the dGPU
Edit : credit for this goes to a kind gentleman who helped with the issue 2 months ago when the new steam UI dropped.
Yeah this is the reason most probably. After the UI update I had the exact same problem. After 2 days of search for solution I finally found it. When it tries to open with discrete GPU it just blinks and doesn’t open. I can only open it with integrated GPU. And you definitely have to use DRI_PRIME=1 argument for every game to open them with dGPU. It is kinda annoying but it’s only solution for now until Valve updates it.
And you definitely have to use DRI_PRIME=1 argument for every game to open them with dGPU.
In my case, I am on a amd+amd laptop and I don’t have to use the DRI_PRIME=1 argument to make the game use the dGPU. It just automatically uses the dGPU but I have seen others mention that they needed to use the argument.
I’ll have to try it without the argument to see. Do you mean you have an AMD single chip CPU/GPU? Like the APUs?
These are the two options in steam.desktop that I see. I’ve tried setting both, one at a time, and then both simulanteously. Rebooting in between each change. I still can only get it to launch once to sign in and then it just sits in the task tray with no response from any of the menu items other than exit. Am I adjusting the right file? It was the only one that came up in a system-wide search.
The line you are changing is the right one. Change the PrefersNonDefaultGPU option from true to false
https://lemmy.one/post/151466. Refer to this for the location of the file. This is for the native .deb package
Well this is frustrating… I changed it as referenced in your other thread and it still will not work. Since this is a new computer, it was no big loss to format the drive and start with a fresh install. But this time I installed EndeavorOS, since it’s not Ubuntu-based like Pop. Then installed Steam and opened it to login. Then closed it, reopened, repeatedly to see if I could replicate the issue. Nope. It works fine on EndeavorOS. Nothing against that OS in general, but Pop is a much better fit for me. So I formatted the drive once again and did a fresh install of Pop instead. I then installed the .deb package from Pop Shop and before even launching the app for the first time I edited steam.desktop and switched PrefersDedicateGPU to false. It won’t launch at all now. Before it would launch once to let me login and I could even install and play games. But once I closed the app it was right back to the flashy business. Looks like I’ll need to try to get some help from Valve and/or System76 on this one. So strange!
Well, I was cautiously optimistic. I removed the .deb version and installed the flatpak version. I was able to launch it and sign in. I was about to try installing a game when I remembered I hadn’t turned on Proton and all that mess, which requires steam to restart. Now instead of just flashing at me I get the Steam “waiting for network” screen, then the icon appears in the task bar (idk if that’s what it’s called in Linux, but in Pop, this is the top right corner where volume, network, etc is). But the favorited icon in the dock doesn’t show the little dot under it like normal open apps would show. If I click on the task bar item, I get the menu, but it’s all unresponsive other than Exit.
I forgot to mention in my original post but this issue persisted through a reimage of the boot drive. That’s not why I reimaged, but pretty alarming that it would stick around through a full reinstall of the OS.
Not sure how to help with this but as a temporary workaround you can append an “&” after the command to make it run even after the terminal is closed. Should look like steam --restart .
Try closing steam entirely before closing the terminal.
Just tried and it’s the same thing. I don’t know why I didn’t think about Linux being any different when it was “closed” vs actually closed.
Is it still in your system tray when you close steam though? Mine doesn’t like to fully exit that way. If so then it isn’t exiting cleanly, you could have bad data getting read the next time you open it.
