ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.21k stars 174 forks source link

steamwebhelper repeatedly crashes #9706

Open salarua opened 1 year ago

salarua commented 1 year ago

Your system information

Please describe your issue in as much detail as possible:

Expected: Steam opens normally and without issues What actually happened: No visible window pops up, I get notifications seconds apart about steamwebhelper crashing until I close Steam from the system tray

Steps for reproducing this issue:

  1. Launch Steam
  2. Observe steamwebhelper crash
Villaton commented 1 year ago

Same issue here. Steam keeps pushing pop-up windows, which seems to crash constantly. Made clean install and problems appear after login. Steam totally unusable. Ubuntu 22.04.2 LTS AMD® Ryzen 5 3600 6-core processor × 12 Advanced Micro Devices, Inc. [AMD®/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] steam_logs.zip

gzqx commented 1 year ago

Same issue here. Get about 13 windows of steamwebhelper every morning I wake up. However, in my case normally usage has no problem, the client works. It seems only happens when my desktop is idle for a long time.

Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor

lorentzforces commented 1 year ago

Issue present on my system as well. Issue previously was seen (in the last few days) when switching back to this machine on a KVM, and would freeze the X session in the process. Right now, it happens on Steam launch, and no window appears (although the tray icon appears and can be interacted with).

Apologies for the screenshot, but I couldn't get a good snapshot of the processes any other way (screenshot is from htop while issue is happening, these processes die and then are created again every few seconds): image

Logs from running steam (gist)

Systemd logs (journalctl) from the crash (gist)

System Information: Fedora Linux 37 AMD Ryzen 5 3600 X11 version: 1.20.14 Nvidia driver version: 535.54.03 Nvidia card: Gigabyte RTX 3080Ti

Steam is installed via the rpm fusion repo through the dnf tool. Steam version as best as I can determine: 1.0.0.78

Output of uname -a: Linux carmine 6.3.8-100.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 15 01:51:54 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Happy to troubleshoot and collect any other relevant data as needed.

ntm commented 1 year ago

Same issue as described by @lorentzforces , not 100% sure that everyone is discussing the same: I don't get any popup windows as described by @gzqx , just steamwebhelper processes seem to start and die in a loop. My setup is fedora 37 on bare metal with nvidia GPU, latest nvidia proprietary drivers from rpmfusion. As a workaround, "steam -vgui" works for me (although no friends list anymore).

gzqx commented 1 year ago

@ntm Are you using Gnome? I have a guess the difference between you and lorentzforces and me is maybe you are using Gnome?

ntm commented 1 year ago

@gzqx no I'm using KDE like you. But I'm using X11 not wayland, maybe that's relevant?

Waddlen commented 1 year ago

After the latest Steam stable update, Steam does not open. The "logging in" windows appears and I can see the Steam icon in the Ubuntu app tray, but I cannot get the Library window to appear. Thanks to @ntm because steam -vgui gets the Library window open.

lorentzforces commented 1 year ago

@ntm I believe these are the same issue - on at least one occasion I had multiple (non-responsive) windows open with "SteamWebHelper" in their titles. That symptom seems to have been superseded by others, but my guess is they're fundamentally the same problem.

kleshas commented 1 year ago

getting the same issue with wayland. beta and non-beta. Constant steamwebhelper dumped core messages in journalctl. No GUI for steam, no popups. What works for me is running steam from the terminal (no need for -vgui). Arch fully updated.

kisak-valve commented 1 year ago

Hello @kleshas, symptomatically, Steam working when started from a terminal makes your issue #9383.

lorentzforces commented 1 year ago

Update in my case:

Some people in the thread for issue #9764 had resolved their issues by removing the directory at ~/.cache/nvidia/GLCache. I removed this directory, and can now successfully launch Steam.

As noted in that issue, this may not resolve all issues with the web helper.

iddm commented 1 year ago

I don't have such a directory with the latest drivers installed. What should I do?

Arch/X11/NVIDIA 535/ RTX 3080 / RTX 4090.

