ashuntu
commented
1 year ago Does switching Nvidia driver versions help?
Closed UnrealisticDino closed 10 months ago
ashuntu
commented
1 year ago Does switching Nvidia driver versions help?
UnrealisticDino
commented
1 year ago I tried the 525 drivers and had the same issue. Trying to install the 530 drivers automatically upgrades to the 535 drivers. I used the additional drivers app to switch back and also used sudo apt purge nvidia* then reinstalled both 525 then 535.
ashuntu
commented
1 year ago I can't reproduce any bad behavior on my machine, I have NVIDIA 525. I personally have never had much luck using the bleeding edge NVIDIA drivers, but since you tried 525 I'm not sure what the issue is. Although, I know at one point only NVIDIA 515 would work for me, but 525 works at present.
It may be worth trying different gaming-graphics-core22 (stable) branches, but I can't promise much there.
@ZoopOTheGoop, I know you have NVIDIA, can you reproduce anything?
UnrealisticDino
commented
1 year ago I had to use sudo snap remove --purge steam to uninstall steam. 1.0.0.7.6 latest/edge seems to work but 1.0.0.76 latest/stable and 1.0.0.75 latest/beta didn't work. this did start after the nvidia 535 driver update but I have no idea why it broke and why it slowly stopped working. Might just do a reinstall of ubuntu.
kenvandine
commented
1 year ago I had a similar issue on my hybrid graphics system (Quadro T2000). When I installed Lunar I got the 525 driver, and had the issue and downgrading to 515 worked. Others couldn't reproduce the issue on 525. I recently got upgraded from 515 to 535 and I ran into this issue again. And now the 515 driver isn't available anymore. I'm going to try downgrading to the 470 to see if it helps.
kenvandine
commented
1 year ago This is due to lack of 32 nvidia driver on the host system. You need to enable i386 support and install the appropriate
sudo dpkg --add-architecture i386 && sudo apt updateThen install the appropriate i386 driver package. For example, the 535 driver is libnvidia-gl-535:i386
sudo apt install libnvidia-gl-535:i386 We need to detect the lack of this at start time and guide users to enable this.
UnrealisticDino
commented
1 year ago I used sudo snap remove --purge steam to uninstall steam 1.0.0.76 latest/edge then went back to 1.0.0.76 latest/stable and it's working now without doing sudo dpkg --add-architecture i386 && sudo apt update or sudo apt install libnvidia-gl-535:i386. Steam did remember what proton version I forced in the game properties but still required a restart when changing it in the settings. If snap purge doesn't completely remove everything then maybe some file got corrupted and was only replaced by switching channels? Yesterday I had to use the terminal because I couldn't uninstall steam using the software center. Maybe saving logs from that would have been useful.
UnrealisticDino
commented
1 year ago It's starting to break again. Certain games no longer work, some are fine, some have performance issues.
ashuntu
commented
1 year ago Could you try https://github.com/canonical/steam-snap/issues/286#issuecomment-1640570498 for completeness sake? On my machine it doesn't seem to matter, but it seems to fix issues for @kenvandine
UnrealisticDino
commented
1 year ago Sorry about that. I should have included that I did try those but only after it started to break again but before making the comment. I did just reboot and it seems to be working fine again. I'll aim to include more relevant information in the future.
UnrealisticDino
commented
1 year ago I finally got around to doing a clean install, had the same issues, https://github.com/canonical/steam-snap/issues/286#issuecomment-1640570498 fixed it.
ashuntu
commented
1 year ago I finally got around to doing a clean install, had the same issues, #286 (comment) fixed it.
If the problems you were experiencing were completely resolved, please close this issue.
Otherwise, it may warrant further digging.
4ndr3aR
commented
10 months ago I can confirm that Steam 1.0.0.78 via snap is unusable. I think it has serious read/write access issues, I see that it manages to download Proton versions but it doesn't create pfx subfolders in compatdata/
UnrealisticDino
commented
10 months ago I can confirm that Steam 1.0.0.78 via snap is unusable. I think it has serious read/write access issues, I see that it manages to download Proton versions but it doesn't create pfx subfolders in compatdata/. Tried extensively with Elite Dangerous (any Proton version) and a few other small Windows games to confirm my theories. What's extremely strange is that writing PROTON_LOG=1 %command% in launch options doesn't produce any log at all. No steam-.log file in $HOME or anywhere else. Changing PROTON_LOG_DIR in user_settings.py to /tmp is the only option to write something, and with something I mean a zero-byte file in /tmp/snap-private-tmp/snap.steam/tmp
The snap has stopped working for me twice and the way I fixed it was by purging the snap then reinstalling. Uninstalling via the software center did not work and would get stuck at about 80%. I haven't been able to replicate it but I think when it broke for me it had something to do with uninstalling Bloons 6.
UnrealisticDino
commented
10 months ago I am going to leave this issue closed though since it seems like you and hardBSDk are experiencing bugs that are not related to the issues I was having.
4ndr3aR
commented
10 months ago I'm sorry, I spent the afternoon yesterday fighting with Steam and Proton, and that was mostly a rant out of frustration. Anyway I can confirm my initial thought: my problem looks like a serious permissions issue, Steam-snap seems to be able to write to half of the locations it should be entitled to write to. Yesterday night I finally removed the Steam snap and installed again via apt. Elite Dangerous worked mostly out of the box (I just had to choose Proton 7.0 probably because of my old Nvidia GTX 650). Hope this can help someone in the future.
ashuntu
commented
10 months ago @4ndr3aR if you're having issues that others are not (and that no issue already exists for), it may be worthwhile to open a new issue if you feel inclined. If it's actually a permissions issue, the denied paths would likely appear in sudo dmesg and would be useful to note in the issue if you open one. My only surface level hints at anything permission related would be to make sure you have plugs connected (snap connections steam lists them).
4ndr3aR
commented
10 months ago Hi @ashuntu,
yep, it's definitely (at least) a permission issue, I've also noticed it with other applications (e.g. chromium not being able to save anything outside its tmp folder) and in other Ubuntu installations, so I assumed it was "to some extent" a relatively normal behavior maybe due to security, sandboxing or whatever. Anyway, I'll keep my eyes open for the next time some application does something similar and I'll double check its snap connections.
lc-nyovchev
commented
10 months ago @4ndr3aR @ashuntu I am almost certain that the issue we are all having is a duplicate of this one: https://github.com/canonical/steam-snap/issues/311
It's rather easy to reproduce.
steam via snapproton versions depending on your confignvidia drivers and reboot, steam will still boot with no problem, but the installed proton versions would fail finding the proper drivers (they'd be searching in the old dirs), so you won't be able to start any gamesteam snap and then reinstalling proton via that makes your games work again (because the paths are now correct)UnrealisticDino
commented
9 months ago @4ndr3aR @ashuntu I am almost certain that the issue we are all having is a duplicate of this one: #311
It's rather easy to reproduce.
* First you install `steam` via `snap` * Then you play some games, which download different `proton` versions depending on your config * Then, if you update your `nvidia` drivers and reboot, `steam` will still boot with no problem, but the installed `proton` versions would fail finding the proper drivers (they'd be searching in the old dirs), so you won't be able to start any game * Reinstalling the `steam` `snap` and then reinstalling `proton` via that makes your games work again (because the paths are now correct)
You might be right. It was working two weeks ago when I made a report running
os_release:
name: "Ubuntu"
version: "22.04.3 LTS (Jammy Jellyfish)"
snap_info:
steam_revision: 171
snapd_revision: 20290
lspci:
08:00.0: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
glxinfo:
gpu: NVIDIA GeForce GTX 1070/PCIe/SSE2
gpu_version: 4.6.0 NVIDIA 535.129.03
lscpu:
model_name: AMD Ryzen 7 3800X 8-Core Processor
xdg_current_desktop: ubuntu:GNOME
desktop_session: ubuntuBut is now broken again
os_release:
name: "Ubuntu"
version: "22.04.3 LTS (Jammy Jellyfish)"
snap_info:
steam_revision: 171
snapd_revision: 20671
lspci:
08:00.0: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
glxinfo:
gpu: NVIDIA GeForce GTX 1070/PCIe/SSE2
gpu_version: 4.6.0 NVIDIA 535.146.02
lscpu:
model_name: AMD Ryzen 7 3800X 8-Core Processor
xdg_current_desktop: ubuntu:GNOME
desktop_session: ubuntu
D1E60E
commented
8 months ago i386-linux-gnu-capsule-capture-libs: warning: Dependencies of libEGL_nvidia.so.0 not found, ignoring: Missing dependencies: Could not find "libnvidia-glsi.so.535.154.05" in LD_LIBRARY_PATH "/snap/steam/171/graphics/lib/i386-linux-gnu:/snap/steam/171/graphics/usr/lib:/snap/steam/171/usr/lib/i386-linux-gnu:/snap/steam/171/lib/i386-linux-gnu
This was my error and then I snap remove --purged the snap version 1.0.0.78 of the steam package
Then I installed apt version which gave me 1.0.0.74 This fixed it !
ashuntu
commented
8 months ago This problem is being tracked in https://github.com/canonical/steam-snap/issues/358 and https://github.com/canonical/steam-snap/issues/311.
gazhay
commented
6 months ago @4ndr3aR @ashuntu I am almost certain that the issue we are all having is a duplicate of this one: #311
It's rather easy to reproduce.
- First you install
steamviasnap- Then you play some games, which download different
protonversions depending on your config- Then, if you update your
nvidiadrivers and reboot,steamwill still boot with no problem, but the installedprotonversions would fail finding the proper drivers (they'd be searching in the old dirs), so you won't be able to start any game- Reinstalling the
steamsnapand then reinstallingprotonvia that makes your games work again (because the paths are now correct)
Just had this issue and confirm this solution does not work. After many graphics driver changes (and reboots) and multiple snap reinstalls (including redownloading all the games, adding accounts, etc) what was working fine 3 days ago no longer works.
Logs are all but useless as they show things like
ERROR: ld.so: object '/home/gaz/snap/steam/common/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.or
(steam:18683): GLib-GIO-CRITICAL **: g_settings_schema_source_lookup: assertion `source != NULL' failedBut all are variously described elsewhere as "red herrings".
Rolled back as far as nvidia-525 but still nothing. Like I said was all happy just days ago.
Describe the bug Zero games work. After pressing play it will process shaders, say running for a second, then the game stops.
To Reproduce The steam snap has slowly gotten worse after the nvidia 535 driver update and now no games work. Steps to reproduce the behavior:
Expected behavior Games that used to work should still work. Games that gave errors should give the same errors.
Screenshots
Environment
snap run steam.reportLogs Add any errors/warnings output to the terminal (if applicable). Run Steam from the terminal with
snap run steamto easily see output.Additional Context