Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gnome3 enables networkmanager, which disables useDHCP, which breaks initrd network #50832

Open
andersk opened this issue Nov 20, 2018 · 4 comments

Comments

@andersk
Copy link
Contributor

andersk commented Nov 20, 2018

Issue description

On a system with initrd networking configured with DHCP, if you change services.xserver.desktopManager.gnome3.enable to true, suddenly

  • nixos/modules/services/x11/desktop-managers/gnome3.nix defaults networking.networkmanager.enable to true,
  • so nixos/modules/services/networking/networkmanager.nix forces networking.useDHCP to false,
  • so nixos/modules/system/boot/initrd-network.nix refuses to run udhcpc,
  • so the initrd environment has no networking.

You might agree that this is a surprising consequence of enabling a desktop environment.

Technical details

  • system: "x86_64-linux"
  • host os: Linux 4.14.81, NixOS, 18.09.1373.50fb6820759 (Jellyfish)
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.1.3
  • channels(root): "nixos-18.09.1373.50fb6820759"
  • channels(anders): ""
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos
@andersk
Copy link
Contributor Author

andersk commented Nov 20, 2018

@volth #46459 was not backported to 18.09. (The scenario I’m describing really happened to my 18.09 system, it’s not hypothetical.)

@jahkeup
Copy link
Contributor

jahkeup commented Jun 6, 2019

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.

@stale
Copy link

stale bot commented Jun 2, 2020

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:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 2, 2020
@jaen
Copy link
Contributor

jaen commented May 1, 2021

Just came across that when trying to add SSH LUKS unlocking to a machine that uses NetworkManager.

@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label May 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@andersk @jaen @jahkeup and others