I think I get the same crash with libcef:

[  131.917220] traps: steamwebhelper[4877] trap invalid opcode ip:7fd6a7ddb794 sp:7fffc43414f0 error:0 in libcef.so[7fd6a54ef000+7770000]
[  257.307002] traps: steamwebhelper[5728] trap invalid opcode ip:7f7fcd5db794 sp:7ffdedcdb110 error:0 in libcef.so[7f7fcacef000+7770000]
[  293.799262] traps: steamwebhelper[19662] trap invalid opcode ip:7f9af37db794 sp:7ffdfe697300 error:0 in libcef.so[7f9af0eef000+7770000]
[  303.754846] traps: steamwebhelper[20031] trap invalid opcode ip:7f55261db794 sp:7fff43ed6fa0 error:0 in libcef.so[7f55238ef000+7770000]
[  313.716293] traps: steamwebhelper[20172] trap invalid opcode ip:7f238b3db794 sp:7fffee8de880 error:0 in libcef.so[7f2388aef000+7770000]
[  324.145893] traps: steamwebhelper[20375] trap invalid opcode ip:7f4410ddb794 sp:7fffb8dfa060 error:0 in libcef.so[7f440e4ef000+7770000]
[  334.221911] traps: steamwebhelper[20569] trap invalid opcode ip:7fa21cfdb794 sp:7fff26346ed0 error:0 in libcef.so[7fa21a6ef000+7770000]
[  373.928393] traps: steamwebhelper[34383] trap invalid opcode ip:7f70a81db794 sp:7ffdb0d4a420 error:0 in libcef.so[7f70a58ef000+7770000]
[  383.603672] traps: steamwebhelper[34788] trap invalid opcode ip:7fc5547db794 sp:7ffd6c031f20 error:0 in libcef.so[7fc551eef000+7770000]
[  393.890319] traps: steamwebhelper[34927] trap invalid opcode ip:7fda90ddb794 sp:7ffc9493fb60 error:0 in libcef.so[7fda8e4ef000+7770000]
[  404.007889] traps: steamwebhelper[35097] trap invalid opcode ip:7f00c25db794 sp:7fff80cc06c0 error:0 in libcef.so[7f00bfcef000+7770000]
[  414.263890] traps: steamwebhelper[35242] trap invalid opcode ip:7f5f2b9db794 sp:7ffd3f73a4c0 error:0 in libcef.so[7f5f290ef000+7770000]
[  424.291781] traps: steamwebhelper[35385] trap invalid opcode ip:7f668f9db794 sp:7ffc31db0020 error:0 in libcef.so[7f668d0ef000+7770000]
[  622.503392] traps: steamwebhelper[36178] trap invalid opcode ip:7ff361ddb794 sp:7fff1cc15780 error:0 in libcef.so[7ff35f4ef000+7770000]
[  647.592556] traps: steamwebhelper[38708] trap invalid opcode ip:7fd9f6fdb794 sp:7ffd5e05d780 error:0 in libcef.so[7fd9f46ef000+7770000]
[  661.459904] traps: steamwebhelper[39655] trap invalid opcode ip:7fa00f3db794 sp:7ffeea24a8b0 error:0 in libcef.so[7fa00caef000+7770000]
[  671.648908] traps: steamwebhelper[39867] trap invalid opcode ip:7f10affdb794 sp:7ffcd706ad70 error:0 in libcef.so[7f10ad6ef000+7770000]
[  681.601398] traps: Composite Threa[40603] trap invalid opcode ip:7fe056fdb794 sp:7fe0446bf8f0 error:0 in libcef.so[7fe0546ef000+7770000]
[  691.841594] traps: Composite Threa[40777] trap invalid opcode ip:7f63047db794 sp:7f62f1e5d8f0 error:0 in libcef.so[7f6301eef000+7770000]
[  701.882964] traps: Composite Threa[40978] trap invalid opcode ip:7f7fbf5db794 sp:7f7facc0a8f0 error:0 in libcef.so[7f7fbccef000+7770000]
[  711.990447] traps: Composite Threa[41174] trap invalid opcode ip:7f2c889db794 sp:7f2c760848f0 error:0 in libcef.so[7f2c860ef000+7770000]
[  722.206224] traps: Composite Threa[41383] trap invalid opcode ip:7fb2453db794 sp:7fb232a268f0 error:0 in libcef.so[7fb242aef000+7770000]
[  732.331439] traps: Composite Threa[41593] trap invalid opcode ip:7f78aebdb794 sp:7f789c2ac8f0 error:0 in libcef.so[7f78ac2ef000+7770000]
[  742.563449] traps: Composite Threa[41828] trap invalid opcode ip:7f14025db794 sp:7f13efba28f0 error:0 in libcef.so[7f13ffcef000+7770000]
[  752.856279] traps: Composite Threa[42096] trap invalid opcode ip:7fbb581db794 sp:7fbb457b88f0 error:0 in libcef.so[7fbb558ef000+7770000]
[  763.088490] traps: Composite Threa[42342] trap invalid opcode ip:7fe14afdb794 sp:7fe13861f8f0 error:0 in libcef.so[7fe1486ef000+7770000]
[  773.067304] traps: Composite Threa[42629] trap invalid opcode ip:7f08a13db794 sp:7f088ea728f0 error:0 in libcef.so[7f089eaef000+7770000]
[  783.330572] traps: Composite Threa[42902] trap invalid opcode ip:7fb9b07db794 sp:7fb99ab5c8f0 error:0 in libcef.so[7fb9adeef000+7770000]
[  793.547577] traps: Composite Threa[43262] trap invalid opcode ip:7fcc18fdb794 sp:7fcc064fd8f0 error:0 in libcef.so[7fcc166ef000+7770000]
[  803.567595] traps: Composite Threa[43561] trap invalid opcode ip:7f28ee9db794 sp:7f28dbfcd8f0 error:0 in libcef.so[7f28ec0ef000+7770000]
[  813.699454] traps: Composite Threa[43869] trap invalid opcode ip:7f965f7db794 sp:7f964ce418f0 error:0 in libcef.so[7f965ceef000+7770000]
[  823.795796] traps: Composite Threa[44191] trap invalid opcode ip:7fc3effdb794 sp:7fc3dd68b8f0 error:0 in libcef.so[7fc3ed6ef000+7770000]
[  834.025417] traps: Composite Threa[44556] trap invalid opcode ip:7fdf685db794 sp:7fdf529178f0 error:0 in libcef.so[7fdf65cef000+7770000]
[  844.235024] traps: Composite Threa[44928] trap invalid opcode ip:7fa73bbdb794 sp:7fa7246cd8f0 error:0 in libcef.so[7fa7392ef000+7770000]
[  854.665286] traps: Composite Threa[45289] trap invalid opcode ip:7fa2d8ddb794 sp:7fa2c633d8f0 error:0 in libcef.so[7fa2d64ef000+7770000]
[  864.535104] traps: Composite Threa[45666] trap invalid opcode ip:7f3ab93db794 sp:7f3aa69b38f0 error:0 in libcef.so[7f3ab6aef000+7770000]
[  874.677943] traps: Composite Threa[46073] trap invalid opcode ip:7fb2393db794 sp:7fb226a4b8f0 error:0 in libcef.so[7fb236aef000+7770000]
[  885.015647] traps: Composite Threa[46473] trap invalid opcode ip:7fa700bdb794 sp:7fa6eea2d8f0 error:0 in libcef.so[7fa6fe2ef000+7770000]

