or just rely on dbus and networkmanager
This appears to be related to issue, #474, as well. Although I think they may still qualify as separate issues, considering that one is in regards to Steams initial startup on boot, and the other is in regards to Steam reconnecting to the internet while already running after "waking" the computer.
I disagree; networkmanager is an un-necessary dependency. Steam should rely on /some/ external influence managed by a system operator (end user/other) to attempt to maintain a network connection of their choice. It should use default routing and use the status of connections it maintains already in order to determine if connectivity exists (Can I talk to the login servers to authenticate? Is the connection to the chat system working?). This allows for the steam client to be more simple and less susceptible to changes in system configuration and libraries. (For example, I see ZERO reason to run network manager on -any- system that has a static configuration of either fixed or DHCPed address from a single source; particularly for Ethernet connected systems
Well in the last months it only did this once or twice, instead of every time like before, so I think it is mostly fixed and I'm closing this.
How to tell steam to reconnect manually?
Restarting is very slow and needs to close games.
Nothing extracted yet.
Everytime I start my system, steam loads up and says that there was no network connection availlable and my only option is to restart steam or Quit.
When i do Quit, the steam client doesn't close and stays there acting like a zombie.
When i do Retry the client closes and restarts and the connection works correctly.
If I disable the auto-start and start Steam manually one second after starting my stystem, it also works correctly.
It appears that steam starts too soon and that the network is not availlable the millisecond it does so. I then see three solutions:
Thank you.