On Mon, 2017-04-17 at 19:29 +0200, Bastien Nocera wrote: > On Mon, 2017-04-17 at 09:00 -0700, Adam Williamson wrote: > > On Mon, 2017-04-17 at 09:48 +0100, Russel Winder wrote: > > > On Sun, 2017-04-16 at 23:26 -0700, Adam Williamson wrote: > > > > On Sun, 2017-04-16 at 08:33 -0700, stan wrote: > > > > > On Sun, 16 Apr 2017 05:34:40 +0100 > > > > > Russel Winder <russel@xxxxxxxxxxxxx> 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 tried removing it but it seems GNOME Shell > > > > > > depends on > > > > > > it's > > > > > > presence. Isn't this a dependency too far? > > > > > > > > > > GNOME shell is probably depending on NetworkManager for its > > > > > updates > > > > > handling, so it is integrated in. networkd probably isn't > > > > > supported > > > > > for that functionality. You can check this by leaving > > > > > NetworkManager > > > > > installed, and masking it in systemd, so that it can't be > > > > > started > > > > > by > > > > > the GNOME update manager (PackageKit?). Then start networkd, > > > > > and > > > > > 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 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 laptops because of the dynamic Internet > > > connection. The workstation and server though are fixed wired > > > connection so I thought I'd try systemd-networkd (removing > > > Networkmanager) and it was working fine – until NetworkManager > > > reinstalled for some reason. > > > > > > > I haven't checked this, but I can't think of any reason the GNOME > > > > update system would specifically require NetworkManager. > > > > > > > > Russel, can you post exactly what output you get from 'dnf remove > > > > NetworkManager'? Thanks. > > > > > > > > > [root@anglides etc]# dnf remove NetworkManager > > > Dependencies resolved. > > > =================================================================== > > > ============= > > > Package Arch Version Re > > > pository > > > > > > Size > > > =================================================================== > > > ============= > > > Removing: > > > NetworkManager x86_64 1:1.8.0-0.2.rc2.fc27 > > > @rawhide 5.2 M > > > NetworkManager-wifi x86_64 1:1.8.0-0.2.rc2.fc27 > > > @rawhide 161 k > > > control-center x86_64 1:3.24.1- > > > 1.fc27 @rawhide 18 M > > > gdm x86_64 1:3.24.1- > > > 1.fc27 @rawhide 2.1 M > > > gnome-initial-setup x86_64 3.24.0- > > > 1.fc27 @rawhide 2.5 M > > > gnome-shell x86_64 3.24.1- > > > 1.fc27 @rawhide 9.9 M > > > gnome-shell-extension-alternate-tab noarch 3.24.1- > > > 1.fc27 @rawhide 9.5 k > > > gnome-shell-extension-apps-menu noarch 3.24.1- > > > 1.fc27 @rawhide 30 k > > > gnome-shell-extension-common noarch 3.24.1- > > > 1.fc27 @rawhide 565 k > > > gnome-shell-extension-launch-new-instance > > > noarch 3.24.1- > > > 1.fc27 @rawhide 4.9 k > > > gnome-shell-extension-openweather noarch 1- > > > 0.28.20170307git48ee4af.fc27 > > > @r > > > awhide 500 k > > > gnome-shell-extension-places-menu noarch 3.24.1- > > > 1.fc27 @rawhide 23 k > > > gnome-shell-extension-user-theme noarch 3.24.1- > > > 1.fc27 @rawhide 7.0 k > > > gnome-shell-extension-window-list noarch 3.24.1- > > > 1.fc27 @rawhide 57 k > > > gnome-tweak-tool noarch 3.24.0- > > > 1.fc27 @rawhide 1.0 M > > > notify-python x86_64 0.1.1- > > > 32.fc26 @System 69 k > > > pulseaudio-gdm-hooks x86_64 10.0- > > > 4.fc26 @rawhide 354 > > > Removing unused dependencies: > > > switcheroo-control x86_64 1.1- > > > 2.fc26 @rawhide 52 k > > > > > > Transaction Summary > > > =================================================================== > > > ============= > > > Remove 18 Packages > > > > Aha: > > > > http://pkgs.fedoraproject.org/cgit/rpms/control-center.git/commit/?id > > =fc2b7c4ee0d62cf6ceb445356a788ab5fe90fb6a > > > > control-center had a dependency added on NetworkManager-wifi. > > That's likely the issue here (the other things being removed probably > > depend on control-center). > > > > Bastien, can you solve this problem some other way that doesn't > > involve > > GNOME getting a hard dependency on NetworkManager? > > Nope, sorry. Not having this dependency would mean that a 'dnf remove > anaconda" after an installation would remove NetworkManager-wifi, > breaking most of our users' systems. > > If you know another trick to avoid this, then feel free to make the > necessary changes to the package, but I don't see NetworkManager being > installed (and inactive) on one systemd-networkd user's machine being > much of a problem compared to users losing Wi-Fi access after removing > the now unused installer. It's actually happened 3 separate times to a > colleague and myself. Putting it in a relevant comps group may make dnf decide it's installed as part of that group, and not remove it with a 'dnf remove anaconda'... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
