Most of Steam is a black screen
Steam shows as a black screen on the main app view, all elements seem to be clickable and sub-menus seem to display fine
22 Replies
Hmmm. If you have an Nvidia GPU and are in Wayland, try X11. Also what version of Bazzite are you running? (Please run
rpm-ostree status in the terminal to see this information)State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
Diff: 1 upgraded
LayeredPackages: fontawesome-fonts libvirt powerline powerline-fonts ruby ruby-devel sunshine tmux-powerline vim-powerline virt-manager
zsh
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
LayeredPackages: fontawesome-fonts libvirt powerline powerline-fonts ruby ruby-devel sunshine tmux-powerline vim-powerline virt-manager
zsh
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
LayeredPackages: fontawesome-fonts powerline powerline-fonts ruby ruby-devel sunshine tmux-powerline vim-powerline zsh
Operating System: Bazzite 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-301.fsync.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700KF
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
Manufacturer: ASUS
Was previously working, could installing libvirt or virt-manager have possibly collided with any other packages/configurations?
It's possible I guess. It does look like you have an updated deployment, check if your issue persists after a reboot
Do updates only apply if I do systemctl reboot, and not a reboot from the launcher?
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
LayeredPackages: fontawesome-fonts libvirt powerline powerline-fonts ruby ruby-devel sunshine tmux-powerline vim-powerline virt-manager
zsh
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
LayeredPackages: fontawesome-fonts libvirt powerline powerline-fonts ruby ruby-devel sunshine tmux-powerline vim-powerline virt-manager
zsh
issue still persists
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
LayeredPackages: fontawesome-fonts powerline powerline-fonts ruby ruby-devel sunshine tmux-powerline vim-powerline zsh
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
LayeredPackages: fontawesome-fonts libvirt powerline powerline-fonts ruby ruby-devel sunshine tmux-powerline vim-powerline virt-manager
zsh
uninstalled libvirt and virt-manager, issue still persists
When did you start having the issue? Maybe you can try a rollback
I think just since yesterday. spent a lot of time trying to troubleshoot getting a midi controller working
it seems the flatpak version of steam is able to render fine
If the flatpak works properly, stick with that for a bit. Or do weird things break in the flatpak?
no, I should be fine switching to this version
Would be nice knowing what is causing the issue though. Maybe try the other one in a few days and see if it works or not
Not an issue if not possible, but is there a way to link the games I have installed to the flatpak version would you know?
ln -s /var/home/$USER/.local/share/Steam/steamapps /var/home/$USER/.var/app/com.valvesoftware.Steam/.steam/steamapps testing it out at the momentNo worries, thank you for the help!
Pleasure. Note that you can move the game from /var/home/$USER/.local/share/Steam/steamapps to /var/home/$USER/.var/app/com.valvesoftware.Steam/.steam/steam/steamapps and if you launch it then it will verify and play (without redownloading) but if you link it you get a steam write error. If you give it access to your home folder you get another error so yeah... the linking is a bad idea
Also experiencing this myself.
Not sure if it was the cause but I did setup Emudeck beforehand, though did run an update as well and did not immediately notice this happening until today.
Running on the nvidia image on x11
Flatpak is also showing up black screen, but I am pretty sure I have the flatpak version of steam symlinked to use the same paths as the regular steam package do, which suggests this is probably being caused by a configuration issue rather then an issue with the package itself
yeah can confirm it is a configuration issue, as upon backing up my old settings and letting steam open with defaults, everything is now working fine, for both the bazzite installed package and flatpak
which strongly suggests to me it was likely emudeck that screwed something up, as it was thew only thing I have done recently that missed with steams setup. Will try to reproduce
hmm I wasnt able to reproduce it , so not sure what missed with the configs besides maybe the update
It might be a combination of installing software that adds items to the steam folder combined with a steam update. 🤷♂️
Hmmm so I was able to fix my original directory by copying over my registry.vdf file in "$HOME/.steam/" from the newly generated one
Or at least it working now anyways
Pretty sure it is at least one of the files in "$HOME/.steam/", since all the directories in there are just symlinks and would not be different between my new and old .steam directories.
I am also having this issue, I did not install anything new from when the issue started, merely updated
here is my rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:d75357ed9559a569d5e0bf30706a1211bbe89db06cc64c225faf98da9131c377
Version: 40.20240517.0 (2024-05-17T17:07:48Z)
LayeredPackages: chntpw
LocalPackages: logmein-hamachi-2.1.0.203-1.x86_64
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:ff79f785d7eeaf6023d7db29a03d84f098617e3261870811954fc89655b841c7
Version: 40.20240514.0 (2024-05-17T04:38:49Z)
LayeredPackages: chntpw
LocalPackages: logmein-hamachi-2.1.0.203-1.x86_64
I had this problem, for me the fix was to turn off the hardware accelerated web views in steam (Settings --> Interface --> Enable GPU accelerated rendering in web views: Set this to disable.) - This only affected me in x11, as I switched back to it from Wayland (GPU is nvidia... and that's kinda broken)
Had this issue as well, make sure the compositor is running on X11 otherwise it will be blank.
ah so just cant use wayland with nvidia still, very cool :\ is there any hope int he future or should I just look to sell my card for AMD (Also having problems running steam on wayland/nvidia
This fixed it!
i suspect this is to do with the x11+kde openGL compositor problem that should be fixed upstream in f40 shortly