I have uninstalled Steam, deleted all files in ~/.local/share/Steam, reinstalled Steam and the segfault still happens. It might be a library that was recently updated that broke it, but I'm not sure since it seems like I'm the only person who has this issue. I can't really think of much else to do other than to reinstall Arch and see if that fixes the issue, but I really don't want to have to do that.
Having this same issue - Steam was working fine on Ubuntu for me for the last month, and a recent package update broke it because when I restarted it's not working anymore.
Tried the usual uninstalling all nvidia drivers, CUDA, and reinstalling only sudo apt install nvidia-driver-460 libnvidia-gl-460:i386 without any luck. It worked before.
I think i've ran into the same issue on fedora workstation 32 with an AMD card, steam runs fine for a while but then it suddenly crashes (taking the game i'm playing with it) with the line 759 error.
Having this same issue - Steam was working fine on Ubuntu for me for the last month, and a recent package update broke it because when I restarted it's not working anymore.
Tried the usual uninstalling all nvidia drivers, CUDA, and reinstalling only
sudo apt install nvidia-driver-460 libnvidia-gl-460:i386without any luck. It worked before.
i only just recently tried the 460 drivers on my Kubuntu 20.04 and steam crashed on all loading attempts... i reverted to the 450 drivers and steam runs again... i'm only just now looking a little further into this problem... maybe reverting to the 450 drivers will also work for you even though it has been two months and if you still have the problem with the 460 drivers...
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Steam experiences a segmentation fault when starting, seemingly caused by a crash in "browser".
When Steam is started using a terminal emulator, the following output is displayed:
Using the native runtime which tries to use Arch Linux's own system libraries, the same error is reported, as shown below:
Viewing the coredump doesn't reveal much information, but I'll post it nonetheless.
Steps for reproducing this issue:
Also note that I have filed this issue on the Arch Linux forums, but it doesn't seem like the people there have figured out the issue.