nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
6.81k stars 1.78k forks source link

bug: Critical Errors starting up with fish. Cannot nix-build nor enter window manager. #5577

Open Dandandooo opened 3 months ago

Dandandooo commented 3 months ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

Directly upon login to my profile, I am greeted with the following message. IMG_3140 Large The greeting was written by me, ignore that.

I cannot use anything usually present in my current system path, nor essential utilities. My system apps are not found, yet the root user is perfectly fine.

My dotfiles are here, and they were built with home-manager switch. No flakes used.

I cannot home-manager switch or uninstall because nix-build is not found.

Maintainer CC

No response

System information

I can't run this since nix-shell is not found in path apparently. Nor are critical system functions such as `kill`, `which`, `uname`, `hyprland`, and even `nix-build`. It's not a system problem, since root user works just fine.

I am running NixOS 24.05 on a desktop PC with a Ryzen 9 5900X and a Radeon RX 6950.
Dandandooo commented 3 months ago

Bash has the same problems, but not as many error messages.

Dandandooo commented 3 months ago

I found that the problem was including /opt/homebrew/bin in my path.

stale[bot] commented 1 week ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve 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

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.