-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(default-flatpaks): Couldn't resolve host name
with some working internet connections
#346
Comments
Interestingly, I caught today that So I believe that we need to set
|
Reopening, because changing |
The PR above that I made solved this issue for me. Maybe I can set 5 network connection tries instead of 3, to be more safe And, it would be good to add log after internet connection is reinstated Edit: Did this above here: |
For me, it seems to connect from 1 to 3 connection attempts, with 2 attempts on average. @Oakleafknight06 Mentioning you to tell you that this issue should be fixed. Here's how logs look like for me now:
|
Here's how it looks like when internet connection is not successful:
|
Alright sounds good. Haven't been using the module and can't really use it right now but thanks for the fix :) |
Even with
user-flatpak-setup
service, which starts later, this issue can arrise when adding remote or installing flatpaks in some working internet connections.We have this in service unit already covered:
Anecdotally, I switched to fiber internet a week ago & since then, I noticed this issue.
I tried to change DNS to Cloudflare, but issue still persists.
Interesting thing is that I also have fiber internet from same operator in another place & flatpak-setup works fine there.
Here's the log on when it happens for me:
Let's investigate on how to improve this situation.
Maybe we need to do some tweaking for service units.
If someone got into similar situation, please comment.
I remember that @Oakleafknight06 had the same issue.
The text was updated successfully, but these errors were encountered: