I have had a problem for quite a while with running Steam since an OS update, it says that it can’t connect to network despite my wifi connection being perfectly fine. What I did to override it was that I was returning to previous OS before the update where it worked perfectly fine.
Unfortunately, it seems that my OS has updated again and now both versions I can choose from are not able to run Steam, it comes up with the same fail message. Sadly also some more apps do not work in this version - for example Firefox and Chromium (while Google Chrome works fine).
I have attached the diagnostics, can you please help me?
flatpak info --show-permissions org.mozilla.firefox
and
flatpak run --command=curl org.mozilla.firefox -v -s https://egon.bot.nu/test.php
We had few similar issues in the past where network connections in (some) flatpak applications stopped working after doing a system upgrade - with varying success in solving these issues. I really would love to nail it down this time to make this not happen anymore in the future
flatpak run --command=curl org.mozilla.firefox -D - -s http://www.google.at | head -1
and
flatpak run --command=curl org.mozilla.firefox -D - -s http://212.33.36.186 | head -1
if my current assumptions are correct, the first one shouldn’t output anything and the later one a HTTP/1.1 302 Found. Is that correct? If yes, please also give me the output of:
Ok, the reason for the apps not able to connect to anywhere has something to do with their inability to resolve the DNS name (something like www.google.at) to the IP adress used for the communication…
As this happens only for applications running Sandboxed, can you please give use additional insight with:
Run:cat /etc/nsswitch.conf (and post it’s output)
Run: flatpak run --command=sh org.mozilla.firefox
Now you are inside the Sandbox, please now run and post the output of those two commands:
ls -la /etc/resolv.conf; cat /etc/resolv.conf
and
ls -la /etc/nsswitch.conf; cat /etc/nsswitch.conf
With these information we should have enough insight to either solve the issue or creating a bugreport upstream if it’s not a configuration issue arisen during the upgrade.
Thank you for your patience in searching for the cause
Actually the second command came up with an error:
veronika@endless:~$ flatpak install -y flathub org.gnome.Sdk//3.38
Looking for matches…
error: Flatpak system operation Configure not allowed for user
veronika@endless:~$ systemctl status --user flatpak-session-helper
● flatpak-session-helper.service - flatpak session helper
Loaded: loaded (/usr/lib/systemd/user/flatpak-session-helper.service; stati
Active: active (running) since Sun 2021-05-09 14:55:17 CEST; 1min 40s ago
Main PID: 998 (flatpak-session)
CGroup: /user.slice/user-1001.slice/user@1001.service/flatpak-session-helpe
├─ 998 /usr/libexec/flatpak-session-helper
└─1002 server --sh -n /run/user/1001/.flatpak-helper/pkcs11-flatpak
May 09 14:55:17 endless systemd[620]: Starting flatpak session helper…
May 09 14:55:17 endless systemd[620]: Started flatpak session helper.
lines 1-10/10 (END)
@Daniel Any Ideas on this? It seems that for some reason, /run/host/monitor/resolv.conf is not available, so /etc/resolv.conf links to a file actually not available and name resolution fails in turn.