Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
again, internet. internet connectivity.
i've seen a handful of other posts about this sort of problem and tried everything mentioned, but no one has explained a source for the problems - just stabbed in the dark until the problem went away.
so - steam linux users - proton games don't connect to the internet. what gives?
other searches have shown the windows games requiring proton have problems with name resolution. it's seemingly related to systemd. i read somewhere that systemd would have to be compiled with 32 bit support, and i did that - updated ABI_X86 to "32 64" a rebuilt. no dice. i haven't been able to get to the bottom of it.
https://pastebin.com/XcQhgsdm
what am i looking for?
FWIW, i see nothing of interest in the steam cli output, but here that is in case it's useful:
https://pastebin.com/BX09ruY7
Domain Nameserver (DNS)
https://wiki.archlinux.org/title/Systemd-resolved
Preserving resolv.conf - this mode preserves /etc/resolv.conf and systemd-resolved is simply a client of this file. This mode is less disruptive as /etc/resolv.conf can continue to be managed by other packages.
Maybe worth a try to have a readable /etc/resolv.conf, even if it is understood by system-resolved, many application don't know about resolved and are only reading nameserver entries in /etc/resolv.conf
AppArmor
It is not a good idea to have security applications such as SELinux and AppArmor, left without administration, it's like having a firewall without ever administering it, at some point it will always block you rather than intruders. If you use it, enable it and configure it, if you don't then uninstall it
Wine file into your boot process ?
Maybe good to look at why your system is attempting to load a Wine file into its boot process, or why a Wine file is part of the boot before even loading the Polkit Authorization Manager. Have a look in the Startup Application of your graphical session
And in your PROTON_LOGS there are indeed indications of
X error
Looking X errors depends on you display manager, I know lightdm on Arch Linux puts them in ~/.xsession-errors, also on most systems you will have some X boot informations in /var/log/Xorg.0.log too, it is good to look for lines starting with (EE) in this last.
And network error
They are indeed warning indicating something blocked the internet connection,
a possible reason would be not preserving the /etc/resolv.conf original format as seen previously
These are all the things I would look for solving this issue on your system
let's focus on the resolv.conf issues for now, because that is what every other related thread i've found has blamed...
i've gone through arch's wiki a few times, and i'm going to apologize for asking what i'm fairly certain is a stupid question, but here goes:
what specifically are you suggesting needs to be done with my resolv.conf?
here is why i ask - the link you point me to says:
the steps i've taken so far are to edit resolv.conf to a completely generic file listing only my search domain and google nameservers:
next, i tried the simlink trick, and resolv.conf became a bit more complicated, but resulting in the conditions you see in the log. i also tried just nuking the file, letting it be recreated... same results.
for now, i've gone back to an immutable resolv.conf as described above, and the results in steam are the same - FC5's arcade just times out.
as far as apparmor goes, libapparmor is required for systemd profiles, but the apparmor service is disabled / not running. so it's not stopping anything.
so - what now?
The mode of operation of systemd-resolved is detected automatically, depending on whether /etc/resolv.conf is a symlink to the local stub DNS resolver file or contains server names.
So yes editing it as you did should be enough for it to know how to work.
What you could try to be sure it is not comming from resolvd, you could systemctl stop the service and see if the issue persists, I don't think this service is required, here I don't have it installed.
Next I would look at higher level, Xorg session log, I think on Gentoo you have a xorg-session.log somewhere, try
sudo locate xorg-session.log
or sudo find / -name "xorg-session.log" -print
https://pastebin.com/WewhreUX
out of curiosity, what is xorg going to log w/rt the network interface?
while at it, my latest boot log:
https://pastebin.com/AG3SSssu
still the same prob - just timeout in FC5 arcade...
shouldn't there be an easier way to diagnose this? FWIW, the problem suggested in all other similar threads has been 32 & 64 bit multilib, where steam / wine require 32 bit ABI. seems odd though, since native linux games have no problem, leading me to think it's only proton.
Wanted to see the Xorg session log on your system to uncover what is hidding the following error, it is uncommon error
Else last thing to try is PROTON_LOG=1 %command% and if we don't find anything better I think you will be good to share your log generated from PROTON_LOG=1 %command% launch option here (it is a file created in your home steam-APPID.log)
https://github.com/ValveSoftware/Proton/issues/2356
I see this connectivity issue is frequently reported for FC5 but no root cause has been found yet, but I see they tagged the ticket Nvidia and you own AMD gpu, so your feedback could be interesting for fixing Proton if necessary.
(You could post it directly to github too, kisak-valve is usually quick and best person to give insights on PROTON_LOG and on potential Proton regressions, many reports mention FC5 behave differently from a Proton version to another)
google tells me that means uplay is missing, broken, dead, whatever.
i give up. i don't game much anyway, and at this point i'm ready to call it a day. hopefully this fixes itself so i can still play offline - otherwise... well... otherwise then i don't game at all any more : /
i think FC5 is dead. i can still run DOOM eternal, but it too cannot see the internet.
so yeah, that's what happens when you try to fix things kids.
don't try to fix things.
Just start Steam normally, Right click FC5 in the library and paste this in the launch options
Reproduce your errors in the game, close game, and look at the file in ~/steam-APPID.log
FWIW - the game is totally dead now though. seeing your comment about FC5 behaving differently with different versions of proton, i went to properties, and tried launching the game with a much older version instead of proton-experimental. it took some time to try to launch, then died.
so i selected a later version, no dice... next version, no dice...
until i got back to proton-experimental. the error message changed from english in the latest stable version to czech when i selected proton-experimental.
so i can't reproduce my error now... i can't do anything.
it's just as well, now i have to find productive hobbies : )