No command "reboot" found in bash any more

SOLUSfiddler

I've been using the command "reboot" for ages in my bash terminal.
Why doesn't it work anymore?
What can I use instead?

BloodFeastMan

SOLUSfiddler Try "sudo shutdown -r now"

elfprince

SOLUSfiddler

SOLUSfiddler $ which reboot /sbin/reboot
Make sure /sbin is in your PATH.

Staudey

SOLUSfiddler What does echo $PATH show for you?

SOLUSfiddler

BloodFeastMan
Yes, thank you, that worked.
But why such a complicated command as opposed to the short "reboot"?

BloodFeastMan

SOLUSfiddler reboot is a symlink, there's no actual binary named "reboot". If your symlink's no longer there, you could just make short bash script with the name "reboot" (or any other name for that matter) with the above command and put it in your path, hope this helps!

SOLUSfiddler

BloodFeastMan
Thank you.
I would like to know why the command doesn't work anymore - I haven't changed anything that might have had this effect, just regularly updated my computer. So, somewhere along the line someone must have changed something and I would like to know what that was.
Maybe someone reading this can give me an answer.

snowee

elfprince
I have the same problem, I cannot execute a plain reboot

when I do a which reboot, i get the following
which: no reboot in (/usr/local/bin:/usr/bin:/bin:/snap/bin)

What should I do next please? I don't know how to edit the path ... is it in my bash.rc?
i never edited my path before, am concerned that i may break something if I do so.

snowee

Staudey I have the same issue as SolusFiddler

echo $PATH

I get :
/usr/local/bin:/usr/bin:/bin:/snap/bin

elfprince

snowee Edit your .bashrc file. Add on a new line export PATH=/sbin:$PATH

snowee

elfprince do I need to reinitialize my bashrc after saving the changes and exiting?

or should I just reboot the bashrc changes to take effect?

thank you.

snowee

elfprince
Thank you very much, it worked. I can do a reboot again.

I can only hope that the next sync will not make any further changes to the PATH again.

WetGeek

snowee do I need to reinitialize my bashrc

If you mean "close and reopen bash," the answer is yes. Bashrc is read when bash starts up.

BloodFeastMan

In addition to the good advice you've received, you can always re-read your .bashrc without re-booting with the command line source ~/.bashrc

infinitymdm

@snowee Glad you got things working, but I can't help but wonder: how did your PATH get modified in the first place? On my fully updated system, I get

marcus@fiora ~ $ echo $PATH
/home/marcus/.local/bin:/usr/sbin:/usr/bin

which I'm pretty sure is bog-standard. Somewhere on your system that's getting changed. Likely some script is rewriting your path variable (e.g. export PATH=/usr/bin:/bin or something similar) instead of adding to it (e.g. export PATH=/my/custom/dir/bin:$PATH). I'd bet it's the same script that's putting /usr/local/bin on your PATH; that doesn't seem to be a standard location in my experience.

Are you running any software that you suspect may make changes to your PATH?

elfprince

infinitymdm My $PATH is much longer than yours and it hasn't been changed, or I would see it right away. Yours is very short.

snowee

infinitymdm I am very mystified too.

Mine was a pretty bog-standard Solus Budgie which I recently installed using the v4.5 ISO a few weeks ago.

I have ran the weekly sync about 3-5 times since then, excluding the first sync done after the ISO install.

I didn't install much programs, except for nvidia drivers, gufw, Steam and Heroic Launcher.
I didn't uninstall anything either.
I didn't modify my bashrc profile, I won't dare to.

Perhaps you could share with me what are your thoughts on what might have changed my PATH settings?

If a recent sync changed our PATH, then why wasn't such an important thing mentioned in the patch notes?

I have never encountered this issue before in my 5 years of using Solus Budgie.

infinitymdm

elfprince My mistake, you are correct. I forgot that I had removed snapd from this system, which would change PATH a bit. There are probably a couple of other places where it differs from a brand-new system. Out of curiosity, what does your PATH look like?

elfprince

infinitymdm
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/snap/bin:/home/sasha/local/bin/:/home/sasha/bin:/home/sasha/.local/bin

infinitymdm

This commit seems relevant to this thread: https://github.com/getsolus/packages/commit/395c7d4ade85367a943460a3b800764b9a592001

infinitymdm

snowee It looks like somehow your PATH doesn't have any system binary directories. I would expect at least /usr/sbin, if not both /sbin and /usr/sbin. Those should get added to your PATH by profile setup scripts that run any time you log in. Edit to clarify: Those directories should already be on your path, and you shouldn't have to add them with your own changes to ~/.bashrc.

As far as how this happened: who knows? It didn't happen on my machine; I still have all those system binaries available because /usr/sbin is in my PATH. I suspect there is some offending piece of software that you have installed which I do not. The most likely explanation I can think of is that someone in the software supply chain made a mistake that got propagated to our packages, and thus to your system.

Now, there is a bit more troubleshooting we can do:

Could you post the output of eopkg hs -l1? That will give a list of the packages upgraded on your system in the previous sync, and could help identify a package which has a mistake.
Could you post the output of eopkg lr? If you happen to be on the unstable repo, that could explain some things. I don't think you are, but it never hurts to check.