Can't Find Installed Nix Packages via System Search in Ubuntu 24 with Home-Manager

Understanding the Environment Isolation

Nix operates on a purely functional model where every package is stored in an immutable store path, such as /nix/store/.... Unlike traditional package managers that install files into system directories like /usr/bin, Nix creates symlinks from a user-specific profile directory to these store paths. When you use Home-Manager, it manages your dotfiles and user-level configurations, but it does not automatically inject the Nix binary locations into the global system environment variables unless explicitly configured.

In Ubuntu 24, the desktop environment relies heavily on environment variables like PATH and XDG_DATA_DIRS to locate executables and application metadata. If Home-Manager does not export the Nix profile path to these variables during the session initialization phase, the desktop search index and the terminal will fail to find the packages you have installed via nixpkgs.

The Role of home.sessionVariables

The primary mechanism for fixing this in Home-Manager is the home.sessionVariables attribute set. This allows you to define environment variables that are available to all processes spawned within your user session. To make Nix packages discoverable, you must ensure that the Nix profile bin directory is prepended to the PATH.

Without this configuration, even if you run nix-shell -p vim successfully inside a specific shell, closing that shell removes the temporary PATH modification. The system-wide search tools do not see this transient change, leading to the perception that the package is "missing" from the system.

Configuring Home-Manager for Global Visibility

To permanently expose Nix-installed packages to the Ubuntu desktop environment, you need to modify your home.nix file. The following steps outline the necessary configuration changes to bridge the gap between Nix and the Ubuntu desktop layer.

1. Edit your Home-Manager configuration: Open your ~/.config/nixpkgs/home.nix file (or wherever your Home-Manager config resides).
2. Add session variables: Include the home.sessionVariables section. You should set PATH to include the Nix profile. A common pattern is to append the Nix profile bin to the existing PATH.

home.sessionVariables = {
  PATH = "${config.home.homeDirectory}/.nix-profile/bin:$PATH";
};

This configuration ensures that every time your graphical session starts, the system checks the .nix-profile/bin directory for executables. This is critical for Ubuntu 24, which uses systemd user sessions to manage environment variables.

Integrating with XDG Data Directories

While PATH handles executable discovery, application menus and desktop search often rely on XDG_DATA_DIRS. Nix stores desktop entries (files ending in .desktop) in its own data directory. If this path is not included in XDG_DATA_DIRS, the desktop environment will not populate the application menu with Nix-installed apps.

home.sessionVariables = {
  PATH = "${config.home.homeDirectory}/.nix-profile/bin:$PATH";
  XDG_DATA_DIRS = "${config.home.homeDirectory}/.nix-profile/share:${config.home.homeDirectory}/.local/share:/usr/share";
};

By adding the Nix profile share directory to XDG_DATA_DIRS, you allow GNOME Shell and other desktop environments to read the application metadata files generated by Nix packages. This makes icons and names appear in the system search bar.

Rebuilding and Verifying the Configuration

After updating your home.nix file, you must apply the changes. Home-Manager does not apply changes in real-time; it generates a new configuration and activates it upon request.

1. Apply the configuration: Run the command home-manager switch in your terminal. This will compile your configuration and update the symlinks in your home directory.
2. Restart your session: For environment variable changes to take full effect in a graphical session, you often need to log out and log back in. Alternatively, restarting the display manager or simply opening a new terminal may suffice for PATH updates, but a full logout is recommended for XDG_DATA_DIRS changes.
3. Verify visibility: Once logged back in, open the system search (usually Super key) and type the name of a Nix-installed package, such as firefox or vim. It should now appear in the results.

If the packages still do not appear, check if your desktop environment caches application data. In GNOME, you might need to clear the icon cache or restart the shell (Alt+F2, then r). However, in most cases, the environment variable configuration resolves the issue immediately after a session restart.

Handling Conflicts with System Packages

Sometimes, Ubuntu’s default package manager might conflict with Nix packages if they share the same name. Because Nix profiles are added to the front of the PATH, Nix versions usually take precedence. If you want to prioritize system packages over Nix packages for certain binaries, you can adjust the order in the PATH string. However, for search visibility, the priority matters less than the inclusion of the directory itself.

Related Resources

If you encounter issues while managing these packages, you may find it useful to review how to handle package changes or installation preferences. For instance, if you need to undo recent changes to your Nix shell environment, you can refer to guides on reverting package changes. Additionally, understanding how to install specific packages without their recommended dependencies can help streamline your Nix profile.

Frequently Asked Questions

Why do Nix packages work in the terminal but not in the GUI?

This occurs because the terminal inherits the environment variables from your current shell session, whereas the GUI relies on the session variables defined in your display manager. Ensuring home.sessionVariables includes the Nix PATH and XDG_DATA_DIRS fixes this discrepancy.

Do I need to reinstall packages after changing Home-Manager config?

No, you do not need to reinstall the packages. Changing the environment variables only affects how the system locates the already installed binaries. After running home-manager switch and logging out/in, the existing installations become visible.

Can I use Home-Manager to manage system-wide Nix packages?

Home-Manager is designed for user-level configuration. While it manages the user Nix profile, it does not manage the system-wide Nix store. For system-wide visibility, you would need to configure the Nix daemon and system-level environment variables separately, which is beyond the scope of typical Home-Manager usage.

What if my desktop search still doesn't show the icons?

If the text appears but icons do not, ensure that XDG_DATA_DIRS includes the Nix profile share directory. You may also need to clear the desktop environment's cache or restart the shell interface to force a re-read of the application metadata files.

Is it safe to add Nix paths to the global PATH?

Yes, it is safe. Nix isolates packages in its own store, preventing conflicts with system libraries. Adding the Nix profile to your PATH is a standard practice and does not compromise system stability, provided you trust the sources of the Nix packages you install.