Re: F28 - Update reintroduced missing connection after suspend

[Stephan Goldenberg <dg1ees oppator de>]

Am 15.05.2018 um 13:33 schrieb Thomas Haller:
> On Tue, 2018-05-15 at 12:24 +0200, Stephan Goldenberg wrote:
> > Am 14.05.2018 um 22:46 schrieb Thomas Haller:
> > > On Mon, 2018-05-14 at 20:45 +0200, Stephan Goldenberg wrote:
> > > > It's a plain old cable based 1GBit/s connection. No WLAN, no
> > > > other
> > > > fancy
> > > > network. What do you need to hunt this down ?
> > >
> > > Hi,
> > >
> > > what's the output of `nmcli device` and `nmcli connection` after
> > > returning from suspend?
> > >
> > > best,
> > > Thomas
> >
> > Hi,
> >
> > there we go:
> >
> > [oppa@localhost ~]$ LANG=C && nmcli device
> > DEVICE      TYPE      STATE        CONNECTION
> > virbr0      bridge    connected    virbr0
> > enp3s0      ethernet  unavailable  --
>
> Hi,
>
>
> STATE=unavailable commonly means that no cable is plugged in (or at
> least, NetworkManger thinks so).
>
> `ip link show enp3s0` should also show you "NO-CARRIER".
>
>
> Unless there is carrier, NM will not autoconnect a profile (at least
> not, if the profile uses DHCP).
>
>
> best,
> Thomas

Hi,

what does this mean ? Switch to systemd-networkd and live with SELinux 
alerts ? This rewrites /etc/resolv.conf with wrong labeling but gets the 
network back up.

Is there a way to downgrade to the old version of NM and prevent future 
updates ?

Regards,
Stephan