protonscr

After some applying configurations to stop NVIDIA GPU from flickering, steam won't open by .desktop file

steamclosed
ValveSoftware/steam-for-linux#9252 · opened 2023-03-11 by msmafra · updated 2023-03-11 · 2 comments · github
Mmsmafra 2023-03-11 github

Your system information

OS: Fedora release 37 (Thirty Seven) x86_64
Host: 82CF LENOVO LEGION 5I-15IMH
Kernel: 6.2.2-cbl1.0.fc37.x86_64
Resolution: 1920x1080, 1920x1080
DE: GNOME 43.3
WM: Mutter
WM Theme: Adwaita
Theme: adw-gtk3-dark [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: tilix
CPU: Intel i7-10750H (12) @ 5.000GHz
GPU: Intel CometLake-H GT2 [UHD Graphics]
GPU: NVIDIA GeForce RTX 2060 Mobile
Memory: 6503MiB / 15866MiB

  • Steam client version (build number or date):
  • Distribution (e.g. Ubuntu):
  • Opted into Steam client beta?: [Yes/No]
  • Have you checked for system updates?: [Yes/No]

Please describe your issue in as much detail as possible:

When I manually configure some nvidia.conf files to avoid screen flickering, Steam flatpak won't open via its .desktop file, but will if I run flatpak run com.valvesoftware.com. Doing that it will work, but very rarely and randomly out of nowhere it will sometimes start games in the iGPU instead of dGPU.
Checking the log when I click the on the .desktop file in the dock:

...
2023-03-10T19:47:49-0300 tars systemd[4974]: Started app-gnome-com.valvesoftware.Steam-66838.scope - Application launched by gnome-shell.
2023-03-10T19:47:49-0300 tars systemd[4974]: Started app-flatpak-com.valvesoftware.Steam-66838.scope.
2023-03-10T19:47:49-0300 tars com.valvesoftware.Steam.desktop[66851]: INFO:root:https://github.com/flathub/com.valvesoftware.Steam/wiki
2023-03-10T19:47:49-0300 tars com.valvesoftware.Steam.desktop[66851]: INFO:root:Will set XDG dirs prefix to /home/marcelo/.var/app/com.valvesoftware.Steam
2023-03-10T19:47:49-0300 tars com.valvesoftware.Steam.desktop[66851]: DEBUG:root:Checking input devices permissions
2023-03-10T19:47:49-0300 tars com.valvesoftware.Steam.desktop[66851]: INFO:root:Overriding TZ to America/Sao_Paulo
2023-03-10T19:47:49-0300 tars com.valvesoftware.Steam.desktop[66851]: DEBUG:root:Addding /usr/lib/extensions/vulkan/vkBasalt/bin to PATH
2023-03-10T19:47:49-0300 tars com.valvesoftware.Steam.desktop[66851]: DEBUG:root:Addding /usr/lib/extensions/vulkan/MangoHud/bin to PATH
2023-03-10T19:47:50-0300 tars com.valvesoftware.Steam.desktop[66851]: steam.sh[2]: Running Steam on org.freedesktop.platform 22.08 64-bit
2023-03-10T19:47:50-0300 tars com.valvesoftware.Steam.desktop[66851]: steam.sh[2]: STEAM_RUNTIME is enabled automatically
2023-03-10T19:47:50-0300 tars com.valvesoftware.Steam.desktop[66926]: setup.sh[77]: Steam runtime environment up-to-date!
2023-03-10T19:47:50-0300 tars com.valvesoftware.Steam.desktop[66851]: steam.sh[2]: Steam client's requirements are satisfied
...

It will get stuck and I'll have to kill the processes.
I completely removed steam flatpak, used rm on the com.valvesoftware.Steam folder after the uninstall. While writing it I tested with Steam installed via DNF, and it also happens.
NVIDIA Driver Version: 525.89.02 now, but I had it happen with previous ones.

Steps for reproducing this issue:

  1. Changes these files:
 ❯ cat /etc/modprobe.d/nvidia.conf
# Enable DynamicPwerManagement
# http://download.nvidia.com/XFree86/Linux-x86_64/440.31/README/dynamicpowermanagement.html
options nvidia NVreg_DynamicPowerManagement=0x03
options nvidia_drm modeset=1

❯ cat /etc/X11/xorg.conf.d/10-nvidia.conf
Section "OutputClass"
	Identifier "nvidia"
	MatchDriver "nvidia-drm"
	Driver "nvidia"
	Option "AllowEmptyInitialConfiguration"
	Option "SLI" "Auto"
	Option "BaseMosaic" "on"
	Option "PrimaryGPU" "yes"
EndSection

Section "ServerLayout"
	Identifier "layout"
	Option "AllowNVIDIAGPUScreens"
EndSection

# this one probably not related, but as I changed it...
❯ cat /etc/dracut.conf.d/nvidia.conf
add_drivers+=" nvidia nvidia_modeset nvidia_drm "
install_items+=" /etc/modprobe.d/nvidia.conf 

  1. Restart;
  2. Open Steam flatpak via its .desktop file on the dock;
Kkisak-valve maintainer 2023-03-11 github

Hello @msmafra, you've described the issue being tracked at #8179. Closing in favor of the older issue report.

Mmsmafra 2023-03-11 github

Oh! Thanks. I was not sure how to search for that.

Nothing extracted yet.