Skip to main content ↑ ↓
Topic: Steam refuses to start (Segmentation fault) (Read 1773 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Steam refuses to start (Segmentation fault)

Decided to finally use Artix as I have been an Arch user for awhile. Went through the migration process smoothly, and didn't have any troubles until I went to try and start Steam. It just refuses to launch.

Code: [Select]
➜  ~ steam-runtime
Running Steam on artix rolling 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Can't find 'steam-runtime-check-requirements', continuing anyway
WARNING: Using default/fallback debugger launch
/home/nick/.local/share/Steam/ubuntu12_32/steam
[2021-04-11 16:22:34] Startup - updater built Mar 23 2021 20:11:00
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
Installing breakpad exception handler for appid(steam)/version(0)
crash_20210411162234_1.dmp[4838]: Uploading dump (out-of-process)
/tmp/dumps/crash_20210411162234_1.dmp
/home/nick/.local/share/Steam/steam.sh: line 771:  4825 Segmentation fault      $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
crash_20210411162234_1.dmp[4838]: Finished uploading minidump (out-of-process): success = yes
crash_20210411162234_1.dmp[4838]: response: CrashID=bp-18597ce8-1492-4c1e-8cea-fecd92210411
crash_20210411162234_1.dmp[4838]: file ''/tmp/dumps/crash_20210411162234_1.dmp'', upload yes: ''CrashID=bp-18597ce8-1492-4c1e-8cea-fecd92210411''

I'm not entirely sure what the issue is. I have Multilib and lib32 enabled as I had before (already updated pacman.conf), reinstalled steam and even cleared caches packages. No difference in native or runtime. I am guessing the failing to find file is the issue, but I'm not entirely sure how to fix it. The Segmentation fault seems to be from starting the debugger, since checking the script shows line 771 being the end of many if's about the debugger variable.

I cleared my ~/.local/share/Steam and ~/.steam (besides installed games). Couldn't find anything else where and even looked through this forum. I'm using runit if that matters with AMD graphics.

Any help would be appreciated.

Re: Steam refuses to start (Segmentation fault)

Reply #3 –
read https://wiki.archlinux.org/index.php/Steam/Troubleshooting, which can help you maybe too

can you try instaln native-runtime? pacman -S steam-native-runtime

Code: [Select]
steam-native
and test if steam will start or not. (i use steam-native for many years, and i never has a problem with launch steam or with games.)
 
But your problem is sounds more as wrong version of driver or missing library....  because "Can't find 'steam-runtime-check-requirements', continuing anyway"
Which driver you use for AMD?  It seems, as  public/steambootstrapper_english.txt if it did not exist .

it´s your output  complete?

Re: Steam refuses to start (Segmentation fault)

Reply #4 –
Quote from: alium – on
read https://wiki.archlinux.org/index.php/Steam/Troubleshooting, which can help you maybe too

you cab try instaln native-runtime? pacman -S steam-native-runtime

Code: [Select]
steam-native
and test if steam will start or not. (i use steam-native years, and i never has a problem with launch steam or with games.)
 
But your problem is sounds more as wrong version of driver or missing library....  because "Can't find 'steam-runtime-check-requirements', continuing anyway"
Which driver you use for AMD?



Steam native is the exact same issue. Nothing is different, and the output is exactly the same (besides the dump file). I've looked into the steam troubleshooting and nothing has solved my issue. I'm using the amdgpu kernel module right now with an RX 560. I should note this was completely working fine pre-artix migration. Steam ran perfectly and I have not changed drivers or anything during or after my migration process.

Re: Steam refuses to start (Segmentation fault)

Reply #5 –
if you migrate, do you have still lib32-systemd installed?

put here output from '/tmp/dumps/crash_20210411162234_1.dmp' or similar dmp, please

Re: Steam refuses to start (Segmentation fault)

Reply #6 –
Quote from: alium – on
if you migrate, do you have still lib32-systemd installed?

put here output from '/tmp/dumps/crash_20210411162234_1.dmp' or similar dmp, please
No lib32-systemd. Instead, I have lib32-elogind like I should.

I'm not familiar with using dump files, and not entirely sure how to bring the output here as I do not see a way to attach the dmp file or know how to get an output.
 

Re: Steam refuses to start (Segmentation fault)

Reply #7 –
Code: [Select]
LANG=C steam
crash too?

from wiki and another web page with same problem as you have:
Quote
Generated en_US.UTF-8 locale, preventing invalid pointer error.

run
Code: [Select]
sudo locale-gen
be sure, that en_US.UTF-8 is enabled

Re: Steam refuses to start (Segmentation fault)

Reply #8 –
Quote from: alium – on
Code: [Select]
LANG=C steam
crash too?

from wiki and another web page with same problem as you have:
run
Code: [Select]
sudo locale-gen
be sure, that en_US.UTF-8 is enabled

Both result in the same output with no differences. Locale generated for 'en_US.UTF-8', all done and no different steam output than before.

Re: Steam refuses to start (Segmentation fault)

Reply #9 –
please try complete uninstallation of lib32
Code: [Select]
sudo pacman -Rcs steam lib32-glibc
and install it again with
Code: [Select]
pacman -S steam
and select properly lib32´s drivers for amd (lib32-vulkan-radeon and similar)

dump should be readable with

Code: [Select]
cat /tmp/dumps/crash_XXXXXXXXXX.dmp

which DE you use?

Re: Steam refuses to start (Segmentation fault)

Reply #10 –
Quote from: alium – on
please try complete uninstallation of lib32
Code: [Select]
sudo pacman -Rcs steam lib32-glibc
and install it again with
Code: [Select]
pacman -S steam
and select properly lib32´s drivers for amd (lib32-vulkan-radeon and similar)

dump should be readable with

Code: [Select]
cat /tmp/dumps/crash_XXXXXXXXXX.dmp

which DE you use?

Completely reinstalling is the same result.

Dump is not readable with a cat at all. It contains unreadable characters and is 160 Kb in size. I use KDE Plasma.