Steam not launching on Ubuntu 24.04

Thing-y commented 2 weeks ago

Your system information

Chromebook C732, Intel® Celeron® N3350 × 2, 4 GB RAM, Intel® HD Graphics 500 (APL 2)

Steam client version (build number or date): Latest (I don't know how to check.)
Distribution (e.g. Ubuntu): Ubuntu 24.04
Opted into Steam client beta?: [Yes/No] No
Have you checked for system updates?: [Yes/No] Yes
Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] steam-logs.tar.gz
GPU: Nvidia/Intel/AMD Intel

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 Okay, so I'm kinda new to Linux, and I've just installed Ubuntu 24.04 and tried to install Steam (after I had the same problem in Xubuntu). I just added the I386 architecture, ran sudo apt uptade and upgrade, and then installed Steam with apt install. The installation worked fine, but when i try to execute it, it gives the following errors:

steam.sh[2920]: Running Steam on ubuntu 24.04 64-bit
steam.sh[2920]: STEAM_RUNTIME is enabled automatically
setup.sh[2990]: Steam runtime environment up-to-date!
/home/thingy/.steam/debian-installation/ubuntu12_32/steam-runtime/run.sh: line 85: steam-runtime-identify-library-abi: command not found
run.sh[3005]: steam-runtime-identify-library-abi --ldconfig-paths failed, falling back to ldconfig
steam.sh[2920]: Can't find 'steam-runtime-check-requirements', continuing anyway
tid(3051) burning pthread_key_t == 0 so we never use it
[2024-05-02 21:55:31] Startup - updater built Jan 13 2024 00:51:43
[2024-05-02 21:55:31] Startup - Steam Client launched with: '/home/thingy/.steam/debian-installation/ubuntu12_32/steam' '-nominidumps' '-nobreakpad'
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
05/02 21:55:32 Init: Installing breakpad exception handler for appid(steam)/version(0)/tid(3051)
crash_20240502215536_2.dmp[3114]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240502215536_2.dmp
crash_20240502215536_2.dmp[3114]: Finished uploading minidump (out-of-process): success = no
crash_20240502215536_2.dmp[3114]: error: libcurl.so: cannot open shared object file: No such file or directory
crash_20240502215536_2.dmp[3114]: file ''/tmp/dumps/crash_20240502215536_2.dmp'', upload no: ''libcurl.so: cannot open shared object file: No such file or directory''
/home/thingy/.steam/debian-installation/steam.sh: line 798:  3051 Segmentation fault      (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"

Can anyone help me out?

Steps for reproducing this issue:

Install fresh copy of Ubuntu 24.04 on a C732 Chromebook.
Add i386 architecture.
Install Steam.

learning-thing commented 2 weeks ago

I'm pretty sure I am having the same problem on Arch, looking a bit similar except the message about family beta.

CPU: Ryzen 5 3600 GPU: NVIDIA GTX 1650 24GB ram Kernel: 6.8.8-arch1-1 DE: KDE (x11) Distro Arch Linux (Everything should be up-to-date)

steam.sh[70717]: Running Steam on arch rolling 64-bit
steam.sh[70717]: STEAM_RUNTIME is enabled automatically
setup.sh[70790]: Steam runtime environment up-to-date!
/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh: Zeile 85: steam-runtime-identify-library-abi: Kommando nicht gefunden.
run.sh[70802]: steam-runtime-identify-library-abi --ldconfig-paths failed, falling back to ldconfig
steam.sh[70717]: Can't find 'steam-runtime-check-requirements', continuing anyway
tid(70852) burning pthread_key_t == 0 so we never use it
[2024-05-03 16:12:49] Startup - updater built Jan 13 2024 00:51:43
[2024-05-03 16:12:49] Startup - Steam Client launched with: '/home/user/.local/share/Steam/ubuntu12_32/steam'
[2024-05-03 16:12:49] Opted in to client beta 'publicbeta_families' via beta file
You are in the 'publicbeta_families' client beta.
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
05/03 16:12:49 Init: Installing breakpad exception handler for appid(steam)/version(1714520927)/tid(70852)
crash_20240503161249_2.dmp[70855]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240503161249_2.dmp
/home/user/.local/share/Steam/steam.sh: Zeile 798: 70852 Speicherzugriffsfehler  (Speicherabzug geschrieben) "$STEAMROOT/$STEAMEXEPATH" "$@"

SubtleMuffin commented 2 weeks ago

See this issue: https://github.com/ValveSoftware/steam-for-linux/issues/10841

learning-thing commented 2 weeks ago

See this issue: #10841

Could be a douplicate maybe, wondering though, why the line is different, in here op and I both have line 798, while the other issue is on line 813. Furthermore, op is on ubuntu, while (afaict) the other issue seemed arch-specific?

learning-thing commented 2 weeks ago

Just had an update on Arch, regarding glibc and it seems to have fixed it, steam seemed a but buggy at first after the update and didn't want to start properly, "steam --reset " fixed it, now working normally again.

smcv commented 1 week ago

@Thing-y:

on a C732 Chromebook

Is this installed directly onto the hardware from Ubuntu install media, or is this Ubuntu running as a container under ChromeOS?

smcv commented 1 week ago

/home/thingy/.steam/debian-installation/ubuntu12_32/steam-runtime/run.sh: line 85: steam-runtime-identify-library-abi: command not found
run.sh[3005]: steam-runtime-identify-library-abi --ldconfig-paths failed, falling back to ldconfig
steam.sh[2920]: Can't find 'steam-runtime-check-requirements', continuing anyway
tid(3051) burning pthread_key_t == 0 so we never use it

These messages are harmless and can safely be ignored.

I just added the I386 architecture, ran sudo apt uptade and upgrade, and then installed Steam with apt install

This is the Debian/Ubuntu .deb (steam-installer) and not Valve's steam-launcher, in case that matters. In principle both should be able to work.

crash_20240502215536_2.dmp[3114]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240502215536_2.dmp
...
/home/thingy/.steam/debian-installation/steam.sh: line 798:  3051 Segmentation fault      (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"

This indicates that the root cause of your issue is: "something inside Steam crashed". Unfortunately...

crash_20240502215536_2.dmp[3114]: error: libcurl.so: cannot open shared object file: No such file or directory
crash_20240502215536_2.dmp[3114]: file ''/tmp/dumps/crash_20240502215536_2.dmp'', upload no: ''libcurl.so: cannot open shared object file: No such file or directory''

... Steam's crash reporting was unable to upload the crash dump, so nobody in Valve can examine it.

I'll see whether I can reproduce this in a VM.

smcv commented 1 week ago

I was unable to reproduce the crash originally reported here in an Ubuntu 24.04 live image. I got a different error (step 13), for which there is a workaround (step 14).

Steps to attempt to reproduce this. Note that this is not Valve's recommended way to install Steam on .deb systems (Valve's recommendation is to use their own steam-launcher package, as seen on #10855) - I am doing my best to replicate what @Thing-y did, not providing an exemplary install log.

Boot an Ubuntu 24.04 live image, in a virtual machine with lots of RAM (I gave it 8G) so that it will have enough space on the root tmpfs to install Steam. I found that virtio graphics didn't work, and used qxl as a workaround.
When prompted, choose a keyboard layout etc., and choose to "Try Ubuntu" rather than "Install Ubuntu".
Open a terminal
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install steam (in this case steam is a transitional package with a dependency on steam-installer, both at version 1:1.0.0.79~ds-2)
steam
See a prompt warning me that Steam is proprietary binary-only software. Choose Install.
See a light grey progress bar "Steam setup / Updating Steam runtime environment...". Wait.
See a dark grey progress bar "Steam / Updating Steam... Downloading update (xxx of 465,450 KB)...". Wait.
Dark grey progress bar becomes "Steam / Updating Steam... Extracting package...". Wait.
Output in terminal shows "Restarting Steam by request...". Wait.
"Error / Steam now requires user namespaces to be enabled". This is https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844, and does not resemble the issue originally reported here.
Work around the error message seen in step 13 by forcing Ubuntu's AppArmor profile for Steam to be reloaded: sudo apparmor_parser -Tr /etc/apparmor.d/steam
Run steam again
See a light grey progress bar "Unpacking Steam Linux Runtime...". Wait.
Login dialog with account name box, password box and a QR code appears, and I can sign in. I didn't test beyond this point.

smcv commented 1 week ago

I got a different error (step 13), for which there is a workaround (step 14).

Reported as https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065088, but in any case that was not the main point of this issue report.

mandle420 commented 6 days ago

cd /home/$USER/.steam/steam/ubuntu12_32/steam-runtime/pinned_libs_64

mv libcurl.so.4 libcurl.so.4.bak

ln -s /usr/lib/x86_64-linux-gnu/libcurl.so.4 libcurl.so.4

may not work, but it does seem to match an issue i've been having for awhile now.... steam libraries don't like something, or ubuntu libraries don't like steam. dunno don't care. it'd be nice to have it fixed tho...

Thing-y commented 6 days ago

cd /home/$USER/.steam/steam/ubuntu12_32/steam-runtime/pinned_libs_64

mv libcurl.so.4 libcurl.so.4.bak

ln -s /usr/lib/x86_64-linux-gnu/libcurl.so.4 libcurl.so.4

may not work, but it does seem to match an issue i've been having for awhile now.... steam libraries don't like something, or ubuntu libraries don't like steam. dunno don't care. it'd be nice to have it fixed tho...

I'll try it out, thanks.

smcv commented 6 days ago

mv libcurl.so.4 libcurl.so.4.bak

This is unsupportable. I would prefer to analyze what is going wrong so that it can be fixed.

@mandle420, please collect the logs requested in the issue template, and provide details of your system and any workarounds you have applied.

It might be better to do this on a separate issue report in case you and @Thing-y are actually experiencing different issues - it's easier to mark a duplicated issue report as a duplicate than it is to disentangle two separate issue reports from one issue report thread, and the longer it takes to understand what is wrong, the longer it will take to fix anything.

dunno don't care. it'd be nice to have it fixed tho...

If the Steam and Steam Runtime developers cannot reproduce an issue (which I couldn't), then it cannot be fixed until/unless someone who can reproduce the issue (maybe you) provides enough information for us to see what is happening.

ValveSoftware / steam-for-linux