Journalctl:

Jul 01 07:51:08 purplejam systemd-coredump[51545]: [🡕] Process 51021 (steamwebhelper) of user 1000 dumped core.

                                                   Stack trace of thread 51535:
                                                   #0  0x00007fbc853db794 n/a (/home/fx/.local/share/Steam/ubuntu12_64/libcef.so + 0x43db794)
                                                   #1  0x00007fbc85467522 n/a (/home/fx/.local/share/Steam/ubuntu12_64/libcef.so + 0x4467522)
                                                   #2  0x00007fbc8546a764 n/a (/home/fx/.local/share/Steam/ubuntu12_64/libcef.so + 0x446a764)
                                                   #3  0x00007fbc6d6f77f2 n/a (libnvidia-glcore.so.535.54.03 + 0x14f77f2)
                                                   #4  0x00007fbc6d1fcf45 n/a (libnvidia-glcore.so.535.54.03 + 0xffcf45)
                                                   #5  0x00007fbc6d20844a n/a (libnvidia-glcore.so.535.54.03 + 0x100844a)
                                                   #6  0x00007fbc6d546182 n/a (libnvidia-glcore.so.535.54.03 + 0x1346182)
                                                   #7  0x00007fbc6d549cb5 n/a (libnvidia-glcore.so.535.54.03 + 0x1349cb5)
                                                   #8  0x00000000004a9cbf n/a (/home/fx/.local/share/Steam/ubuntu12_64/steamwebhelper + 0xa9cbf)
                                                   ELF object binary architecture: AMD x86-64
Jul 01 07:51:17 purplejam systemd-coredump[52088]: [🡕] Process 51553 (steamwebhelper) of user 1000 dumped core.

I guess the steamwebhelper was built with one version of libcef, and at runtime, we get another binary-incompatible one.

kisak-valve commented 1 year ago

Hello @vityafx, #9634 is relevant to your system. You could try downgrading to the 530 series NVIDIA driver as a workaround.

RayOfLight1 commented 10 months ago

I have the same symptoms and I don't have anything nVidia Related: 33:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev c1)

I have been unable to start steam for more than two months, tried multiple launch flags and still crash, reinstalled steam-launcher and no change, and I'm unable to set beta or no beta, I don't even have the login window.

traps: steamwebhelper[1423113] trap invalid opcode ip:7fb227c066e2 sp:7ffd7d723b50 error:0 in libcef.so[7fb2240ef000+7770000]
traps: steamwebhelper[1423550] trap invalid opcode ip:7f4b6d0066e2 sp:7ffc783cfd00 error:0 in libcef.so[7f4b694ef000+7770000]

[...] etc. ad infinitum.

tg-- commented 9 months ago

I'm having the same issues and suspect this is a wayland problem.

There's a new tool that works around some wayland timeout issues due to overloaded queues, wayland-proxy, which acts as a load balancer.

I've tried it for 3 sessions now and didn't have a single crash since, while I usually had 3-10 crashes per session. I can't be certain that this is actually working yet, but maybe someone else wants to give it a try, too.

Just build wayland-proxy, and start steam with it ("wayland-proxy /usr/bin/steam" or whatever).

seanpatrick1976 commented 8 months ago

Edit: it seems after reading this thread as I'm able to open from a terminal normally my issue is related to https://github.com/ValveSoftware/steam-for-linux/issues/9383.

I'm having the same issue in Wayland - I can launch it from the terminal just fine but launching it from the desktop just loops opening and closing. Interestingly enough the Steam menu remains in the taskbar as the window keeps trying to open, but selecting anything doesn't work.

pchmykh commented 7 months ago

Same error here.

yumio7 commented 7 months ago

i just cant get it to launch at all, native runtime doesnt work either, none of the flags ive seen recommended even get me to a login window. It just either doesnt launch a window at all, or after a while gives me the "steamwebhelper is not responding" one

Arch/Wayland/Ryzen 9 4th Gen/RTX2060/NVIDIA 545

ryanmusante commented 6 months ago

Related to https://github.com/ValveSoftware/steam-for-linux/issues/10577

I'm encountering same issues on execution of steam. Tried different launch options with no luck.

Manjaro/Wayland/Intel i7-11800h/RTX3080/NVIDIA 550

[Mon Mar  4 15:05:42 2024] traps: steamwebhelper[2385] trap int3 ip:7c5757d1a193 sp:7ffc518e2790 error:0 in libcef.so[7c5751b36000+91a8000]
[Mon Mar  4 15:14:34 2024] traps: steamwebhelper[3565] trap int3 ip:75c6c431a193 sp:7ffef9912cf0 error:0 in libcef.so[75c6be136000+91a8000]
[Mon Mar  4 15:15:18 2024] traps: steamwebhelper[3983] trap int3 ip:7f371531a193 sp:7ffca3e5c480 error:0 in libcef.so[7f370f136000+91a8000]

Output from cli launch:

[2024-03-04 15:15:15] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/ryan/.local/share/Steam/logs

XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe3ba1dc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe3ba0500
steamwebhelper.sh[3862]: === Mon Mar  4 03:15:17 PM PST 2024 ===
steamwebhelper.sh[3862]: Starting steamwebhelper under bootstrap sniper steam runtime at /home/ryan/.local/share/Steam/ubuntu12_64/steam-runtime-sniper
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 4016
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
glu8716 commented 6 months ago

Having the same problem mentioned by @ryanmusante on Artix Linux. It started randomly yesterday night after the client crashed. I've tried to delete everything steam-related and used various launch commands recommended in the thread, but nothing worked.

JohnieWalkerCZ commented 6 months ago

Same problem on Ubuntu 22.04, RTX 2060 Mobile

SheridanR commented 4 months ago

Steam randomly doesn't launch for me at all anymore. Just loops crashing the steamwebhelper process. Using an AMD Radeon 7600 XT.

Joey451-OG commented 4 months ago

Steam randomly doesn't launch for me at all anymore. Just loops crashing the steamwebhelper process. Using an AMD Radeon 7600 XT.

Same here. I've tried the rpm and flatpak version. It just will not start anymore.

Spec: Fedora 40 AMD Radeon 6700 XT

fruitbang commented 4 months ago

same problem

System Details Report


Report details

Hardware Information:

Software Information:

AltantisPegasus commented 3 months ago

Hey. Im also expecting the steamwebhelper-crashing, when starting via steam-shortcut pinned to window-bar. getting the loading screen, then a black windows and then the crash report is generated in journalctl. if i start steam from terminal, everythings fine. steam -vgui doesnt bring up anything or startable, steam just sitting then in the systemtray. maybe as addition: i changed my shell via chsh to zsh. but shouldnt be the problem at all, since starting steam via terminal works fine.

Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland

Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 61.8 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X670E AORUS PRO X System Version: -CF Windowing System: Wayland Kernel Version: Linux 6.8.9-zen1-1-zen

jwhipp commented 3 months ago

+1 Fedora 40 with a discrete AMD gpu. Will launch if I select "Launch using integrated Graphics Card".

gitsoft commented 3 months ago

Same issue here.

Processors: Intel® Core™ i7-4790S CPU @ 3.20GHz × 8 Memory: 32 GiB of RAM Graphics Processor: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] Gnome version: 42.9 Windowing System: X11 OS: POP OS 22.04 Kernel Version: Linux 6.9.3-76060903-generic

Akiyamka commented 2 months ago

Fedora 40, Gnome Wayland. Constantly crashes after launch from app catalogue or dock ("Launch using integrated Graphics Card" works fine, launch from terminal works fine too)

updater built Jun 20 2024 17:13:49

Hardware:

CPU: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (16) @ 5.26 GHz
GPU 1: AMD Radeon RX 7700S @ 0.86 GHz [Discrete]
GPU 2: AMD Radeon 780M @ 0.80 GHz [Integrated]
Blitzwing1 commented 2 months ago

Replying to https://github.com/ValveSoftware/steam-for-linux/issues/9706#issuecomment-2220282163

Sounds like I have the same issue, I've just ended up creating a new .desktop shortcut that targets /usr/bin/steam, it doesn't have the right click icon menu functionality but it got around it, until a fix comes.

Ophiolith commented 1 month ago

Also having this issue, seems to be unrelated to setting DRI_PRIME as I've disabled the iGPU in my BIOS. RPM and Flatpak versions give the exact same error. Curiously, it seems to specifically be related to when I 'soft-close' Steam so it should be running in the background is when steamwebhelper starts crashing. If I completely kill Steam from the Gnome's background application manager and then restart, it works again.

