Hello @cirruszoi, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
I had the same issue. Disabling the iGPU fixed it for me.
I have the exact same issue, although using an AMD card (RX 6800XT)
Officially, Valve states that the .deb from steampowered.com or the Flatpak are the only supported versions of Steam. The packaged version on rpm-fusion is made by a 3rd party and valve has no control over what dependencies are bundled.
Please retest with the flatpak version of steam and attempt to reproduce. Or install Ubuntu LTS as the Readme on this repo suggests.
I have the exact same issue, although using an AMD card (RX 6800XT)
I managed to figure this issue out. Apparently, my upgrade from fedora 42 to 43 was broken with the packages themselves getting upgraded, but their repos were set to unknown. Specific to my case, the steam package from rpm-fusion was freshly installed, but the related drivers were still shown as belonging to unknown. Reinstalling them fixed the issue.
You can list the broken packages with sudo dnf list --installed | grep unknown and reinstall the broken packages (or remove them)
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/12422#issuecomment-3508288849
This is valuable information which states the issue is related to the Operating System, the Fedora upgrade process, and the associated dependencies that Steam relies on. Perhaps the best course of action would be to report this issue to the Steam package maintainer for rpm-fusion and/or Redhat in some capacity - since they package and distribute Fedora.
@cirruszoi in light of what @SilverArrow009 has outlined, are you still seeking assistance from the Steam community?
Apparently, my upgrade from fedora 42 to 43 was broken with the packages themselves getting upgraded, but their repos were set to
unknown.
No, the repo being <unknown> is not a sign of broken packages. I have almost 2000 out of 3500 packages with unknown repo on my F41 install. There are various reasons for it (e.g. https://github.com/rpm-software-management/dnf5/issues/1379) but it is harmless.
but the related drivers were still shown as belonging to unknown. Reinstalling them fixed the issue.
@SilverArrow009 If you think that specific packages are broken in F42 to F43 upgrade, please report to Fedora. There is a known issue with wine but not any other packages. Without knowing the suspected packages, it's impossible to guess what went wrong.
Replying to [#12422 (comment)](https://github.com/ValveSoftware/steam-for-linux/issues/12422#issuecomment-3508288849)
This is valuable information which states the issue is related to the Operating System, the Fedora upgrade process, and the associated dependencies that Steam relies on. Perhaps the best course of action would be to report this issue to the Steam package maintainer for rpm-fusion and/or Redhat in some capacity - since they package and distribute Fedora.
@cirruszoi in light of what @SilverArrow009 has outlined, are you still seeking assistance from the Steam community?
If you do not believe the issue is in the Linux steam client itself. I was never trying to receive assistance, but report on behavior that appeared to be a bug or at least an issue. I found how to work around it, but I wanted to make sure that it was reported on somewhere so other people could also report and find the workaround if needed. Through my searches I did not find any other people reporting on this same issue at the time I reported it.
It appears no one really knows the underlying cause of the bug, but it seems people believe it falls in the RPM Fusion relm of things rather than the client itself. I'll probably throw something over there just to make sure someone on that side of things is tracking.
but it seems people believe it falls in the RPM Fusion relm of things rather than the client itself
It most likely isn't the RPMFusion steam package, which doesn't change between F42 and F43, and is only a bootstrapper for client updated from Valve's side.
It could be some other Fedora/RPMFusion package. We don't know which packages @SilverArrow009 reinstalled that they claim fixed the problem. As mentioned there is a known issue with wine-core during F42 to F43 upgrade, but not any other packages.
In general, reinstalling packages should not fix issues because it should result in an identical state before and after (if not, it suggests there is something non-deterministic about the install process, and all installs cannot be trusted to be correct).
I would ignore the comments by truefakts/LuminousHustler, who appear to be the same person or group targeting the same issues with long-winded, irrelevant "triaging".
@cirruszoi I believe this is the same issue:
Possible workarounds:
https://discussion.fedoraproject.org/t/bug-report-fedora-43-causes-black-screens-in-most-proton-games/171578/4
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/12422#issuecomment-3509640331
I wasn't meaning the repos pointing to unknown were broken, it's actually otherwise (i.e, the broken packages had their repo named unknown). I know for a fact that they broke because I was trying to upgrade from 42 to 43 and my pc basically didn't reboot for 1hr. I had to manually shut it off and get a half baked system where the packages were all upgraded to their 43 version counterparts, but dnf showing that its repos are still from fedora 42. To state the fact, I didn't even get the GUI. I had to manually sort that mess, which is unrelated to this issue. If you knowingly have unknown repos on your machine, that is totally valid and is not a broken package, but that wasn't intended in my case.
I only realized that my upgrade was "broken" when I tried launching steam, in which case I got the same error as OP, but with an AMD card, I thought the issue might be similar. but when I saw a lot of packages tagged unknown, which is not what I expected, I simply reinstalled them. Now, I don't actually know how and why, but only that it worked in my case.
I only posted that to make it easy for the maintainers to see that my issue was totally unrelated to the one OP has and for anyone with similar problems as mine, might find useful. If it is helpful to remove my comments since they were causing confusion, I'd happily remove them :)
TLDR: My problem is now solved and it is unrelated to the one OP posted (OP's card is Nvidia, I have AMD). RPM fusion version of steam works flawlessly on AMD cards. If you feel my comments were distracting, feel free to remove them :)
Confirming this on a second system, though slightly different GPU and driver build. Also sorry if I am a little late to the party.
System information
GpuTopology output (Fedora 43)
Running query: 1 - GpuTopology
Response: gpu_topology {
gpus {
id: 1
name: "AMD Ryzen 9 7900X3D 12-Core Processor (RADV RAPHAEL_MENDOCINO)"
vram_size_bytes: 11245047808
driver_id: k_EGpuDriverId_MesaRadv
driver_version_major: 25
driver_version_minor: 3
driver_version_patch: 6
luid: 0
}
default_gpu_id: 1
}
Exit code: 0
Saving response to: /tmp/steamAopBMh - 88 bytes
Very similar to the original report: iGPU only, dGPU and llvmpipe both absent. Host-side vulkaninfo enumerates the 3090 Ti correctly, and the Steam UI reports it correctly under System Information, however it's only the per-game launch path that fails.
Other affected titles include Baldur's Gate 3, The Last of Us Part I, Grim Dawn, Tiny Glade. Tiny Glade's in-game "select graphics card" picker offers the iGPU as the only option, which is a useful quick check.
Symptoms vary, BG3 and Grim Dawn render a black screen with a working cursor, audio and input. TLOU Part I shows a white screen and I believe audio as well - in that the underlying game is in fact running, and gets to the opening menu. Lots of VK_ERROR_INITIALIZATION_FAILED on swapchain creation errors in Vulkan logs for each game.
VK_LOADER_DRIVERS_SELECT=nvidia resolves it on a per-game basis. Post-workaround the same TLOU log shows zero VK_ERROR_INITIALIZATION_FAILED and three "Found device: NVIDIA GeForce RTX 3090 Ti" lines.
Two other things I tried that did not work, in case they help: __VK_LAYER_NV_optimus=NVIDIA_only had no effect at all, and
DXVK_FILTER_DEVICE_NAME matched zero adapters and produced "Failed to create rendering device".
Other affected titles [...] Symptoms vary
All games should be affected; specific symptoms in games aren't really relevant since you already know the root problem is that they're running on the iGPU.
Did you try changing the desktop file? See https://github.com/ValveSoftware/steam-for-linux/issues/12422#issuecomment-3512784890
Ultimately this is a problem with the ambiguous desktop spec. #9940
I don't know what's the status in KDE to fix (work around) this ambiguity, since this issue is still open but last updated 2024 https://bugs.kde.org/show_bug.cgi?id=480797
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Immediately after upgrading my system to Fedora 43, I noticed that the vulkan drivers were not matching to my NVIDIA GPU when trying to launch games in Proton. Specifically I was hitting the error
Driver "nvidia_icd.x86_64.json" ignored because not selected by env var 'VK_LOADER_DRIVERS_SELECT'. This happened for every VK_LOADER_DRIVER, including all available NVIDIA drivers. This would cause my games to render a black screen or throw errors and not launch as it would fall back to the AMD iGPU Vulkan loader.This can be fixed by manually setting it in the launch options as
VK_LOADER_DRIVERS_SELECT=*nvidia*which does allow my games to launch as normal. This was not the case before, previously it would launch with my NVIDIA discrete card automatically.I looked back at my previous
console-linux.txtlogs I noticed that theGpuTopologyscript was previously detecting my GPU and now is not (Output shown below). The only change to my system was the Fedora 43 upgrade. I am pretty sure this is what was causing the VK_LOADER_DRIVERS_SELECT error above but I am not familiar with how the script works and how permissions / upgrade nuances could change the GpuTopology behavior.Another detail is that the Steam Client itself recognizes my GPU in the UI, it is only when I launch games and the
GpuTopologyscript is run that it fails to detect the GPU.The "System Information" UI element shows:
I thought it would be worth reporting as I have not seen something about this yet and Fedora 43 was just released. If this seems to fall outside of the Steam Client, let me know where this issue could be falling so I can report it elsewhere.
Previous GpuTopology output (Fedora 42)
Current GpuTopology Output (Fedora 43 after upgrade)
Steps for reproducing this issue: