Open andersk opened 5 years ago
@volth #46459 was not backported to 18.09. (The scenario I’m describing really happened to my 18.09 system, it’s not hypothetical.)
I agree, NetworkManager enabled as a side effect of enabling a desktop manager is surprising to say the least. To me, this was especially confusing as I was enabling and configuring dhcpcd and configuring for appropriate interfaces - which was working up until I enabled gnome3 for another user.
I'm not positive how exactly, but it would seem as though the config's intent to configure another network "utility/daemon/manager" could result in NetworkManager /not/ being enabled.
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Just came across that when trying to add SSH LUKS unlocking to a machine that uses NetworkManager.
Issue description
On a system with initrd networking configured with DHCP, if you change
services.xserver.desktopManager.gnome3.enable
totrue
, suddenlynetworking.networkmanager.enable
totrue
,networking.useDHCP
tofalse
,udhcpc
,You might agree that this is a surprising consequence of enabling a desktop environment.
Technical details
"x86_64-linux"
Linux 4.14.81, NixOS, 18.09.1373.50fb6820759 (Jellyfish)
yes
yes
nix-env (Nix) 2.1.3
"nixos-18.09.1373.50fb6820759"
""
/nix/var/nix/profiles/per-user/root/channels/nixos