I'm running into the exact same issue on Linux Mint 20.1 Cinnamon. Fully up to date on everything as well.
Same on Manjaro
Here my dump file:
assert_20210525162547_1.zip
For reference, the attached minidump is a SIGSEGV in steamclient.so.
For reference, the attached minidump is a SIGSEGV in steamclient.so.
And that what means? Is there anything I can do to solve it?
There's an old issue here, that's still open: https://github.com/ValveSoftware/steam-for-linux/issues/4428 | regarding a similar issue. There's some suggested fixes there. I've tried them all, it still crashes for me at startup. I'm on Manjaro 5.11, and the crash dump is pretty much the same as above.
I was able to resolve my issue by uninstalling steam-native from the system. I then hopped over to Applications (bauh) and installed the flatpak version of the steam provided by flathub. It installed, downloaded a 288MB update, and then went through a cycle of purging old pins and force rebuilding pins to be new. Thereafter, the application started up again and works no issues. I recognize that this doesn't address the native application, but this can be considered an alternative fix or hotfix to the issue at hand.
Best Regards,
I solve the issue using steam --reset; some users says that modifying their configs after the reset was causing the problem to come back, but that was not my case. Now just works fine
I did the steam --reset as well, but had issues launching games. I ended up doing a second steam --reset and turning off beta and back to working. Will monitor issue and turn beta back on once resolved.
Ran steam --reset. Started Steam, closed it and started again and the issue reappeared.
I solve the issue using
steam --reset; some users says that modifying their configs after theresetwas causing the problem to come back, but that was not my case. Now just works fine
Update: The issue come back, I opt-in the beta program and the issue reappeared, also, in the non-beta I can not launch proton games (Like The Binding of Isaac: Repentance) but Natives games works fine (Like Team Fortress 2)
[...] also, in the non-beta I can not launch proton games (Like The Binding of Isaac: Repentance)
You will need to reenable "Enable Steam Play for all other titles" in Settings -> Steam Play.
eed to reenable "Enab
I already do that, the game keeps in the "launching" steam popup
looks like have same problem https://github.com/ValveSoftware/steam-for-linux/issues/7477#issuecomment-848937887
steam --reset worked (after i delete ~/.steat/steam.sh`, without this it fails)
Effect to me also. I've been done already twice, going to third round. Between resets, I can play my game two or three times and after that this issue will reappeared.
hopefully you can fix this issue soon.
edit, Linux WO Ubuntu 21.04 64-bit. No problems in four five days. 02.06.2021
On Ubuntu 20.04 is crashed too when beta is enabled.
assert_20210529095847_20.dmp[71271]: response: CrashID=bp-25fe323e-87b0-4e70-bd1f-7cab92210528
assert_20210529095847_20.dmp[71271]: file ''/tmp/dumps/assert_20210529095847_20.dmp'', upload yes: ''CrashID=bp-25fe323e-87b0-4e70-bd1f-7cab92210528''
assert_20210529095844_1.dmp[71275]: Finished uploading minidump (out-of-process): success = yes
assert_20210529095844_1.dmp[71275]: response: CrashID=bp-78e369f1-971e-4864-a1a3-fdbe72210528
assert_20210529095844_1.dmp[71275]: file ''/tmp/dumps/assert_20210529095844_1.dmp'', upload yes: ''CrashID=bp-78e369f1-971e-4864-a1a3-fdbe72210528''```Same problem here in Fedora 34 (AMD Radeon 5700, kernel 5.10.23).
Running steam --reset works exactly once, but since I need to restart after enabling proton for all titles this workaround is useless to me.
Leaving the beta is the workaround for me now.
I appear to have hit this same issue on the stable client from the update today.
It's hitting me on NixOS with Steam stable and AMD GPU. --reset only fixes it for a single run then it crashes again. This makes Steam completely unusable for me.
Logs/dumps are in https://github.com/NixOS/nixpkgs/issues/124308#issuecomment-856404821
The same issue appeared on stable Steam on Arch Linux, too, after today's client update. steam-native crashes with the same error as above. steam-runtime still works, though.
Exact same problem here also on Arch. I had already switched away from beta about a week ago to avoid it but it seems like today's update pushed it out to stable. Installing lib32 pipewire didn't work for me. steam-runtime is working though.
Same issue here. Steam is completely broken now, both in beta and stable.
I can fix it again by running steam --reset but it will only work as long as I don't restart Steam again. As soon as it finishes downloading all shaders it stops working again.
@kisak-valve Is it possible to rollback that update on Linux for now? I can't play anything with Proton right now.
steam --reset doesn't work. I can't launch steam at all. I'm attaching the dumps
For reference, the attached minidumps are a SIGSEGV in steamclient.so and a DUMP_REQUESTED in crashhander.so.
For reference, Pop_OS 21.04 with the same issue right now - can't run Steam at all.
I do have a very... artisanal override of PipeWire on my system.
It's crashing in Flatpak for me too.
dumps.tar.gz
edit: this should not have worked. I installed libnm0:i386, no change. reverted my pipewire from self-installed to Hirsute Upstream, rebooted, it's working?
edit 2: aaaand nope.
Early this year the client beta was crashing on Ubuntu 21.04 flatpak, now the last stable update get this problem too.
Most likely Valve is doing something backend changes ... What I learned is that I did have problems few days, steam --reset did helped for while. But now I don't have any problems launching steam linux client without problem one week now.
Im on generic ubuntu 20.04 LTS and am also seeing the same issue.
steam --reset lets it run once, and after a restart of steam its dead, both beta and stable.
I see many people report that steam --reset lets it run once. It doesn't do that for me. My error messages are mostly the same as the original poster (missing symbol in libdconfsettings, assertion failure in utlmemory.h) but in addition there's a failure to connect to the X session manager.
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Loaded SDL version 2.0.15-6501165
Gtk-Message: 18:20:55.155: Failed to load module "overlay-scrollbar"
Gtk-Message: 18:20:55.156: Failed to load module "atk-bridge"
(steam:209083): Gtk-WARNING **: 18:20:55.165: Unable to locate theme engine in module_path: "adwaita",
(steam:209083): Gtk-WARNING **: 18:20:55.165: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.166: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.167: Unable to locate theme engine in module_path: "pixmap",
(steam:209083): Gtk-WARNING **: 18:20:55.168: Unable to locate theme engine in module_path: "adwaita",
Gtk-Message: 18:20:55.168: Failed to load module "canberra-gtk-module"
Steam: An X Error occurred
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 20 (X_GetProperty)
Atom id in failed request: 0x0
Serial number of failed request: 12
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 20 (X_GetProperty)
Atom id in failed request: 0x0
Serial number of failed request: 13
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 20 (X_GetProperty)
Atom id in failed request: 0x0
Serial number of failed request: 14
xerror_handler: X failed, continuing
Installing breakpad exception handler for appid(steam)/version(1623096420)
Could not connect to X session manager: Authentication Rejected, reason : MIT-MAGIC-COOKIE-1 authentication rejected
[0608/182055.511882:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: browser
[0608/182055.528412:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[0608/182055.528460:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1623094080
[0608/182055.528464:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[0608/182055.528468:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_log_structured_standard
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
[0608/182055.562922:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[0608/182055.562990:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1623094080
[0608/182055.562997:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[0608/182055.563002:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
[0608/182055.563651:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: gpu-process
[0608/182055.646292:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[0608/182055.646364:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1623094080
[0608/182055.646371:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[0608/182055.646374:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
[0608/182055.646913:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: utility
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
CAppInfoCacheReadFromDiskThread took 77 milliseconds to initialize
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
CApplicationManagerPopulateThread took 6458 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Installing breakpad exception handler for appid(steam)/version(1623096420)
Proceed to auto login
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
Installing breakpad exception handler for appid(steam)/version(1623096420)
assert_20210608182102_23.dmp[209235]: Uploading dump (out-of-process)
/tmp/dumps/assert_20210608182102_23.dmp
Installing breakpad exception handler for appid(steam)/version(1623096420)
assert_20210608182053_1.dmp[209239]: Uploading dump (out-of-process)
/tmp/dumps/assert_20210608182053_1.dmp
/home/harald/.steam/steam.sh: line 772: 209083 Segmentation fault (core dumped) $STEAM_DEBUGGER $DEBUGGER_ARGS "$STEAMROOT/$STEAMEXEPATH" "$@"
assert_20210608182102_23.dmp[209235]: Finished uploading minidump (out-of-process): success = yes
assert_20210608182102_23.dmp[209235]: response: CrashID=bp-b7316f1e-1ec4-4fc0-8106-f84c92210608
assert_20210608182102_23.dmp[209235]: file ''/tmp/dumps/assert_20210608182102_23.dmp'', upload yes: ''CrashID=bp-b7316f1e-1ec4-4fc0-8106-f84c92210608''
assert_20210608182053_1.dmp[209239]: Finished uploading minidump (out-of-process): success = yes
assert_20210608182053_1.dmp[209239]: response: CrashID=bp-958bbe20-2303-4154-9f0f-e20572210608
assert_20210608182053_1.dmp[209239]: file ''/tmp/dumps/assert_20210608182053_1.dmp'', upload yes: ''CrashID=bp-958bbe20-2303-4154-9f0f-e20572210608''
Dont click "remember my password".... this is working for me now.
After trying a whole bunch of different things (mostly kernel version and nvidia driver) as there was an apt update I did last week that included a kernel jump from 5.4.0-73 to 5.4.0-74, i've found one solution that works on my machine and its quite simple - dont click "Remember my password" (you have to login each time you start steam obv, but much less annoying than steam not working at all).
My steam client now starts up fine and i annoyingly have to login every time, but its not crashing anymore.
Longer version: I remembered that last time i'd rebooted my laptop was after an apt update that included the kernel update. First I tried different nvidia drivers and no change (though the steamlink app also died when i tried using that as well - nvidia 465 drivers were the culprit).
I then tried rolling back the kernel to 5.4.0-73 and that appeared to be working so I rolled everything back to what I had prior to that 5.4.0-74 kernel update and it was all working until I clicked "Remember my password", then it stopped again.
Rolled everything back forward to the most current updates in ubuntu, did a steam --reset again and as long as i dont click "Remember my password", its been fine.
I see many people report that steam --reset lets it run once. It doesn't do that for me. My error messages are mostly the same as the original poster (missing symbol in libdconfsettings, assertion failure in utlmemory.h) but in addition there's a failure to connect to the X session manager.
There is one thing in your log that in my case was part of the issue:
Proceed to auto login
Suggests to me that steam --reset isnt actually properly resetting you as it shouldn't have any auto-login details and for me at least, getting rid of the auto-login has stopped the client crashing.
Also happening here. steam --reset lets me actually start steam again, and it will continue to start if I don't check "remember my password." This happens both with and without the beta enabled. Pretty horrible bug, hope there's something in the works soon.
Ubuntu 21.04 Pop variant, getting a painful
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
here as well.
I can confirm leaving "remember password" unchecked is a functional (but annoying) workaround.
Hmm now it's crashing after just being open for a few minutes, so seems even without checking "remember password" you still need to reset to actually play anything.
windows > linux btw
Yup, I confirm this. Reset and leaving "remember passwords" unchecked works.
For Flatpak users, you can do this on the terminal, on the current user account.
flatpak run com.valvesoftware.Steam --reset
Steam Native Arch fix: https://bugs.archlinux.org/task/71092#comment200392
Excellent! I can confirm that building and installing the lib32-libnm referred above fixes steam-native on Arch Linux!
Can confirm same problem here on Fedora 32 64-bit.
Can also confirm that steam --reset allows me to run Steam again properly.
Hi guys, unclicked "remember my password" works for me.
If you like, please see https://github.com/ValveSoftware/steam-for-linux/issues/7477#issuecomment-857339782
Hi guys, I somehow figure out this problem.
It's a (known) workaround, not a fix.
I think that we are seeing two separate bugs here, which manifest themselves in the same way, with very similar error messages: one that is fixed by adding a missing 32-bit networkmanager library (lib32-libnm in Arch), and one that requires people to run steam --reset and occasionally not to save their credentials.
My steam updated last night, and since then I can't start it anymore, this is gdb output:
[2021-06-09 09:40:31] Verification complete
Thread 1 "steam" received signal SIGTRAP, Trace/breakpoint trap.
0xef1901e6 in ?? () from /home/pieter/.steam/ubuntu12_32/vgui2_s.so
(gdb) backtrace
#0 0xef1901e6 in ?? () from /home/pieter/.steam/ubuntu12_32/vgui2_s.so
#1 0xf7c64bcf in _XError () from /usr/lib/i386-linux-gnu/libX11.so.6
#2 0xf7c617bc in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
#3 0xf7c62ba9 in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
#4 0xf7c47ec2 in XGetWindowProperty () from /usr/lib/i386-linux-gnu/libX11.so.6
#5 0xf25c701f in ?? () from /home/pieter/.steam/ubuntu12_32/steamui.so
#6 0xf25c76cd in ?? () from /home/pieter/.steam/ubuntu12_32/steamui.so
#7 0xf25c9882 in ?? () from /home/pieter/.steam/ubuntu12_32/steamui.so
#8 0xf2789bbc in ?? () from /home/pieter/.steam/ubuntu12_32/steamui.so
#9 0x56592430 in ?? ()
[#10](/issue/ValveSoftware/steam-for-linux/10) 0x565933c3 in ?? ()
[#11](/issue/ValveSoftware/steam-for-linux/11) 0x5657c92e in ?? ()
[#12](/issue/ValveSoftware/steam-for-linux/12) 0xf7952ee5 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
[#13](/issue/ValveSoftware/steam-for-linux/13) 0x56581229 in _start ()
(gdb)
Steam native runtime has been update on Arch, so the issue is maybe already fixed.
Steam also crashes during shader caching now after a fresh steam --reset. Although it still starts after that, assuming I didn't remember my login.
This is the log of a fresh steam start after a reset, just logging in and letting the shaders download for ~10 minutes:
https://gist.github.com/DomiStyle/82123a3ad608fee1c9dfc008296cba5d
I can confirm that one, running Steam on Manjaro 21.0.6, and sincey yesterday's update, Steam started crashing on launch (this is running steam-manjaro package, by the way, which uses Steam's own runtime, as opposed to steam-native).
At first I was clearing out the entire .local/share/Steam, which would allow me to launch it once, then it'd start crashing again.
After steam --reset and making sure I don't check "Remember the password", it launches, albeit I need to put my credentials in every time.
On Fedora, I've been able to start Steam without issue, even with "Remember password" checked, after installing libnm.so.0. This persists after rebooting my machine, as well. I did see Steam crash when compiling the Vulkan shaders so I've unchecked that option and don't appear to be having any issues anymore.
On NixOS, overriding the steam package to add networkmanager to extraLibraries fixes the crasher for me
Steam version: 1623193086
Steam runtime: 0.20210126.2
On Ubuntu 20.04 LTS, presence of libnm.so.0 does not seem to matter.
> ldconfig -p | grep libnm
libnma.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnma.so.0
libnm.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnm.so.0
libnm.so.0 (libc6) => /usr/lib/i386-linux-gnu/libnm.so.0
libnm-util.so.2 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnm-util.so.2
libnm-gtk.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnm-gtk.so.0
libnm-glib.so.4 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnm-glib.so.4
All attempts to run steam --reset did not help, autologin error continued to appear.
Fixed by editing ~/.steam/registry.vdf and changing "RememberPassword" from "1" -> "0"
Please try to keep separate issues separate, if you can - I think we might have several different crashes happening here, on several different OSs and configurations.
Some general words about this, not specifically dealing with any of the crashes:
A supported installation of Steam requires using the copy of the Steam Runtime that comes with Steam (specifically ~/.steam/root/ubuntu12_32/steam-runtime, which is distributed as steam-runtime.tar.xz.part{0,1,2} and is unpacked by Steam's wrapper shell script). The Steam Runtime provides 32- and 64-bit copies of all of the required libraries except for glibc and graphics drivers like Mesa: in particular it includes the libpipewire-0.3.so.0 and libnm.so.0 that have been mentioned in this issue report.
Valve specifically does not support installations that do not use this copy of the Steam Runtime, such as Arch Linux's steam-native. If you are using steam-native or similar, then it is up to the maintainers of that runtime environment to make it fully ABI-compatible with the current version of the Steam Runtime. In recent versions of Steam this means you will need 32- and 64-bit libnm.so.0 and libpipewire-0.3.so.0, among others.
If you are not running Steam in a container or chroot (like typical installations on Debian or Arch), then for each (library SONAME, word size) pair, Steam will use either the version from the operating system or the version from the Steam Runtime, whichever one is newer. There are a few exceptions where for ABI compatibility reasons, the Steam Runtime version always needs to be used, even if the operating system copy is newer (currently this means libcurl, 32-bit libdbus, 32-bit libdbusmenu and 32-bit GTK 2).
If you are running Steam in a container or chroot (like Flatpak and NixOS) then it's the same as the non-container situation, except the versions from the container are used instead of the versions from the operating system.
Normally, I'd ask people who are experiencing a bug to include their Help -> System Information contents. If Steam is crashing on startup, obviously you can't get that. However, there is some useful information you can provide:
What version of Steam? For example if you run it from a terminal and you see something like appid(steam)/version(1621893676), then you're using version 1621893676. The current version at the time I'm writing this comment is 1623193086 (meaning 2021-06-08 22:58:06, according to date -d '@1623193086' --utc), which is in both the beta and stable branches.
What version of the Steam Runtime? This is in ~/.steam/root/ubuntu12_32/steam-runtime/version.txt. The current version at the time I'm writing this comment is 0.20210518.3.
When you are still in the situation where it crashes, does the diagnostic tool report any problems? Normally you'd get this from Help -> System Information, but if Steam isn't starting up correctly, here's how to run it the hard way, without needing to launch Steam:
~/.steam/root/ubuntu12_32/steam-runtime/setup.sh
~/.steam/root/ubuntu12_32/steam-runtime/run.sh steam-runtime-system-info > srsi.txt
After running those commands, srsi.txt will contain most of the same information that would be in Help -> System Information. In particular, look for library-issues-summary and issues, which indicate potential problems with your setup. If you run it like this, it's normal that it will say
"steam-installation" : {
"issues": [
"steamscript-not-in-environment"
]
}
so you can ignore that one.
If you run it with the --verbose argument:
~/.steam/root/ubuntu12_32/steam-runtime/setup.sh
~/.steam/root/ubuntu12_32/steam-runtime/run.sh steam-runtime-system-info --verbose > srsi.txt
then for each of the libraries we're interested in, it will tell you which copy of that library it is using. For example, on an Arch test system where I'm using the Steam Runtime's 64-bit libudev.so.0 but using Arch's newer libusb-1.0.so.0, I get:
"libudev.so.0" : {
"soname" : "libudev.so.0",
"path" : "/home/me/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64/libudev.so.0",
}
"libusb-1.0.so.0" : {
"soname" : "libusb-1.0.so.0",
"path" : "/usr/lib/libusb-1.0.so.0",
}
Unfortunately libpipewire-0.3.so.0 is not currently checked like this (see ValveSoftware/steam-runtime#419 for a workaround). The next Steam Runtime update, versioned 0.20210608.1 or later, should fix this.
If you run ~/.steam/root/ubuntu12_32/steam-runtime/setup.sh --force and then try again, does that work around the problem?
If you can work around the crash by installing extra libraries, what specific versions of those extra libraries work around the crash? For example if you're on Ubuntu 20.04 and can work around a crash by installing libnm0:i386, you might say "I installed libnm0:i386 version 1.22.10-1ubuntu2.2 and it worked around this".
If you can work around the crash somehow (by installing extra libraries or by running setup.sh --force or any other method), it would be helpful to get a steam-runtime-system-info --verbose report without the workaround, get a similar steam-runtime-system-info --verbose report with the workaround, and do a diff between them.
If you are encountering a crash that can be resolved by installing an additional library, then there are several possible root causes:
steam-native). Valve does not support this configuration and cannot help you.libpipewire-0.3.so.0, but then shipped as a beta without also updating the Steam Runtime. This bug was fixed in a subsequent beta, and I don't think the stable (general availability) branch was ever affected.appid(steam)/version(1623193086)
steam-runtime_0.20210518.3
$ ~/.steam/root/ubuntu12_32/steam-runtime/setup.sh
Pins up-to-date!
$ ~/.steam/root/ubuntu12_32/steam-runtime/run.sh steam-runtime-system-info > srsi.txt
All occurrences of library-issues-summary are empty arrays.
issues has a few though:
"steam-installation" : {
"issues" : [
"steamscript-not-in-environment",
"unexpected-steam-uri-handler",
"unexpected-steam-desktop-id"
]
"architectures" : {
"i386-linux-gnu" : {
"x11/vdpau" : {
"issues" : [
"cannot-draw"
]
},
"x11/vaapi" : {
"issues" : [
"cannot-draw"
]
}
}
}
"xdg-portals" : {
"issues" : [
"missing-interface",
"no-implementation"
],
"messages" : [
"Failed to connect to 'org.freedesktop.portal.Desktop'",
"Failed to connect to 'org.freedesktop.portal.Desktop'",
"There isn't a working portal implementation"
]
},
Libraries used by Steam but not provided by Steam Runtime:
https://gist.github.com/Maykin-99/672c64f2dd1dab77965120e8a63ae513
$ ~/.steam/root/ubuntu12_32/steam-runtime/setup.sh --force
Found newer runtime version for 32-bit libudev.so.0. Host: 0.0.9999 Runtime: 0.13.0
Forced use of runtime version for 32-bit libdbus-1.so.3. Host: 3.19.13 Runtime: 3.5.8
Found newer runtime version for 64-bit libudev.so.0. Host: 0.0.9999 Runtime: 0.13.0
Found newer runtime version for 32-bit libGLU.so.1. Host: 1.3.1 Runtime: 1.3.8004
Forced use of runtime version for 32-bit libgtk-x11-2.0.so.0. Host: 0.2400.33 Runtime: 0.2400.10
Forced use of runtime version for 32-bit libcurl.so.4. Host: 4.7.0 Runtime: 4.2.0
Forced use of runtime version for 32-bit libdbusmenu-glib.so.4. Host: 4.0.12 Runtime: 4.0.13
Forced use of runtime version for 32-bit libdbusmenu-gtk.so.4. Host: 4.0.12 Runtime: 4.0.13
Found newer runtime version for 64-bit libGLU.so.1. Host: 1.3.1 Runtime: 1.3.8004
Forced use of runtime version for 64-bit libcurl.so.4. Host: 4.7.0 Runtime: 4.2.0
Found newer runtime version for 64-bit libdbusmenu-glib.so.4. Host: 4.0.12 Runtime: 4.0.13
Found newer runtime version for 64-bit libdbusmenu-gtk.so.4. Host: 4.0.12 Runtime: 4.0.13
Still crashes when running steam-runtime.
Same here on arch linux (manjaro). steam --reset makes it work the first time but if i save the password it starts to crash again.
same issue on ubuntu 20.04.02 after the last steam update.
stream --reset not works
I confirm - steam crashes with the "Segmentation fault" after the restart. steam --reset works only once. Moreover, after the reset, I've lost all my configurations in some games and had to download some games again.
Thank you for the suggestion above - I'll try not to save the password
@smcv : to address your request, note that similar issues on other distros (such as #7853 ), are getting closed by (what I understand are) the maintainers, so it is a bit hard to fulfill.
Also, since the issue definitely appears to affect the stable release now, would you consider adding this: https://github.com/ValveSoftware/steam-for-linux/issues/7813?_pjax=%23js-repo-pjax-container#issuecomment-857834053 to the list of possible workarounds, as it appears to work for at least a number of people?
[worked around] by editing
~/.steam/registry.vdfand changing"RememberPassword"from"1"->"0"
This seems to be the least destructive workaround available right now for one of the issues that a lot of people are experiencing.
There are at least four reasons seen recently for a crash on startup, and maybe more. Not everyone who sees Steam crashing will be experiencing the same thing: there are lots of reasons a large program can crash.
libnm:ERROR:libnm-core/nm-setting-wireless-security.c:837:need_secrets: code should not be reached. That's #7832.
libnm0:i386 (Debian/Ubuntu), lib32-libnm (Arch), or some other way to get a 32-bit libnm.so.0, then installing that will work around this problem.src/public/tier1/utlmemory.h (176) : Assertion Failed: 0. I think this is what most of the people here and on #7847 are seeing.
~/.steam/registry.vdf and changing "RememberPassword" from "1" to "0" seems to avoid this.libpipewire-0.3.so.0 (#7807). This was fixed, and you should not be seeing this one any more.steam-native or STEAM_RUNTIME=0 or other mechanisms that bypass the Steam Runtime. This is not supported by Valve, and is unlikely to help you to avoid the issues described here; it's more likely to cause new failures.I'm running debian sid here and can confirm that setting RememberPassword to "0" fixes crash on both beta and non-beta :)
Yay! I can play BL3 again. If any devs want to use my Machine to debug this I'm happy help.
We have made some changes that may affect the utlmemory.h abort in today's Steam beta client update (June 11th). Please re-test with Steam beta and report if the crash is still present and the RememberPassword workaround still needed for you.
$ steam-runtime
Running Steam on arch rolling 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Steam client's requirements are satisfied
WARNING: Using default/fallback debugger launch
/opt/games/Steam/ubuntu12_32/steam
[2021-06-11 23:21:59] Startup - updater built Jun 11 2021 19:28:45
[2021-06-11 23:21:59] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
Installing breakpad exception handler for appid(steam)/version(1623445000)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2021-06-11 23:21:59] Loading cached metrics from disk (/opt/games/Steam/package/steam_client_metrics.bin)
[2021-06-11 23:21:59] Using the following download hosts for Public, Realm steamglobal
[2021-06-11 23:21:59] 1. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf'
[2021-06-11 23:21:59] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf'
[2021-06-11 23:21:59] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
Installing breakpad exception handler for appid(steam)/version(1623445000)
[2021-06-11 23:21:59] Checking for update on startup
[2021-06-11 23:21:59] Checking for available updates...
[2021-06-11 23:21:59] Downloading manifest: https://cdn.akamai.steamstatic.com/client/steam_client_publicbeta_ubuntu12
Installing breakpad exception handler for appid(steam)/version(1623445000)
[2021-06-11 23:21:59] Download skipped by HTTP 304 Not Modified
[2021-06-11 23:21:59] Nothing to do
[2021-06-11 23:21:59] Verifying installation...
[2021-06-11 23:21:59] Performing checksum verification of executable files
[2021-06-11 23:21:59] Verification complete
Loaded SDL version 2.0.15-6501165
(steam:355982): Gtk-WARNING **: 23:22:00.071: Unable to locate theme engine in module_path: "adwaita",
/usr/share/themes/Adwaita-dark/gtk-2.0/main.rc:733: error: unexpected identifier 'direction', expected character '}'
(steam:355982): Gtk-WARNING **: 23:22:00.072: Unable to locate theme engine in module_path: "adwaita",
/usr/share/themes/Adwaita-dark/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant
Steam: An X Error occurred
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 20 (X_GetProperty)
Atom id in failed request: 0x0
Serial number of failed request: 12
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 20 (X_GetProperty)
Atom id in failed request: 0x0
Serial number of failed request: 13
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 20 (X_GetProperty)
Atom id in failed request: 0x0
Serial number of failed request: 14
xerror_handler: X failed, continuing
Installing breakpad exception handler for appid(steam)/version(1623445000)
STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy
[0611/232200.276455:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: browser
[0611/232200.306316:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[0611/232200.306373:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1623439753
[0611/232200.306377:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[0611/232200.306381:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
/usr/lib/gio/modules/libdconfsettings.so: undefined symbol: g_log_structured_standard
Failed to load module: /usr/lib/gio/modules/libdconfsettings.so
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
[0611/232200.339728:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[0611/232200.339776:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1623439753
[0611/232200.339780:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[0611/232200.339786:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
[0611/232200.340213:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: gpu-process
[0611/232200.403894:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process.
[0611/232200.431687:WARNING:crash_reporting.cc(286)] Failed to set crash key: UserID with value: 0
[0611/232200.431740:WARNING:crash_reporting.cc(286)] Failed to set crash key: BuildID with value: 1623439753
[0611/232200.431746:WARNING:crash_reporting.cc(286)] Failed to set crash key: SteamUniverse with value: Public
[0611/232200.431751:WARNING:crash_reporting.cc(286)] Failed to set crash key: Vendor with value: Valve
[0611/232200.432221:INFO:crash_reporting.cc(247)] Crash reporting enabled for process: utility
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
CApplicationManagerPopulateThread took 171 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
CAppInfoCacheReadFromDiskThread took 623 milliseconds to initialize
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
Proceed to auto login
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
Installing breakpad exception handler for appid(steam)/version(1623445000)
Installing breakpad exception handler for appid(steam)/version(1623445000)
assert_20210611232201_20.dmp[356241]: Uploading dump (out-of-process)
/tmp/dumps/assert_20210611232201_20.dmp
Installing breakpad exception handler for appid(steam)/version(1623445000)
assert_20210611232159_1.dmp[356246]: Uploading dump (out-of-process)
/tmp/dumps/assert_20210611232159_1.dmp
/opt/games/Steam/steam.sh: Zeile 772: 355982 Speicherzugriffsfehler (Speicherabzug geschrieben) $STEAM_DEBUGGER $DEBUGGER_ARGS "$STEAMROOT/$STEAMEXEPATH" "$@"
maykin:~ $ assert_20210611232159_1.dmp[356246]: Finished uploading minidump (out-of-process): success = yes
assert_20210611232159_1.dmp[356246]: response: CrashID=bp-f167c88b-71de-42a2-87a8-a85ac2210611
assert_20210611232159_1.dmp[356246]: file ''/tmp/dumps/assert_20210611232159_1.dmp'', upload yes: ''CrashID=bp-f167c88b-71de-42a2-87a8-a85ac2210611''
assert_20210611232201_20.dmp[356241]: Finished uploading minidump (out-of-process): success = yes
assert_20210611232201_20.dmp[356241]: response: CrashID=bp-ed877c0d-48fb-43a0-b527-deab82210611
assert_20210611232201_20.dmp[356241]: file ''/tmp/dumps/assert_20210611232201_20.dmp'', upload yes: ''CrashID=bp-ed877c0d-48fb-43a0-b527-deab82210611''
The interesting thing is that the X Error still happens when the browser
runs ok.
This is when it's working and remember password is not ticked.
Thanks - are you using the 32 bit libnm library from your host/distribution, or the one from the steam runtime?
e.g. if you have libnm0:i386 installed (Debian/Ubuntu) or lib32-libnm installed (Arch), can you uninstall it and try to repro again. And vice versa if you don't have it installed..
lib32-libnm (on Arch) wasn't installed. I installed it, but no change.
Dear TTimo,
No apparent change with the library removed.
The following packages will be REMOVED:
libnm0:i386
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 1,658 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 473215 files and directories currently installed.)
Removing libnm0:i386 (1.30.0-2) ...
Processing triggers for libc-bin (2.31-12) ...
Hello @0ryn, the logs you are inlining with your comments have negative value and just make it more difficult to discuss this issue. Please use a gist (https://gist.github.com) or other pastebin service and share a link when attaching logs instead of copy/pasting the log inline with the rest of your feedback.
@0ryn so far we cannot reproduce, but indeed I suspect there is something unusual in your network interfaces list/configuration that is crashing the Steam client.
I have VMWare Workstation installed.
I'll uninstall it
BRB
On 11/06/2021 23:26, TTimo wrote:
@0ryn https://github.com/0ryn so far we cannot reproduce, but indeed
I suspect there is something unusual in your network interfaces
list/configuration that is crashing the Steam client.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7813#issuecomment-859938927,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS46QBOO3HE3AAHGVA3HCTTSKEQVANCNFSM45QEURBQ.
can you send me the output of nmcli privately maybe - there might be something there that will stand out
I suspect there is something unusual in your network interfaces list/configuration that is crashing the Steam client.
@TTimo I guess, this is unusual to have a dozen of bridge networks configured;) It isn't for me.
Jokes aside, thanks for the tip. I've deleted all bridge networks created by docker and Boxes VMs on Fedora and the issue is gone. I'm using the latest stable runtime.
I'm going to try to add those back and see when it is going to fail again.
thanks I think that puts us on the right track
I removed VMWare Workstation so no effect but the log looks slightly
different.
I have a more useful error.
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
Installing breakpad exception handler for appid(steam)/version(1623445000)
crash_20210611235603_21.dmp[72124]: Uploading dump (out-of-process)
/tmp/dumps/crash_20210611235603_21.dmp
src/public/tier1/utlvector.h (1216) : Assertion Failed: !pArray ||
(Base() >= (pArray + size)) || (pArray >= (Base() + Count()) )
src/public/tier1/utlvector.h (1216) : Assertion Failed: !pArray ||
(Base() >= (pArray + size)) || (pArray >= (Base() + Count()) )
src/public/tier1/utlvector.h (1208) : Assertion Failed: count >= 0
src/public/tier1/utlvector.h (1208) : Assertion Failed: count >= 0
double free or corruption (!prev)
On 11/06/2021 23:35, TTimo wrote:
can you send me the output of |nmcli| privately maybe - there might be
something there that will stand out—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7813#issuecomment-859941516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS46QF7GRQWZ24VW3STL63TSKFSJANCNFSM45QEURBQ.
I suspect there is something unusual in your network interfaces list/configuration that is crashing the Steam client.
@TTimo I guess, this is unusual to have a dozen of bridge networks configured;) It isn't for me.
Jokes aside, thanks for the tip. I've deleted all bridge networks created by docker and Boxes VMs on Fedora and the issue is gone. I'm using the latest stable runtime.
I'm going to try to add those back and see when it is going to fail again.
I guess that explains my crashes before adding libnm to the Steam container, I'm running k3s on my machine lol
I've masked my V6 address I don't care about exposing my V4 Nat'ed address
https://gist.github.com/0ryn/011c45df138a4d6d5ee89609e4427da0
On 11/06/2021 23:35, TTimo wrote:
can you send me the output of |nmcli| privately maybe - there might be
something there that will stand out—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7813#issuecomment-859941516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS46QF7GRQWZ24VW3STL63TSKFSJANCNFSM45QEURBQ.
So, moved from this config with the issue being reproduced
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c0:b8:83:c7:22:f2 brd ff:ff:ff:ff:ff:ff
inet 192.168.13.155/24 brd 192.168.13.255 scope global noprefixroute wlp0s20f3
valid_lft forever preferred_lft forever
inet6 ... scope link noprefixroute
valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:33:f2:b5 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
12: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:34:71:c0:3e brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
4: br-1b88c179a929: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:6c:09:54:22 brd ff:ff:ff:ff:ff:ff
inet 172.27.0.1/16 brd 172.27.255.255 scope global br-1b88c179a929
valid_lft forever preferred_lft forever
... more like the last one
to this with no issues
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether c0:b8:83:c7:22:f2 brd ff:ff:ff:ff:ff:ff
17: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:5d:3d:52:71 brd ff:ff:ff:ff:ff:ff
18: br-5d334bd3a9f5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:b9:58:20:03 brd ff:ff:ff:ff:ff:ff
The only difference I see is virbr0 network. Unfortunately, I cannot remember why it was there. Sorry.
It looks like I'm unable to return to a reproducable state.
Even with just localhost as the only active interface I still get a crash
https://gist.github.com/0ryn/011c45df138a4d6d5ee89609e4427da0
On 12/06/2021 00:08, Jonathan Baldwin wrote:
I suspect there is something unusual in your network interfaces list/configuration that is crashing the Steam client. @TTimo <https://github.com/TTimo> I guess, this is unusual to have a dozen of bridge networks configured;) It isn't for me. Jokes aside, thanks for the tip. I've deleted all bridge networks created by docker and Boxes VMs on Fedora and the issue is gone. I'm using the latest stable runtime. I'm going to try to add those back and see when it is going to fail again.I guess that explains my crashes before adding libnm to the Steam
container, I'm running k3s on my machine lol—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7813#issuecomment-859950886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS46QGGW6P6INTZTSZYIB3TSKJQHANCNFSM45QEURBQ.
Thanks, you saved my weekend.
I'm programmer and my OS (Elementary OS Linux) had many network interfaces, because of docker and other applications. I could never imagine this was the problem. So I removed all unused interfaces.
Look at the state it was in:
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> ...
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> ...
3: ham0: <BROADCAST,MULTICAST,UP,LOWER_UP> ...
4: br-ad7b8559838e: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
5: br-b4a155dba820: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
6: br-e98eec2aab8f: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
7: br-f7ee62fa2a90: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
8: br-8127a0be4866: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
9: br-8e381cb8bdad: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
10: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
11: br-e735982a640e: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
12: br-ece5e3a56919: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
13: br-12bdfbd03a52: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
14: br-170f38516e1c: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
15: br-2081c6aaf7d8: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
16: br-13aefcd99a65: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
17: br-6e697d20fd79: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
18: br-772d3523bc0e: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
I removed all inuseful interfaces (CAUTION: not remove your internet interface).
I used the command:
$ sudo ip link delete br-772d3523bc0e
Result:
$ ip a
1: lo: < LOOPBACK, UP, LOWER_UP > ...
2: enp4s0: < BROADCAST, MULTICAST, UP, LOWER_UP > ...
3: ham0: < BROADCAST, MULTICAST, UP, LOWER_UP > ...
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> ...
Now I can save the Steam login
EDIT
After restarting the computer the interfaces appeared again. So I confirmed that the docker was the creator, and then exec docker network rm $(docker network ls -q)
Ubuntu 20.04.2. Removing docker networks solves the issue when using both beta and stable. Remember password checkbox is also checked.
Arch: I can confirm that if I remove all Docker networks then Steam's Auto-Login works again.
killing all docker containers solved for me too
RememberPassword
Where can i set this option without turning on steam?
2. Another reason for Steam to crash on startup seems to involve letting Steam save your password. This often (always?) has the assertion message `src/public/tier1/utlmemory.h (176) : Assertion Failed: 0`. I think this is what _most_ of the people here and on [#7847](/issue/ValveSoftware/steam-for-linux/7847) are seeing.
I can confirm that on Fedora 34 removing ~.local/share/Steam/resource/registrykeys.vdf, forcing relogin without storing the password seems to solve the problem.
Thanks!
So for me I had to recompile my custom kernel removing support for ip6_gre. With ip6_gre built as a module and loaded The Steam Client fails. rmmod ip6_gre and it works again.
I can confirm same here. Ubuntu 20.04
Installing breakpad exception handler for appid(steam)/version(1623445000)
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
src/public/tier1/utlmemory.h (176) : Assertion Failed: 0
Installing breakpad exception handler for appid(steam)/version(1623445000)
crash_20210612220955_21.dmp[6780]: Uploading dump (out-of-process)
$ docker network prune
solve the problem (edit: workaround to run steam)
@FHenry That solves it for me, too. Thanks!
docker network prune is not a solution, it is a workaround.
@pohmelie don't be so meticulous 🧢
I am hitting this issue on Arch Linux with Network Manager and numerous additional network interfaces configured via Docker. It seems to be new, at least in my case, as I did not have the issue prior to yesterday. In case it's useful to Valve, this is my Docker configuration: https://gist.github.com/jlanzobr/83a9fb81e046446bffad40dd0e97c134
Although I've recently installed Docker along with x11docker in Arch Linux desktop, since I have not used Docker to run any graphical applications, I've decided to uninstall Docker and after I restart my computer, I tried to launch Steam with "Remember password' checked and Steam crashed, so I can eliminate Docker being the problem. However, I do have an unusual networking configuration. For my Linux home server, I have a virtual homelab for playing with network configuration using pfSense and VyOS (two router distributions), so that's where I use VLANs and bridges so that my desktop and server VMs can communicate through VLAN.
In nutshell, here are the list of bridges, VLANs, and a single interface that I currently have:
grayson@grayson-epcotcenter
~
$ ip link show | grep ethbr0 | awk '{printf $2}' | sed 's/:/\n/g'
enp5s0
ethbr0_2404
ethbr0_2402
ethbr0_2403
ethbr0_2400
ethbr0
ethbr0.2407@ethbr0
ethbr0.2408@ethbr0
ethbr0.2402@ethbr0
ethbr0.2401@ethbr0
ethbr0.2406@ethbr0
ethbr0.2400@ethbr0
ethbr0.2404@ethbr0
ethbr0.2405@ethbr0
ethbr0.2409@ethbr0
ethbr0.2403@ethbr0
ethbr0_2408
ethbr0_2401
ethbr0_2407
ethbr0_2405
ethbr0_2406
ethbr0_2409
enp5s0 is my 2.5Gbit Ethernet interface and ethbr0 bridges to enp5s0 Ethernet interface. All the VLANs were all assigned to the single bridge interface and each bridge is assigned per VLAN. ethbr0_2400 is assigned to ethbr0.2400@ethbr0, ethbr0_2401 is assigned to ethbr0.2401@ethbr0, and so on. Yes, my network configuration is unusual; however if I remove all the bridged interfaces, I will have to setup all the bridged interfaces again so that VMs with specific VLAN ID can communicate with VMs in my home server. Am I confusing anyone? Even for those who understand Linux and basic or advanced networking?
Anyway, as long as I do not have "Remember Password" checkbox checked, I should be able to launch Steam. At least I still have my password stored in my Bitwarden password manager, which can be a bit inconvenient, but workable. Steam does work well until recently with the "Remember password" checkbox checked until I get the latest update...
It' working again on Arch after updates today
It' working again on Arch after updates today
Not for me. I still need to kill all Docker containers and networks to start up Steam.
After today's update (1623532164) I can run Steam Client with ip6_gre loaded
On 13/06/2021 20:39, Maykin-99 wrote:
It' working again on Arch after updates todayNot for me. I still need to kill all Docker containers and networks to
start up Steam.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7813#issuecomment-860260183,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS46QG2Q7JBUT2E32EGHUDTSUCQJANCNFSM45QEURBQ.
@0ryn mine is still on its proverbial backside if I save my password. But I still have extra docker network devices, so.
I wasn't running any docker apps or such network devices in the first
place. But I did have lots of kernel built in network devices. I just
built everything into the kernel. Not that I needed it.
I just removed a bunch of stuff that I wasn't using and found that Steam
worked when I removed ip6_gre.
It works now with it loaded.
On 13/06/2021 23:39, Renaud Lepage wrote:
@0ryn https://github.com/0ryn mine is still on its proverbial
backside if I save my password. But I still have extra docker network
devices, so.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7813#issuecomment-860279982,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS46QDTBNF5U6TKNA5LX3LTSUXTJANCNFSM45QEURBQ.
The beta was updated today (June 13th - 1623682048) with another change that we think will address this (the root cause does not seem to be the actual network interfaces on your system, but how many there are to iterate through).
@TTimo I just pulled the latest update and it still crashed. The number of utlmemory.h failed asserts went down though.
I have 5 br- network devices, fwiw. (as well as 2 veth). Ubuntu 21.04 by way of Pop_OS, using KDE/KF5.
Same here on Ubuntu 21.04, still crashes on latest beta from June 13th.
I have same issue on ubuntu 20.04 with radeon rx5700xt gpu.
Have same error on Ubuntu 20.04
workarouned with
docker kill $(docker ps -q)
docker system prune
waiting for normal solution
We are aware of this and do not need new reports at the moment. Please don't add a "me too" comment unless you have significant new information.
The minimal workaround seems to be: edit ~/.steam/registry.vdf and change "RememberPassword" from "1" to "0".
Latest beta should fix this (Jun 16).
It's working. with latest beta, on ubuntu 20.04
with remember me password checked, even after I restart my computer, its still working.
thank you...
Second confirm, latest beta pulled from VALVe logs in fine with saved creds.
Confirmed.
What about non-beta users? When fix will lands mainstream?
What about non-beta users? When fix will lands mainstream?
When enough people have tried the beta to be confident that it doesn't break anything else.
I think this should be opened until that time.
Pardon my "me too" comment however I am able to confirm once I participate in the BETA program and choose to remember password. Once I have Steam remember password, I quit Steam, launched Steam again, and I am able to open Steam without being asked for password again since I have "Remember password" checked. I quit Steam again and opened it back up again in order to confirm I am able to open Steam without being prompted to login. So yes, I can confirm that it's working well.
Sorry if this is a "me too" comment, but running docker network prune and docker system prune -af --volumes did nothing, nor did steam --reset. I am running MicroK8s on my machine, and this command fixed it for me:
ip a | grep -o "cali[a-z0-9]\+" | xargs -I[] bash -c "echo []; sudo ip link delete []"
It's the MicroK8s equivalent of docker network prune. This is with the stable client, and with auto-login enabled.
For me steam works fine until I select to run steam play / proton in settings. Even on completely clean installation enabling proton causes steam to stop running again.
I confirm, docker network prune, did the trick, I assume we hit some kind of limit ?
My understanding is that there isn't a specific number that is safe or not safe, but the more network interfaces you have, the more likely it is that the crash will happen.
Your system information
Please describe your issue in as much detail as possible:
Steam does not start up when opting in to beta. Opting out by removing
~/.steam/steam/package/betaworks fine though.When issue #7807 was raised, I simply installed
lib32-pipewirefrom AUR, but since today the Beta seems to be completly broken now. I already uninstalledlib32-pipewireagain but it resulted in no change to the current issue.Output: