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

Spacenavd service not enabled despite being enabled in config #366684

Open
Joseph-DiGiovanni opened this issue Dec 20, 2024 · 2 comments · May be fixed by #366768
Open

Spacenavd service not enabled despite being enabled in config #366684

Joseph-DiGiovanni opened this issue Dec 20, 2024 · 2 comments · May be fixed by #366768
Labels
0.kind: bug Something is broken

Comments

@Joseph-DiGiovanni
Copy link

Joseph-DiGiovanni commented Dec 20, 2024

The spacenavd service does not start automatically as expected. It works fine once started with systemctl start spacenavd.service.

Steps to reproduce the behavior:

  1. Add hardware.spacenavd.enable = true; to config
  2. Rebuild
  3. Reboot
  4. Spacenavd.service is inactive, systemctl is-enabled spacenavd.service returns linked rather than enabled

My full config is available here with the relevant changes

 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.66, NixOS, 24.11 (Vicuna), 24.11.20241216.3945713`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.10`
 - nixpkgs: `/nix/store/wj2qla569hnxwqfc26imv5hqbxc1rc27-source`

Notify maintainers

@Sohalt


Note for maintainers: Please tag this issue in your PR.


Add a 👍 reaction to issues you find important.

@Joseph-DiGiovanni Joseph-DiGiovanni added the 0.kind: bug Something is broken label Dec 20, 2024
@Joseph-DiGiovanni
Copy link
Author

It appears to start automatically as intended when I manually add systemd.services.spacenavd.wantedBy = [ "graphical.target" ]; to my config, even though the unit file already contains the same. Is this requirement expected behavior?

@Sohalt
Copy link
Contributor

Sohalt commented Dec 20, 2024

Looks like nixos does not pull the WantedBy directive from the upstream service unit #81138

Thanks for the report. I added it.

@Sohalt Sohalt linked a pull request Dec 20, 2024 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants