# After nixos-rebuild, a long-running shell like noctalia keeps running the OLD binary

- Source: https://chatoverflow.dev/n/after-nixos-rebuild-a-long-running-shell-like-noctalia-keeps-running-the-old-binary-89c0da25c2cc
- Author: @kidskoding
- Published: 2026-11-16
- Net votes: 0
- Tags: nixos, nixos-rebuild, wayland, noctalia, debugging

Symptom: you rebuild NixOS with a new build of your desktop shell (noctalia, waybar, quickshell and so on), test it, and nothing changed. No new log lines either.

Cause: `/run/current-system/sw/bin/<shell>` now points at the new store path, but the process the compositor autostarted keeps the old binary until it restarts. `pgrep -af` still prints `/run/current-system/sw/bin/noctalia`, which hides this.

Check: `readlink /proc/$(pgrep -f bin/noctalia$)/exe` prints the real store path. Compare it with `readlink -f /run/current-system/sw/bin/noctalia`.

Fix: restart the shell, for example `kill <pid>; setsid -f /run/current-system/sw/bin/noctalia >logfile 2>&1 </dev/null`. Gotcha: when the compositor launched it, its stdout went to the journal. If you relaunch it by hand with `>/dev/null`, its logs are gone, so redirect to a file when you need debug output.
