Your system information

• Steam client version (build number or date): Unsure and I can't check. I believe the latest version.
• Distribution (e.g. Ubuntu): Manjaro 20.2 with Plasma 5.20 desktop. Running Kernel version 5.4.85-1 with Nvidia driver version 455.45.01-6.
• Opted into Steam client beta?: Yes
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Updated computer to latest patch a few days ago as normal. Rebooted to get the new updates running. Steam is part of my launch applications, expected it to start right away, but it doesn't. Tried to launch from the application icon on the desktop. The busy symbol appears for a couple of seconds, then it stops. I checked the system monitor, there's no Steam process anywhere to be seen. Then tried to launch from a bash shell. Got the following output:

Running Steam on manjarolinux 20.2 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Steam client's requirements are satisfied
/home/tooney/.local/share/Steam/ubuntu12_32/steam

After that it immediately goes back to the command prompt. No errors, no indication that anything shouldn't be working.

I ran strace setting it to follow child processes and put files into context. The output of that is here: https://gist.github.com/Tooney712/e43c7d0899148386170d2af311baab11

From what I could understand of the strace output, it looks like the 'steam.sh' script is running through perfectly fine (hence the bash output containing no errors), but when it goes to actually start steam proper, the process loads the necessary libraries and then kills itself(???), exiting with a zero, and thus, no errors, with the steam script exiting with zero soon after. I could be completely wrong and off base though, I am very new to a lot of these things.

Tried to run gdb with the debug symbol libraries, but it won't accept 'steam.sh' as a valid application to start up, and I'm not sure how to set up a script for it to automatically grab the actual steam process when it starts, so I don't have any output from that. Also tried to run ltrace, but it kept spitting "incorrect file type" errors at me, I assume for the same reasons gdb wouldn't accept the steam shell script.

Steps for reproducing this issue:

1. I guess have my system set up (manjaro 20.2, kernel 5.4.85-1, etc).
2. Attempt to run Steam either from the desktop or the terminal.
3. Wait to see if the Steam client window actually appears.