-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New steam UI does not open if run with DRI_PRIME=1 #9383
Comments
can you test
|
This works fine from flatpak sandbox with same runtime as Steam |
Hello @koresh-krasa, please copy your system information from Steam ( Blind guess that this is related to https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19101. |
Since I'm also seeing the same behavior, I figured I'd provide my own system information. But due to #9398, I cannot 😞 |
@kisak-valve System information from stable client DRI_PRIME=1 was working before this update. Also similar behavior was present with new gamepadui before (similar to #9190) |
@kisak-valve I see 2 issues here:
Solving issue 2 is pretty easy, just remove the options from the desktop file. I've sent a PR to fix that in the Flatpak package for now, until it's removed upstream: flathub/com.valvesoftware.Steam/pull/1086 |
Re-reading this issue report, it should be noted that the common case where |
Not sure if I necessarily executed the above workaround correctly, but I could not get it to work. What I was able to do was run Steam from the terminal with the argument My setup is Ubuntu 20.04 with Steam installed via the .deb package from here and I am opted into the Steam Beta releases. |
Hello @TimTheOverlord, with regards to this issue report, running |
Hey all, I'm sure you guys are all still cracking at it either way, but I just wanted to mention there's a specific use case for users deliberately launching steam under the DRM_PRIME=1 variable. https://help.steampowered.com/en/faqs/view/145A-FE54-F37B-278A |
I have no clue what
'v-gui' argument is the only way to get Steam to launch for me as well. 'DRI_PRIME' and modifying 'PrefersNonDefaultGPU=true' do absolutely nothing |
@Candyhands @TimTheOverlord are you guys by any chance using KDE or one of the other Qt-based DEs? If that's the case, besides removing Note that this test might require a logoff/login or a reboot because DEs often have trouble live reloading |
Can confirm that changing
|
I have done this, and no dice. I'm on xfce, so it's gtk based rather than qt based. Running 'steam-runtime --reset' fixed the problem for me, but only for once launch. When I closed it, I couldn't open it back up. |
Same problem here, with DRI_PRIME=1, steamwebhelper chash. OS: Fedora release 38 (Thirty Eight) x86_64 |
Removing |
this happened to me, after restarting. Steam would show a balck window and close it, repeatedly, not being able to show my library. Launching from console worked OK. What worked for me is that I noticed that my iGPU (the one that comes with the CPU) was suddenly enabled after a restart. Disabling it, as it was at the moment of installation of Steam, fixed everything. |
After @perroboc 's comment, I checked the BIOS and my iGPU was enabled as well (Ryzen 9 7950X3D). Just disable the stupid thing, and you are good to go without any modifications. |
Lot of comments here so apologies if this has been said before, but I found a fix. If you can find a way to launch steam that works (for me launching it from console with the |
Well, it appears that changing the two lines in the Steam setup to: PrefersNonDefaultGPU=false Well, now it works only once and then quits for good. Steam will not open. I have no idea why. Perhaps it's the new update for Linux Mint, Steam, or both. I have no idea... In short, the Panel Icon for Steam will not work right. Also, the start menu application shortcut for Steam does not work either... Thankfully, I can still get it to work by typing in "Steam" in the terminal, clicking the Steam desktop icon, or by right-clicking the Steam icon on the Panel and selecting "Settings." It will not open any other way (at least none that I know about). Ay-ya-ya-ya-yai. Such a rigmarole trying to get Steam to work on Linux Mint, you know? Uffda... :( It seems over time, Steam wants us to use their program less and less. I don't know why. A lot of us don't wanna switch to Ubuntu to run Steam. Plus, from what I've heard, some people are even having problems on there as well... Even "Minigalaxy" (which is basically the Linux version for GOG Galaxy) does not have any issues opening up... |
This seems to be a solution for me, as for now. But sometimes the issue comes back and the client remains invisible. So I hope this is more of a permanent solution. At least until it is properly fixed Unfortunenately the problem came back. |
I wrote a script that automates setting up a workaround for this. You can find it here: https://gist.github.com/major-gnuisance/4fad491e37c5ac7efa72f9473d4e95bd It sets up a shim script that adds the -cef-disable-gpu flag when the DRI_PRIME environment variable is set and installs a modified steam.desktop to use it. |
Hear, hear! Ideally, Steam itself would always prefer to use the default GPU, to conserve power, and help the user manage GPU preferences for games. I'd suggest adding a "default GPU" setting, looking something like this:
With an option to override the selection on a per-game basis, much like it works with Proton. See the output of |
Yes! This is the only thing that fixed it for me, on Fedora 40 KDE Plasma 6. I removed the variables from the desktop file, but it only worked once I also turned this off. |
Got a solution, not sure if this has already been posted, but I have a feeling that this is indeed a problem on valves end. This started happening on my version of Kubuntu 24.04. Steam launched with an update pending, after the update, I completely lost the steam window and it would only launch from the terminal or by executing the launch script from the bin folder. This is my fix in Kubuntu 24.04 Locate Steam.desktop (typically located in /usr/share/applications/ -or- /home/YourUsername/.local/share/applications/) (repeat this step for wherever you have the steam.desktop located) This was able to fix my issue. |
yep fixed it for me as well |
guys, nothing work for me, i am in kde plasma 6 in manjaro stable, with RTX 4070 in WAYLAND, What things i've tried? there is the list:
These solutions not work for me could please something help me? |
What CPU are you using? |
CPU: Intel i5-14500 (20) @ 5.000GHz |
You need to disable your iGPU in the BIOS. That's the permanent solution. |
It not a solution for me, I need work with my GPU and use it for passthrought in many situations I was playing for a long time this way. my iGPU loads kde plasma and my steam games use my nvidia card, it was always working in the past without any problems.. there is no reason to change it, it is a steam error, steam should open as it normally did. |
what's the output from this? |
this
|
are you sure your problem is the same as in this issue? from the arch wiki, Finding missing runtime libraries, could you please share the output from this command? $ cd ~/.steam/root/ubuntu12_32
$ file * | grep ELF | cut -d: -f1 | LD_LIBRARY_PATH=. xargs ldd | grep 'not found' | sort | uniq and make sure you [re]install required libs. I remember when I used Arch I had to do something similar: pacman -S lib32-fontconfig lib32-freetype2 lib32-gdk-pixbuf2 lib32-gtk2 lib32-libice lib32-libnm lib32-libpulse lib32-sdl2 lib32-libva lib32-libvdpau lib32-libudev0-shim lib32-openal lib32-libsm |
Thank u very much bro, it apparently works well, after install and run your command for search file, it dont found errors, and now I've installared my steam beta and works. NOTE IT WORK ONLY IF I RUN STEAM WITH THIS:
Thank uuu bro !!!! If the error occurs again I will let you know. |
Currently still an issue, however I need Steam to launch with the dGPU in specific circumstances, like when using VR. If the Steam client is launched with the iGPU but you launch SteamVR with the dGPU (for example when using ALVR), you get this garbled mess. Launching games still works fine (as long as you run them with DRI_PRIME=1) so it's not a showstopper, just a bit annoying. |
Your system information
Please describe your issue in as much detail as possible:
Similar symptoms as #9381
Login prompt displayed correctly but than main window tries to appear but crashes and goes into loop.
This issue is happening if DRI_PRIME is set to non 0 (e.g. DRI_PRIME=1, DRI_PRIME=pci-0000_03_00_0) DRI_PRIME=0 works fine.
In journalctl I was able to find some error logs related to steamwebhelper crash.
steam_journalctl.txt
Optput from
DRI_PRIME=1 com.valvesoftware.Steam
steam_output.txt
Steam client is flatpak
System information:
https://gist.github.com/koresh-krasa/b9a7a4c486ff061b9823aea6ce44f65b
DRI_PRIME=1 was working before this update
Steps for reproducing this issue:
Screencast from 2023-04-28 11-23-06.webm
The text was updated successfully, but these errors were encountered: