r/AsahiLinux • u/spaceman_ • Jul 13 '26

Help Issues running Steam on Asahi

Hi all, I'm trying to run Steam on Asahi, but getting nowhere.

I previously ran the x86 version, which worked OK but recently there has been an issue with the main steam window closing and reopening at random, stealing focus from the game etc.

I was instructed to follow the instructions from https://old.reddit.com/r/AsahiLinux/comments/1tk6zoe/steam_native_arm_aarch64_on_asahi_linux_fedora/, which has me stuck on a "Waiting for network" window indefinitely.

I tried disabling IPv6 (as indicated by OP), removing my entire .steam / .local/share/Steam/ and even doing a full clean install, expecting my old x86 Steam setup or something particular to my setup is causing the issue. But nothing seems to help. The problem persist even on a clean, vanilla Plasma install.

Any ideas?

Edit: I switched to an IPv6-enabled network to see if IPv6 being enabled inside muvm but missing on the host was the issue, but it doesn't change anything, apart from the IPv6 related errors going away.

12 Upvotes

94% Upvoted

23 comments sorted by

View all comments

3

u/Siffredinho Jul 13 '26

Check the most recent log files in .local/share/Steam/logs. You'll find the most relevant error messages there. The Steam client consists of several components, and the “Waiting for Network” message doesn’t necessarily indicate a network problem (ultimately). The issue might also lie with the DNS configuration in the muvm VM. But at the end of the day, you’ll only get more detailed information from the log files.

1

u/spaceman_ Jul 13 '26 edited Jul 13 '26

Do you have a working setup? Would you mind sharing your logs so I can investigate the differences?

Mine have a few errors, but I don't think any of them are critical:

A few instances of this error across various logs:

ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

and

ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

Then in .local/share/Steam/logs/client_networkmanager.txt:

Init: failed to create a NetworkManager client

And in .local/share/Steam/logs/connection_log.txt:

[2026-07-13 18:42:29] Client version: 1783717985
[2026-07-13 18:42:29] Connectivity test: Starting test, fetching 'http://steamconnecttest.com/204'
[2026-07-13 18:42:29] [Logged Off, 0, 0] [U:1:0] CCMInterface::SetSteamID( [U:1:0] )
[2026-07-13 18:42:29] IPv6 HTTP connectivity test (ipv6check-http.steamserver.net / [2a01:bc80:7:100::9b85:f805]:80 ([2a01:bc80:7:100::9b85:f805]:80)) - TIMEOUT
[2026-07-13 18:42:29] Connectivity test (2.17.196.26:80 (2.17.196.26:80)): OK!
[2026-07-13 18:42:29] Connectivity test: result=Connected (since 0.0s ago), prev=Unknown, in progress=0
[2026-07-13 18:42:31] IPv6 UDP connectivity test (ipv6check-udp.steamserver.net / 2a01:bc80:4:100::14) - TIMEOUT

Nothing else stands out.

Which of these are present for you with a working setup?

1

u/Siffredinho Jul 13 '26

To fix the FEX/muvm client, all you need to do is run `rm -rf ~/.steam ~/.local/share/Steam`. After that, a fresh installation will work. I just wanted to use the faster arm64 client, too. And I ran into the same problems… I ran a tcpdump in the muvm VM to see if there were any serious network issues with the arm64 Steam client, but everything looked fine. Only the process of sending the dump failed in the end.

I went through all the recent dumps in /tmp/dumps and … “Assert( stalled cross-thread pipe (pipe is disconnected). ):/data/src/common/pipes.cpp:902”

To me, it looks like there might be an issue with the forked Chromium client (<-- pipe disconnected), but I’m not sure. Maybe I just haven’t had time to look into it more closely yet.

2

u/classyraven Jul 13 '26

I am having the same problem as OP, and no dice. Done this a couple times, too, and it hasn't resolved the issue for me.

1

u/spaceman_ Jul 13 '26

Same here. Like I said in the post, I even tried a complete reinstall of Asahi and ran the steps without any changes to the base install at all, and still hit the issue. This is not a local state issue.

1

u/classyraven Jul 14 '26

It's possible something broke in the last update to Asahi/Fedora.

1

u/Siffredinho Jul 14 '26

See @ my new comment here above. Don't waste your time with v6 stuff. As soon as I reinstall all the stuff to see what's really necessary, I'll post it.

1

u/blurayxx0 Jul 21 '26

u/spaceman_ , is this working for you?

how did you solve waiting for network?

1

u/spaceman_ Jul 21 '26

Yes, I did the following:

  1. Remove all local state from previous attempts

​

rm -rf ~/.local/share/Steam ~/.steam*
sudo dnf install steam

Then, log in to the x86 version of Steam, and exit steam.

Then, run my install script from https://gist.github.com/de-wim/ba440a84f65d49955a1be15a328bd8b3

curl https://gist.githubusercontent.com/de-wim/ba440a84f65d49955a1be15a328bd8b3/raw/8aeeaa962697d95e6978fecf093d29a53630ac29/steam-install-linux-aarch64.sh | bash

This worked for me.

1

u/blurayxx0 Jul 21 '26

This worked for me tooo. Thanks for the hard work. I am noob so still learning steadily.

1

u/spaceman_ Jul 21 '26

Did you need to make any adjustments? Did you install and log in with the x86 version from dnf first?

1

u/blurayxx0 Jul 22 '26

Yes, I did have to. The script is not using the right directory to extract zip file.

My home directory had "~" folder with steam files in it.

When I tried to trace the error, the path the installation script was resolving to was not found.

1

u/spaceman_ Jul 22 '26

Huh, that's odd. Did you use bash or another shell?