Steamwebhelper encounters stack smashing with NVIDIA 390
I'm just going to take a stab in the dark wondering if this is the same issue I commented about on bug #10942 . Is it possible to downgrade your kernel version to something lower than 6.9 and see if that resolves the issue?
This is so frustrating. I've been trying to unsubscribe from this thread
but no matter what I do I keep getting emails from it. Can anyone help?
On Sat, Jun 15, 2024, 19:12 PaddyMac @.***> wrote:
I'm just going to take a stab in the dark wondering if this is the same
issue I commented about on bug #10942
https://github.com/ValveSoftware/steam-for-linux/issues/10942 . Is it
possible to downgrade your kernel version to something lower than 6.9 and
see if that resolves the issue?—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/10980#issuecomment-2170998822,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVOY4BEUQT3HL6ROX3PUELTZHTQ7TAVCNFSM6AAAAABJLWNVO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZQHE4TQOBSGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
my kernel is 5.15 and until yesterday steam worked fine , after the last update all gone to hell , and don't need to downgrade or upgrade the kernel , steam need to work with all kernels
Had the exact issue, since yesterday (after update).
Solution for me was changing the driver from nvidia-driver-390 to nvidia-driver-530. Steam is now working again.
I'm having the same problem using archlinux
Kernel: 6.9.4-lqx1-1-lqx
GPU: Intel
I also have the same problem from one day ago since the steam update, what I did was
- I tried to change the GPU from nvidia to intel (sudo prime-select intel) successfully run, I can run steam launcher and games.
- when I change again from intel to nvidia (sudo prime-select nvidia) the previous thing happened again, just blinking after verifying the update and when I run it through the terminal there is no info (or maybe there is another way that I don't know), maybe a steam bug on the gpu.
my specs:
gpu driver: nvidia-390 (610m) and intel hd4000m driver(
kernel: 5.15.0-107-generic
os : Zorin 16 Lite
If the NVIDIA 390 series video driver is involved, then this is another variation of https://github.com/ValveSoftware/steam-runtime/issues/420.
I canot unninstal the nvidia 390 driver because no other driver works for me , i am wondering when the updates are made , there is someone who testing ????? who the hell are doing thoes updates , why my steam yesterday worked fine without bugs , without problems ..... after updating .... canot open anymore??????
I'm seeing this since Steam updated yesterday. Also using NVIDIA 390 series, on Ubuntu 22.04, kernel 6.5.0-35-generic.
Also seeing this. Very disappointing. I dusted off my laptop (not my daily driver, which is a desktop) for some long-awaited PTO. Figured I would update Steam so I could play some of my older games while I was out.
Steam was working - after update, not working. Just saying that the 390 drivers are "not supported" is no good - no newer drivers work with the GPU in this laptop.
I guess no gaming for me while on vacation.. If I'd known this was going to happen (just a few days before my vacation!) I'd have done the updates and set it to offline mode a week or two ago (before steam decided it hates my laptop)... shoot.
edit: I do have to wonder what changed in the soldier runtime that made it worth breaking the entire steam client. Saying that proton is not supported on the 390 driver is one thing - but steam in general? Seems a bit extreme to break that with a seemingly innocuous runtime update that I wasn't able to opt out of. The titles I was looking to play werent even proton titles - they were linux-native.
If the NVIDIA 390 series video driver is involved, then this is another variation of ValveSoftware/steam-runtime#420.
Apologies for the double reply. Trying to narrow down the issue, and get official word on it.
So, for users that have older GPUs (e.g. a moderately "mature" laptop) - is running steam (in general) now officially unsupported, period? https://github.com/ValveSoftware/steam-runtime/issues/420 was with respect to Proton. This is not Proton, this is the steam client itself. I now can't get to any of my games, proton or otherwise.
PS - the frustration about my laptop issues aside - I love Proton, Steam, and use both almost every day on my desktop. Other than this unanticipated break, I've been immensely pleased with how it's come along.
I'm seeing this since Steam updated yesterday. Also using NVIDIA 390 series, on Ubuntu 22.04, kernel 6.5.0-35-generic.
The OP has the same crash in the webhelper-linux.txt log.
I did a test of the steam version on flatpak and it worked normally the first time I run it after closing and opening it again appears the same error as the native with steam already logged in appears the steamwebhelper warning after closing loads steam and the message that is in the screenshot appears
Today Steam has made another update ... but without success , it gives me the same error ...
allex@allex-K55VM:~$ steam
steam.sh[2412]: Running Steam on linuxmint 21.3 64-bit
steam.sh[2412]: STEAM_RUNTIME is enabled automatically
setup.sh[2532]: Steam runtime environment up-to-date!
steam.sh[2412]: Steam client's requirements are satisfied
[2024-06-20 06:38:11] Startup - updater built Jun 18 2024 22:39:03
[2024-06-20 06:38:11] Startup - Steam Client launched with: '/home/allex/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
06/20 06:38:11 minidumps folder is set to /tmp/dumps
06/20 06:38:11 Init: Installing breakpad exception handler for appid(steam)/version(1718751621)/tid(2598)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2024-06-20 06:38:11] Loading cached metrics from disk (/home/allex/.local/share/Steam/package/steam_client_metrics.bin)
[2024-06-20 06:38:11] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2024-06-20 06:38:11] Using the following download hosts for Public, Realm steamglobal
[2024-06-20 06:38:11] 1. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-06-20 06:38:11] Checking for update on startup
[2024-06-20 06:38:11] Checking for available updates...
[2024-06-20 06:38:11] Downloading manifest: https://cdn.steamstatic.com/client/steam_client_ubuntu12
[2024-06-20 06:38:11] Manifest download: send request
[2024-06-20 06:38:11] Manifest download: waiting for download to finish
[2024-06-20 06:38:12] Manifest download: finished
[2024-06-20 06:38:12] Download skipped: /client/steam_client_ubuntu12 version 1718751621, installed version 1718751621, existing pending version 0
[2024-06-20 06:38:12] Nothing to do
[2024-06-20 06:38:12] Verifying installation...
[2024-06-20 06:38:12] Performing checksum verification of executable files
[2024-06-20 06:38:13] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/allex/.local/share/Steam/logs
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf3aa9370
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xf3aa7cc0
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 2718
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
[2024-06-20 06:40:14] Background update loop checking for update. . .
[2024-06-20 06:40:14] Checking for available updates...
[2024-06-20 06:40:14] Downloading manifest: https://cdn.steamstatic.com/client/steam_client_ubuntu12?t=613738304
[2024-06-20 06:40:14] Manifest download: send request
[2024-06-20 06:40:14] Manifest download: waiting for download to finish
[2024-06-20 06:40:17] Manifest download: finished
[2024-06-20 06:40:17] Download skipped by HTTP 304 Not Modified
[2024-06-20 06:40:17] Nothing to do
After the update happened the same problem of flatpak opening for the first time and stops working again
It's becoming worse after every damn update. I would love to go back to 2018/19 Steam, UI was just perfect and had no bugs or problems like this... Really considering removing this crap full of lib32 packages and just running Lutris...
i don't have any issues , only the gpu acceleration thing on X11;
Ok, I found what works for me as a solution (Ubuntu 20.04):
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.390.157" steam
or as a longer-term solution, add the following to /etc/ld.so.conf.d/nvidiafix.conf:
/usr/lib/x86_64-linux-gnu/tls/ then run sudo ldconfig.
This solved the issue for me. Able to launch & login to steam again.
Shout out to the excellent arch community at https://bbs.archlinux.org/viewtopic.php?id=283327
Hello @jhalag, it would be interesting to test if that workaround extends to steam-runtime#420. If it does, then that's an interesting hint for a runtime dev to look closer at.
I'd suggest trying to get Team Fortress 2 to run in Legacy OpenGL mode from the Steam client and follow up on https://github.com/ValveSoftware/steam-runtime/issues/420 if you have any interesting results.
Ok, I found what works for me as a solution (Ubuntu 20.04):
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.390.157" steamor as a longer-term solution, add the following to
/etc/ld.so.conf.d/nvidiafix.conf:/usr/lib/x86_64-linux-gnu/tls/then runsudo ldconfig.This solved the issue for me. Able to launch & login to steam again.
Shout out to the excellent arch community at https://bbs.archlinux.org/viewtopic.php?id=283327
This works for me as well on Ubuntu 22.04.
After I reinstalled my system, Steam was back to working normally in the stable version
Ok, I found what works for me as a solution (Ubuntu 20.04):
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.390.157" steamor as a longer-term solution, add the following to
/etc/ld.so.conf.d/nvidiafix.conf:/usr/lib/x86_64-linux-gnu/tls/then runsudo ldconfig.This solved the issue for me. Able to launch & login to steam again.
Shout out to the excellent arch community at https://bbs.archlinux.org/viewtopic.php?id=283327
hey, the first option worked great, but i want to use the second option because i do not want to write the code every time i enter steam. can you explain in detail how to do it, i am a new Linux user
Ok, I found what works for me as a solution (Ubuntu 20.04):
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.390.157" steamor as a longer-term solution, add the following to
/etc/ld.so.conf.d/nvidiafix.conf:/usr/lib/x86_64-linux-gnu/tls/then runsudo ldconfig.This solved the issue for me. Able to launch & login to steam again.
Shout out to the excellent arch community at https://bbs.archlinux.org/viewtopic.php?id=283327
This worked for me, thanks!
In case anyone comes across this, I'm running Ubuntu 22.04 with a geforce gt 730 and nvidia drivers version 390.
Installed steam through .deb package.
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Steps for reproducing this issue:
steam-logs.tar.gz