Re: F28 - Update reintroduced missing connection after suspend

On Wed, 2018-05-16 at 10:58 +0200, Stephan Goldenberg wrote:
Am 16.05.2018 um 09:40 schrieb Stephan Goldenberg:

I'm going to switch to networkd now and it will work.


I made the move and network is just fine, even after resume from 
suspend. The mislabeling of /etc/resolv.conf seems to be fixed too.
So I 
stick with networkd. Somehow NetworkManager can't handle my system
networkd can.

Gnome thinks the network is broken because it needs NetworkManager
some reason but I have no problems with that. I just care about the 
network being up and running after boot and after resume.



if the link has no carrier, then that is not related to NetworkManager.
It is likely a kernel issue or the switch to which your computer is

It is not clear, why networkd would work with cable (seemingly)
unplugged. But great if it works for you!!

Clearly Gnome would not know that you are connected to a network,
because networkd does not expose a meaningful D-Bus API that Gnome
could use. It should however work just fine without it (some features
missing). If not, that would be a bug (in Gnome).


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]