Games in Steam return to Play Bazzite
Games in Steam return to "Play" - Bazzite Host (A thread)
134 Replies
Clean install of Bazzite (KDE) NVIDIA version.
Installed software and rebooted.
Steam games will let me click play and will look like they're going to load, then they return to the green "Play" button.
Are you running under Wayland? If so, try switching to X11
Currently yes, I will test that too.
Let me know how that works out for you
oh gadzooks everything is huge
I have had this even on steam OS if I don’t update for a while …
all of the settings look correct but everything is zoomed in too far lol
resolution is correct,
xrandr -s 0 didn't fix it.
the DPI is wayyy off lolThis happens switching between the two. I'd imagine scaling is off
the scaling is set to 100%
it's workable enough for me test steam again though
That's so weird
I can confirm the same "back to play" issue is happening in X11 too though.
Tested with Halo Infinite and Cyberpunk 2077. They're on different drives from each other so that shouldn't affect it.
BRB switching back to Wayland.
okay, so weird development
it just loaded Final Fantasy VI
and I'm thinkin,g okay, it's running on Integrated.
But nope, definitely running everything on the NVIDIA GPU
Grab a dump with PROTON_LOG=1
that's what I'm about to do! 🙂
well, now Discord is not letting me upload any files...
I think this is the relevant section:
yep, back to failing to create vulkan device for you
let me see what might be happening
Yeah, thanks.
Another issue is that by default it was set to 175% of display scaling in the integrated panel.
did you have an external display connected?
Yes
and KDE or GNOME?
KDE
ok, I'll have to add a workaround for that
only happens if an external display is connected
NP, just FYI
BTW, amazing work already <3
yeah, so in my case, the internal display of the laptop is 4K, so I disabled it in the OS, and was only using 2x external monitors, both 1080p, and that's when the scalling trouble started (on X11, not Wayland)
also @KyleGospo the Vulkaninfo IS showing up in settings.
hm?
interesting, and that's for the nvidia gpu?
yep, 1070, doesn't have switchable graphics so it's always on
and that one still fails the same way??
nvidia-smi shows up fine and shows processes running under it
correctGuh
What game were you launching?
I tried with Halo Infinite, Cyberpunk 2077, Borderlands 3
I was able to launch Final Fantasy VI
(the old pixelated one)
not a 32-bit vs 64-bit problem then
interesting..
does vkcube work and all that?
yep, spins like a top
what the heckin heck Crysis just launched
Let me think on this one
??
I am as confused as you are!
trying cyberpunk again... same problem...
I'm trying Steam Beta to see if that changes anything
First one is Cyberpunk, Second is Crysis Remastered
Halo MCC launches fine as well.
@KyleGospo this looks unrelated but:
ERROR: ld.so: object '/run/host/usr/lib/extest/libextest.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.Yeah that one's normal, steam is 32-bit and extest is as well
It'll throw that error on anything 64-bit steam loads after the fact
But that's not relevant since only steam needs it
Okay, that makes sense
That being there does mean my volume is working in distrobox though, so that's good
Yeah, not sure what would be causing this looking at the logs
Unless defining a volume somehow breaks nvidia mounting
But then it wouldn't be intermittent
Update: I can get Cyberpunk to launch to a black screen with no sound using these launch options:
PROTON_LOG=1 DXVK_ASYNC=1 PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr %command% -dx12 --launcher-skip
DXVK_ASYNC you can remove, that does nothing now
rest of that looks pretty standard nvidia stuff, interesting that fixes it somewhat
does this issue relate to this new nvidia driver issue? @turbwroan https://www.gamingonlinux.com/2023/08/recent-nvidia-drivers-are-causing-issues-for-proton/
GamingOnLinux
Recent NVIDIA drivers are causing issues for Proton
Have you been seeing some problems with the NVIDIA 535 driver series when trying to run Steam games on Linux with Proton? Well, you're not alone but investigations are under way. Here's what's happening.
idk how nvidia drivers work since ive switched to AMD 2 years ago
but this is supposedly a new issue with the 535 driver
nvidia
classic!
Interesting...could be related. Though Cyberpunk specifically wasn't launching with 7.6 or however the main version is numbered. It's not in front of me atm
Always improve themselves /s
I'm now downloading it on my other (Ubuntu) NVIDIA system to see if it launches properly there
Cyberpunk 2077 runs fine with experimental (on Wayland) if I pass
--launcher-skip but that's on the Ubuntu 23.04 machine.What Nvidia driver versions does Ubuntu 23.04 use?
Let me try to replicate this
Driver Version: 525.125.06 CUDA Version: 12.0
works on Proton 8.0-3 as well, just wanted to double-check that.
I can/will open a Github issue too, this just keeps not being what I expect is the problem lol
@KyleGospo Can replicate... Should we ship 530 until this is fixed?
yeah that's a good call
once again out here doing the heavy lifting so nvidia can keep fucking up
All right. I'll get a PR open
NVK can't come soon enough
No, it definitely can't
I just wanted to play Elden Ring ;_;
did this ever get fixed?
Not yet
Waiting on nvidia
thats insane loooool
i would be so angry if i couldnt run games just because i have to rely on closed source drivers on an OS where the other vendors have open source drivers
We'll see whether proton or NVIDIA fix it first, my money is on Proton
Assuming it's workaroundable.
Knowing their crap drivers.
Wouldn't be surprised if they said "Contact your vendor for guidance" /s
The Github issue made it sound like it might be workaround able
Yeah, AFAICR it seems just an address space problem.
But this remember me the same issue with DXVK and nVidia issues
Same story.
I'm not sure if it got fixed ever as of today.
It depends on how much control you have on it, after all.
As a reference: https://github.com/doitsujin/dxvk/issues/1100
GitHub
Games crash on Nvidia due to memory allocation failures · Issue #11...
For some reason it looks like DXVK's device memory allocation strategy does not work reliably on Nvidia GPUs. This leads to game crashes with the characteristic DxvkMemoryAllocator: Memory allo...
Seems to be closed now.
Update 3: Please update to driver version 440.59.
LOL
So, not really that workaroundable /s
7 months, it seems.
Better than nothing.
It looks like there's a new NVIDIA driver (non-beta) as of yesterday - v. 535.104.05
@KyleGospo if I wanted to test the newer driver version, what would be the best way to do that?
I have the .run file downloaded. But can't install it in the usual way since the file system is mounted read only.
would need to be updated in ublue-os/nvidia
and then I can kick off new nvidia builds of bazzite
no way to install manually
looks like @bsherman ran a build 2 hours ago
maybe w/ that version? Looking
looks like 535.98?
that's the version I'm currently on
checking what rpmfusion is providing
Latest Production Branch Version is 535.104.05 https://www.nvidia.com/en-us/drivers/unix/
Unix Drivers | NVIDIA
Unix Drivers
just for reference
that build didn't pickup a new nvidia driver... was just keeping foo-nvidia in sync with foo-main
doesn't look like new 535.104.05 is here yet
https://ohioix.mm.fcix.net/rpmfusion/nonfree/fedora/updates/38/x86_64/repoview/index.html
I mean the page said it only landed yesterday, so that's not super surprising
builds are in the pipeline https://koji.rpmfusion.org/koji/buildinfo?buildID=26624
https://koji.rpmfusion.org/koji/buildinfo?buildID=26602
so probably available soon
complete!
so by running
just update I'll get it eventually?I'll let you know when
much obliged
@KyleGospo any rough ETA on when the newer driver will be available? Also, do we still think this is the most likely cause, or is it more related to xdg?
Is this still a problem? I've been able to play games for about a week now
should be fixed, newest nvidia drivers are up
oh i forgot what thread this was, about to reference <#1144743760224329960>
today i couldnt launch the .desktop shortcut that bazzite-arch made. but running it thru the terminal inside the distrobox container worked
what did your desktop file have in it?
it's the one bazzite-arch makes and puts on the actual desktop hold on
that looks correct
run
/usr/bin/bazzite-steam-runtime in bazzite-arch
what happensoh let me exit steam first lol
seems normal
steam launched and everything
wtf
who knows... i tried it on my first boot earlier today
system, flatpak, and distrobox containers updated shortly after that
maybe it's now fixed
oh ok nvm
LOL yeah
so clicking steam from the desktop just makes it have a black screen that keeps opening and closing
but if i run it thru the terminal or do that command you just told me about, it's fine
interesting
that makes no sense
it's the same thing
yeah im confused here too lol
Exec=/usr/bin/distrobox-enter -n bazzite-arch -- bazzite-steam-runtime
bash: -n: command not found
i think thats a spacing issue lol hold on
bazzite-steam-runtime inside the container worked fine@nickname I forget, are you on an NVIDIA system?
Nope
AMD for both CPU and GPU
interesting.
I keep seeing this in the bazzite-arch terminal:
is that normal?
fossilize is shadercache stuff iirc
xdg-user-dir is interesting im not getting that either
i just get loads of extest errors lol
ERROR: ld.so: object '/usr/lib/extest/libextest.so'
but that's because it needs a fix from the devsJust tried to run Halo Infinite and got this:
let me run a game
i got none of those errors
nothing looks wrong here, try remaking your box
only failing to load gstreamer plugin
oh wait game im running is one of the few games to run better with openGL wine
share that one for me, might just be another dependency
i should mention that
haha ignore my SteamLibrary folder twice
that looks normal
okay
yeah i didnt notice any issues
game ran like it did on flatpak steam
steam & wine are very noisy
lots of entries that aren't errors
that say error/failed
so this is interesting...the Steam flatpak seems broken on my machine
How so?
When logging gets taken too far...
Meanwhile my day job is a framework that thinks a checkout preventing issue shouldn't be logged, or if it is provides no details of the actual source of the problem
I'll take the noisy logs any day
Lmao
I wouldn't want to be the person that had to fix that
I fixed it. But I'm not sure why it wasn't working. I uninstalled and reinstalled it via Discovery which kept throwing an error message and nothing happened when I clicked on the menu Entry for Steam. It loaded after I installed it manually via Terminal and removed the external drive permissions in Flatseal
Very strange
I'm taking "measures" and should have more data soon. lol
An appropriate emoji since I am metaphorically burning some things to the ground.
this happened to me too
it's the reason i rebased to bazzite
like a week ago
Okay, progress, Steam flatpak version is working, but I can't select my external drives from the in Steam storage dialogue, was this something we saw and fixed?
Nvm, found it in the Bazzite Help portal. Running
systemctl restart --user xdg-desktop-portal solved it.
so I was able to select the drives, but it's not detecting the games inside the SteamLibrary folders.you might have to choose "select another location"
and literally choose the SteamLibrary folder
and hope it doesn't complain about it not being empty
just steam things
I did that, I thought. Lol I'll try again!
oh LOL
wait
hmm does flatpak steam still require filesystem permissions?
for any secondary drives
or anything outside of the flatpak application data directory
you mean like these?
yeah....
the "COOL" part is that if I give it blanket access to the filesystem, the app doesn't load anymore.
okay it's not that
Isn't that great!?
but wait, there might be hope!
If I tell a game to install on the drive it's already installed on, it goes to "validating" instead of downloading.
Yeah that works
Just did that for every game that was previously on my deck
Idk why it can't just detect them, but it's a step in the right direction. I'll take it.
Ironically the
bazzite-arch version didn't have that problem, it just wouldn't launch games...
The real test is going to be if it can launch a game that's not on the internal drive in the flatpak folder.
The validations are ending in a disk-write error...
@KyleGospo @EyeCantCU
Update on NVIDIA testing with Bazzite
Testing on two systems:
1. System76 Oryx 1
CPU: 6th gen Intel i7
GPU: NVIDIA 980M
RAM: 16GB DDR4
2. System76 Oryx 3
CPU: 8th gen Intel i7
GPU: NVIDIA GTX 1070
RAM: 32GB DDR4
Both systems had clean installs done. Computer 1 more recently, Computer 2 has had some customizations and updates before this writing.
Expected Behavior:
Run Steam on bazzite-arch, install games, play games.
Actual Behavior:
Computer 1:
bazzite-arch distrobox fails to launch with OCI error (after an update and reboot).
What's odd about this is prior to the update, this was working fine. Halo Infinite launched and was playable. Of note, the game was installed on the same drive as the OS.
Now Steam will not launch at all, and nvidia-smi says it can't talk to the driver. Attempting another clean install.
Computer 2:
bazzite-arch launches, and games can be played, so long as they are on the same drive as the OS.
If games are on a secondary drive, they return to the "play" button.
I was having other drive issues (I/O errors and permissions issues) before this, so, to eliminate drive issues I backed up the contents of my secondary drives and formatted them. They are now btrfs and mount at /run/media/nathaniel/name-of-drive
Problem is not affected by running under Wayland or Xorg.
I'm happy to move this to github or to another thread, but figured I'd update here first.
Update: this seems to be resolved and may have been a drive mounting/permissions issue. Or other updates may have cleared it up.Really happy to hear that!