t; let it take over network functionality. After a while of
> > > > > running,
> > > > > look
> > > > > in the logs, journalctl -r, to see if there are any complaints
> > > > > about an
> > > > > inability to check for upd
dates. It might take a while.
>
> I removed PackageKit a long time ago – I cannot afford automatic update
> for a number of reasons. No update has ever reinstalled it. I use
> NetworkManager on the laptops because of the dynamic Internet
> connection. The workstation and server though are
urnalctl -r, to see if there are any complaints
> > about an
> > inability to check for updates. It might take a while.
I removed PackageKit a long time ago – I cannot afford automatic update
for a number of reasons. No update has ever reinstalled it. I use
NetworkManager on the l
On Sun, 2017-04-16 at 08:33 -0700, stan wrote:
> On Sun, 16 Apr 2017 05:34:40 +0100
> Russel Winder wrote:
>
> > I had thought I had removed NetworkManager from my workstation in
> > favour of using systemd-networkd. However it seems in the last Rawhide
> > update,
On Sun, 16 Apr 2017 05:34:40 +0100
Russel Winder wrote:
> I had thought I had removed NetworkManager from my workstation in
> favour of using systemd-networkd. However it seems in the last Rawhide
> update, NetworkManager has reinstalled itself and has enforced
> starting.
I had thought I had removed NetworkManager from my workstation in
favour of using systemd-networkd. However it seems in the last Rawhide
update, NetworkManager has reinstalled itself and has enforced
starting. I tried removing it but it seems GNOME Shell depends on it's
presence. Isn't this a