bug: All home-manager services are not running.

[winston0410]

Is there an existing issue for this?

• I have searched the existing issues

Issue description

All services inside home-manager are not running. This is the file that I have defined my home-manager module:

{ config, lib, pkgs, ... }:

{
  imports = [
    <home-manager/nixos>
    # ./services/fusuma.nix
    # ./service-configuration.nix
  ];

  environment.systemPackages = with pkgs; [ xautomation ];

  home-manager.useUserPackages = true;
  home-manager.useGlobalPkgs = true;

  home-manager.users.hugosum = { pkgs, ... }: {
    programs.zoxide = {
      enable = true;
      enableZshIntegration = true;
      enableFishIntegration = true;
    };

    programs.fzf = {
      enable = true;
      # enableZshIntegraton = true;
      enableFishIntegration = true;
    };

    programs.direnv = {
      enable = true;
      enableZshIntegration = true;
      enableFishIntegration = true;
    };

    services.lorri = { enable = true; };

    services.sxhkd = {
      enable = true;
      extraConfig = ''
        control + n
            xte "key Down"
      '';
    };

  };
}

Then I just import this file into configuration.nix like this:

{ config, pkgs, ... }:

let unstable = import <unstable> { };
in {
  imports = [
    ./hardware-configuration.nix
    ./xserver.nix
    ./home-manager.nix
    ./shell.nix
    ./docker.nix
  ];

  users = {
    mutableUsers = false;
    users.hugosum = {
      isNormalUser = true;
      home = "/home/hugosum";
      extraGroups = [ "wheel" "networkmanager" ];
  };
}

I can confirm that I am running the correct user:

❯ whoami
hugosum

And when I check systemctl --user, I cannot find all the defined service direnv, lorri and sxhkd:

  UNIT                                                                                       >
  sys-devices-LNXSYSTM:00-LNXPWRBN:00-input-input3-event3.device                             >
  sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0A08:00-LNXVIDEO:00-input-input6-event6.device      >
  sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0C0C:00-input-input1-event1.device                  >
  sys-devices-LNXSYSTM:00-LNXSYBUS:00-PNP0C0E:00-input-input2-event2.device                  >
  sys-devices-pci0000:00-0000:00:02.0-backlight-acpi_video0.device                           >
  sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2deDP\x2d1-intel_backlight.device     >
  sys-devices-pci0000:00-0000:00:1c.0-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device       >
  sys-devices-pci0000:00-0000:00:1c.0-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device       >
  sys-devices-pci0000:00-0000:00:1c.0-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device       >
  sys-devices-pci0000:00-0000:00:1c.0-0000:01:00.0-nvme-nvme0-nvme0n1.device                 >
  sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-net-wlp2s0.device                         >
  sys-devices-pci0000:00-0000:00:1e.0-dw\x2dapb\x2duart.2-tty-ttyS0.device                   >
  sys-devices-pci0000:00-0000:00:1e.3-pxa2xx\x2dspi.3-spi_master-spi2-spi\x2dAPP000D:00-input>
  sys-devices-pci0000:00-0000:00:1e.3-pxa2xx\x2dspi.3-spi_master-spi2-spi\x2dAPP000D:00-leds->
  sys-devices-pci0000:00-0000:00:1f.3-sound-card0-controlC0.device                           >
  sys-devices-platform-serial8250-tty-ttyS1.device                                           >
  sys-devices-platform-serial8250-tty-ttyS2.device                                           >
  sys-devices-platform-serial8250-tty-ttyS3.device                                           >
  sys-devices-virtual-input-mice.device                                                      >
  sys-devices-virtual-misc-rfkill.device                                                     >
  sys-devices-virtual-misc-tun.device                                                        >
  sys-devices-virtual-net-docker0.device                                                     >
  sys-module-configfs.device                                                                 >
  sys-module-fuse.device                                                                     >
  sys-module-tun.device                                                                      >
  sys-subsystem-net-devices-docker0.device   

Maintainer CC

No response

System information

❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.48, NixOS, 21.05.1408.9376bf7b342 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.12`
 - channels(hugosum): `"home-manager-21.05, nixos-21.05.1408.9376bf7b342, unstable-21.11pre301044.87807e64a5e"`
 - channels(root): `"home-manager-21.05, nixos-21.05.1408.9376bf7b342, unstable-21.11pre301439.f9e81f7ad87"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

[rycee]

Unfortunately HM doesn't start/stop systemd services by default on activation, only prints suggested systemctl commands to run. If you look in the logs for the home-manager-hugosum.service then it may contain something to that effect, e.g., by running journalctl -u home-manager-hugosum.service. You can try adding

systemd.user.startServices = "sd-switch";

or

systemd.user.startServices = "legacy";

to have HM automatically run the necessary commands automatically.

About sxhkd, it is started from .xsession, which only happens if you let HM manage your X session.

[winston0410]

I have just tried both sd-switch and legacy, and still the output for journalctl -u home-manager-hugosum.service is identical with the original suggest.

-- Journal begins at Sat 2021-07-03 10:23:56 BST, ends at Sat 2021-08-07 16:27:24 BST. --
Aug 07 16:11:04 nixos systemd[1]: Starting Home Manager environment for hugosum...
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating home-manager configuration for hugosum
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Starting home manager activation
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating checkFilesChanged
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating checkLinkTargets
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating writeBoundary
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating installPackages
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating linkGeneration
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Cleaning up orphan links from /home/hugosum
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: No change so reusing latest profile generation 26
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Creating home file links in /home/hugosum
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating onFilesChange
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: Activating reloadSystemd
Aug 07 16:11:04 nixos hm-activate-hugosum[572]: User systemd daemon not running. Skipping reload.
Aug 07 16:11:04 nixos systemd[1]: Finished Home Manager environment for hugosum.

Just want to double confirm, as I am running in nixos, do I need to install home-manager and run home-manager switch as well, or I only need to import the config for home-manager into configuration.nix and run nixos-rebuild switch?

[berbiche]

@winston0410 are you doing these manipulations while being logged in as the user "hugosum"? That could explain the systemd session not running for your user.

[winston0410]

@berbiche I am running the command as hugosum

~
❯ whoami
hugosum

~
❮ journalctl -b -u home-manager-hugosum.service
-- Journal begins at Sat 2021-07-03 10:23:56 BST, ends at Sun 2021-08-08 10:17:36 BST. --
Aug 08 10:16:35 nixos systemd[1]: Starting Home Manager environment for hugosum...
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating home-manager configuration for hug>
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Starting home manager activation
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating checkFilesChanged
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating checkLinkTargets
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating writeBoundary
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating installPackages
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating linkGeneration
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Cleaning up orphan links from /home/hugosum
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: No change so reusing latest profile generatio>
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Creating home file links in /home/hugosum
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating onFilesChange
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: Activating reloadSystemd
Aug 08 10:16:35 nixos hm-activate-hugosum[583]: User systemd daemon not running. Skipping rel>
Aug 08 10:16:35 nixos systemd[1]: Finished Home Manager environment for hugosum.

And my current config has set startService as "sd-switch"

     systemd = { user.startServices = "sd-switch"; };

[stale]

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.

Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[mzabani]

Perhaps we can revive this issue? I have the exact same problem.

$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.76, NixOS, 21.05.3964.6c0c3014634 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(mzabani): `"home-manager-21.05, nixpkgs-21.05.3964.6c0c3014634"`
 - channels(root): `"nixos-21.05.3964.6c0c3014634, home-manager-21.05, nixpkgs-21.05.3964.6c0c3014634"`
 - nixpkgs: `/home/mzabani/.nix-defexpr/channels/nixpkgs`

And also:

$ journalctl -b -u home-manager-mzabani.service
-- Journal begins at Wed 2019-06-26 16:14:21 -03, ends at Tue 2021-11-23 16:34:01 -03. --
nov 23 16:28:16 nixos systemd[1]: Starting Home Manager environment for mzabani...
nov 23 16:28:16 nixos hm-activate-mzabani[725]: Activating home-manager configuration for mzabani
nov 23 16:28:16 nixos hm-activate-mzabani[725]: Starting home manager activation
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Activating checkFilesChanged
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Activating checkLinkTargets
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Activating writeBoundary
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Activating installPackages
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Activating linkGeneration
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Cleaning up orphan links from /home/mzabani
nov 23 16:28:17 nixos hm-activate-mzabani[725]: No change so reusing latest profile generation 19
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Creating home file links in /home/mzabani
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Activating onFilesChange
nov 23 16:28:17 nixos hm-activate-mzabani[725]: Activating reloadSystemd
nov 23 16:28:17 nixos hm-activate-mzabani[725]: User systemd daemon not running. Skipping reload.
nov 23 16:28:17 nixos systemd[1]: Finished Home Manager environment for mzabani.

Also, this happens when I boot my machine, but if I restart my home-manager unit I get something different:

$ systemctl restart home-manager-mzabani.service
$ journalctl -b -u home-manager-mzabani.service
nov 23 16:40:07 nixos systemd[1]: home-manager-mzabani.service: Succeeded.
nov 23 16:40:07 nixos systemd[1]: Stopped Home Manager environment for mzabani.
nov 23 16:40:07 nixos systemd[1]: home-manager-mzabani.service: Consumed 0 CPU time, received 824B IP traffic, sent 824B IP t>
nov 23 16:40:07 nixos systemd[1]: Stopping Home Manager environment for mzabani...
nov 23 16:40:07 nixos systemd[1]: Starting Home Manager environment for mzabani...
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating home-manager configuration for mzabani
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Starting home manager activation
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating checkFilesChanged
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating checkLinkTargets
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating writeBoundary
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating installPackages
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating linkGeneration
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Cleaning up orphan links from /home/mzabani
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Creating profile generation 21
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Creating home file links in /home/mzabani
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating onFilesChange
nov 23 16:40:07 nixos hm-activate-mzabani[4610]: Activating reloadSystemd
nov 23 16:40:07 nixos hm-activate-mzabani[4715]: Started org.gnome.Shell@wayland.service - deactivating

Even then, it seems the systemd mount and system service I have defined don't run.

I have also set systemd.user.startServices to both "sd-switch"and"legacy"`, but neither worked (the outputs above are for "sd-switch"). I'm new to home-manager but can provide more information if it helps.

[berbiche]

@mzabani can you check whether there's a systemd instance running for your user?
systemctl status "user@$(id -u)".service

I'm not sure what could prevent sd-switch from communicating with the user systemd session.