OS: Fedora Workstation 40 / GNOME / Wayland
CPU: AMD Ryzen 7 7700x
GPU: AMD Radeon RX 7800xt
andrewbenton commented 1 month ago

I'm also seeing this issue on Fedora 40 w/ Gnome on X11. It seems like this issue occurs when I try to launch Steam through the Gnome overview launcher. It doesn't occur when I launch via $ steam on the CLI or launch through Gnome Software. Steam works consistently once launched and until shutdown. Attached captured logs are each from a single attempted launch and immediate shutdown.

andrewbenton commented 1 month ago

After a bunch more digging, I think that this is an issue related to the DRI_PRIME variable (or Gnome's handling of it). After starting the steam process through the 3 methods mentioned above, I compared the /proc/<pid>/cmdline and /proc/<pid>/environ. The /proc/<pid>/cmdline didn't have any considerable differences between the 3 different runs. The /proc/<pid>/environ showed differences in a few variables such as LD_LIBRARY_PATH, MANPATH, and MEMORY_PRESSURE_WATCH, but changing any of these values had no impact. There was also a difference in DRI_PRIME...

When launched from the Gnome overview (using the .desktop file), DRI_PRIME was set to DRI_PRIME=pci-0000_14_00_0. If I run steam from the CLI as DRI_PRIME=pci-0000_14_00_0 /usr/bin/steam or DRI_PRIME=1 /usr/bin/steam then steam does the previously mentioned crashloop. If I leave DRI_PRIME unset then it works without issue. It turns out that pci-0000_14_00_0 is the iGPU on my machine. If I instead run DRI_PRIME=0000_04_00_0 /usr/bin/steam then my dGPU is targeted and steam launches and runs without a problem.

I've attempted to change the PrefersNonDefaultGPU and X-KDE-RunOnDiscreteGpu from /usr/share/applications/steam.desktop between true and false to change the set value of DRI_PRIME through the Gnome overview-launched application. This had not had the intended effect, though this may be due to the .desktop launch settings being cached somehow even through an xdg-desktop-menu forceupdate.

Related issues:

PaoloTorregroza commented 1 month ago

Hi! Fresh Fedora 40 install, AMD 7900gre and AMD7800x3d, steam fails to open from app list, works from terminal.

I have the steam families beta enabled.

Stihl commented 3 weeks ago

I have had this issue on Debian 12 since the first week of this install (started Aug 9th 2024). I started with KDE Plasma but was getting crashes with KDE and steam was doing this. I decided to purge KDE and install XFCE instead. This changed the stability of my DE but didn't change steams issues.

I had reinstalled steam several times and it seemed to work each time but kept failing when I would sleep or start the machine. And some times it would randomly work after having restarted. After trying the vgui flag and it not working I decided to check out and see if steam had any flags for me to test out. I found this site and went through them. https://developer.valvesoftware.com/wiki/Command_line_options#Command-Line_Parameters_4 I eventually landed on -no-dwrite The Description for this flag is "Forces vgui to use GDI text even if DWrite support is available". I figured I have no clue what DWrite is and its probably not important but this changes some kind of text rendering so I should try it. I tested the flag in my launcher bar and steam now launches just fine for me.

After some further searching of DWrite I have come to the conclusion that its a Microsoft library related to text/symbol rendering. Im not sure if there is supposed to be a version of DWrite that linux supports but it seems that GDI text is relevant. (when searching apt for libgdi I find libgdiplus is a valid repo when i search apt but I do not have it installed and do not need it to run steam)

I can see when launching from the command line that many commands are automatically run which suggests to me that the Linux version needed to be distributed with that flag by default (after all they run -gamepadui by default as noted in the note in its description).

My conclusion after this session of attacking the problem is that Steam UI is relying on some kind of Microsoft library that is not on Linux or is not properly considered when launching the Linux version of steam.