I've tested two computers:
Interestingly, both of these computers work perfectly when switched to Windows operating system. However
~$ steam
steam.sh[28717]: Running Steam on ubuntu 20.04 64-bit
steam.sh[28717]: STEAM_RUNTIME is enabled automatically
setup.sh[28835]: Steam runtime environment up-to-date!
steam.sh[28717]: Steam client's requirements are satisfied
[2023-08-11 16:48:45] Startup - updater built Jul 28 2023 18:44:09
[2023-08-11 16:48:45] Startup - Steam Client launched with: '/home/mi/.local/share/Steam/ubuntu12_32/steam'
08/11 16:48:45 Init: Installing breakpad exception handler for appid(steam)/version(1690583737)/tid(28926)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2023-08-11 16:48:46] Loading cached metrics from disk (/home/mi/.local/share/Steam/package/steam_client_metrics.bin)
[2023-08-11 16:48:46] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2023-08-11 16:48:46] Using the following download hosts for Public, Realm steamglobal
[2023-08-11 16:48:46] 1. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-08-11 16:48:46] Checking for update on startup
[2023-08-11 16:48:46] Checking for available updates...
[2023-08-11 16:48:46] Downloading manifest: https://cdn.steamstatic.com/client/steam_client_ubuntu12
[2023-08-11 16:48:46] Manifest download: send request
[2023-08-11 16:48:46] Manifest download: waiting for download to finish
[2023-08-11 16:48:47] Manifest download: finished
[2023-08-11 16:48:47] Download skipped: /client/steam_client_ubuntu12 version 1690583737, installed version 1690583737, existing pending version 0
[2023-08-11 16:48:47] Nothing to do
[2023-08-11 16:48:47] Verifying installation...
[2023-08-11 16:48:47] Performing checksum verification of executable files
[2023-08-11 16:48:47] Verification complete
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf182e370
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xf182ccc0
/home/mi/.themes/Flat-Remix-GTK-Blue/gtk-2.0/main.rc:1090: error: unexpected identifier 'direction', expected character '}'
/home/mi/.themes/Flat-Remix-GTK-Blue/gtk-2.0/apps.rc:91: error: unexpected identifier 'direction', expected character '}'
GetWin32Stats: display was not open yet, good
GetWin32Stats: display was not open yet, good
steamwebhelper.sh[28939]: Runtime for steamwebhelper: defaulting to /home/mi/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[28939]: Using CEF sandbox (try with -no-cef-sandbox if this fails)
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Segmentation fault (core dumped)
mi@e5-desktop:~$ glxinfo | grep "OpenGL"
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Radeon RX 590 Series
OpenGL core profile version string: 4.6.14756 Core Profile Context 20.45
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.14756 Compatibility Profile Context 20.45
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: 4.6.14756 Compatibility Profile Context 20.45
OpenGL ES profile shading language version string: 4.60
OpenGL ES profile extensions:
It appears that the issue isn't related to Mesa drivers. Back in 2022,
Steam was functioning properly on my Ubuntu system with an RX590 GPU.
I was able to play games like Hollow Knight without any problems.
However, after Steam updated its login launcher to a more recent style,
I encountered issues. Specifically, I found that I couldn't interact with the Steam UI – it became unresponsive.
Before I tried reinstalling Steam, I discovered a workaround: I could initiate game launches with alreay login user by right-clicking the Steam icon in the taskbar and selecting the game from the menu.
It appears that the issue stems from the new Steam update, which introduced a different UI library. This change seems to be causing the problem.
mi@e5-desktop:/etc/apt$ tree .
.
├── apt.conf.d
│ ├── 00aptitude
│ ├── 00trustcdrom
│ ├── 01autoremove
│ ├── 01-vendor-ubuntu
│ ├── 10periodic
│ ├── 15update-stamp
│ ├── 20apt-esm-hook.conf
│ ├── 20archive
│ ├── 20auto-upgrades
│ ├── 20dbus
│ ├── 20packagekit
│ ├── 20snapd.conf
│ ├── 50appstream
│ ├── 50command-not-found
│ ├── 50unattended-upgrades
│ ├── 60icons
│ ├── 60icons-hidpi
│ ├── 70debconf
│ └── 99update-notifier
├── auth.conf.d
├── dir
├── preferences.d
│ ├── amdgpu
│ ├── amdgpu-core
│ ├── amdgpu-dkms
│ ├── amdgpu-doc
│ ├── amdgpu-pin
│ ├── amdgpu-pro
│ ├── amdgpu-pro-core
│ ├── amf-amdgpu-pro
│ ├── appprofiles-amdgpu
│ ├── clinfo-amdgpu
│ ├── comgr-amdgpu
│ ├── gst-omx-amdgpu
│ ├── hsakmt-roct-amdgpu
│ ├── hsa-runtime-rocr-amdgpu
│ ├── libdrm-amdgpu
│ ├── libdrm-amdgpu-common
│ ├── llvm-amdgpu
│ ├── llvm-amdgpu-rocm
│ ├── mesa-amdgpu
│ ├── ocl-icd-amdgpu
│ ├── opencl-orca-amdgpu
│ ├── opencl-rocr-amdgpu
│ ├── opengl-amdgpu
│ ├── repo-radeon-pin-600
│ ├── rocm-device-libs-amdgpu
│ ├── vulkan-amdgpu
│ ├── vulkan-amdgpu-pro
│ └── xserver-xorg-amdgpu-video-amdgpu
├── sources.list
├── sources.list.aliyun
├── sources.list.bak
├── sources.list.d
│ ├── mongodb-org-4.4.list
│ ├── mongodb-org-5.0.list.bak
│ ├── steam-beta.list
│ └── steam-stable.list
├── sources.list.save
├── trusted.gpg
├── trusted.gpg~
└── trusted.gpg.d
├── microsoft-edge.gpg
├── microsoft-edge.gpg~
├── microsoft.gpg~
├── mongodb.gpg
├── oibaf_ubuntu_graphics-drivers.gpg
├── rocm-keyring.gpg
├── scootersoftware-keyring.gpg
├── sublimehq-archive.gpg
├── ubuntu-keyring-2012-archive.gpg
├── ubuntu-keyring-2012-cdimage.gpg
└── ubuntu-keyring-2018-archive.gpg
6 directories, 68 files
I hope these contribute to resolving the issue.
However, what's strange is that on another computer with a newly installed Ubuntu 20.04 and an NVIDIA RTX 3090 graphics card, the same issue persists.
However, what's strange is that on another computer with a newly installed Ubuntu 20.04 and an NVIDIA RTX 3090 graphics card, the same issue persists.
So, I believe that any computer with a fresh installation of Ubuntu 20.04, using the latest steam_latest.deb, will trigger this bug.
on Ubuntu 20.04.5 LTS
This is not the current version of Ubuntu LTS, so I would recommend upgrading to 22.04 if possible.
with a clean Ubuntu 20.04.5 LTS installation
OpenGL vendor string: Advanced Micro Devices, Inc.
Which one of these is it? A normal/clean installation of Ubuntu 20.04 should have the Mesa graphics driver stack, not AMDGPU or AMDVLK (which have been known to cause weird crashes in the past). I'd recommend the default Mesa drivers, which are also what's used on the Steam Deck (although that has a much newer version).
with a clean Ubuntu 20.04.5 LTS installation
OpenGL vendor string: Advanced Micro Devices, Inc.
Which one of these is it? A normal/clean installation of Ubuntu 20.04 should have the Mesa graphics driver stack, not AMDGPU or AMDVLK (which have been known to cause weird crashes in the past). I'd recommend the default Mesa drivers, which are also what's used on the Steam Deck (although that has a much newer version).
Actually, I have tried installing the original version of Ubuntu on three different machines. After the fresh installation, when I install Steam, I encounter the same issue.
"If there is an issue, it seems that the new version of Steam might not have been tested with the official Ubuntu 20.04 release. Prior to this, Steam used to run smoothly on this version, regardless of whether the graphics card was AMD or NVIDIA."
"Regardless of whether the driver is Mesa or AMD Pro, the previous version of Steam used to run smoothly. However, ever since Steam updated its interface, the Linux version has been compromised and is no longer functioning."
"Is it normal for Steam to not run on Ubuntu? Has it undergone release testing?"
Nothing extracted yet.
System Information
Issue Description
I'm encountering an issue with the Steam for Linux launcher on Ubuntu 20.04.5 LTS. Upon launching, the Steam launcher initializes as expected, but it becomes unresponsive to user input. The GUI client remains frozen, and the terminal displays a "Segmentation fault (core dumped)" error.
I anticipated that the Steam launcher would start smoothly, enabling interaction with the GUI client. However, the actual behavior is an unresponsive GUI and a terminal error.
Steps to Reproduce
Additional Notes
I've tested this issue on a new computer with a clean Ubuntu 20.04.5 LTS installation. I downloaded the steam_latest.deb package and installed it. When attempting to run Steam via the terminal, it consistently results in a "Segmentation fault (core dumped)" error. This issue occurs on both Intel and Nvidia GPUs, without configuring or installing additional drivers.
Your assistance in resolving this issue would be greatly appreciated. Please let me know if further information is required.