8/14/2023 0 Comments Gedit command not found in bashIt was only then that I saw the contents of the file in which I had several paths added to the file. bahsrc file through running the command line cat. bashrc by running the command PATH=/usr/bin:/usr/sbin. I learned that once I am in the diagnostic mode through the command Ctrl+Alt+F2 right after unsuccessful login, I can temporarily fix the messed up file. bashrc and look inside it and make needed changes permanently so my system logins appropriately leads me into its normal graphical mode where I see and utilize all Fedora features. So now, my question is whether there is a command-line based method that I can open. This time I don't know how I made changes in it that it caused all the issues explained here. I remember that I always used to make slight changes in the. However, I don't know why the former command (sudo) gedit ~/.bashrc is not working either. And instead I should run it in the following format: source ~/.bashrc Now, learning from the answer, I am not supposed to run this latter command as it is not executable. Or running commands like this one: ~/.bash_profileīash: /home/bbenjamin/.bash_profile: Permission denied. (gedit:1397): Gtk-WARNING **:cannot open display: Unable to init server: Could not connect: Connection refused However, I am receiving error messages like: bashrc file and fix its issues permanently (assuming that I can have access to its original version somehow.) To do this, I need to run commands like (sudo) gedit ~/.bashrc To make this possible in particular I need to open my. However, I still need to logging normally so that I can make use of all the graphics and other features of Fedora which is impossible in the diagnostic mode. The only time I was successful in getting most commands get realized by the shell was when I ran the following code (as mentioned by in the answer): PATH=/usr/bin:/usr/sbinĪfter which at least I could look for and see my files and folders and programs (since most commands are getting realized.) It is here that none of the commands are recognized by the shell no matter what. In this mode, then the login prompt appearĪfter entering my username, then it says:Īfter entering my password, then it says: I was able to login to my system only after entering the diagnostic mode by pressing Ctrl+Alt+F2 right after reboot and login into the main startup which fails under normal conditions. bashrc (which I can no longer see inside it by using the following command:) The only thing I can think of is some possible automatic update that I was not aware of or messing my. Would you mind letting me know how to fix such issue when actually no command is accepted in the diagnostic mode in the shell by saying the following? The last line that I saw a complete stop was saying: I tried to do diagnostics by pressing CTRL+ALT+F2 when the screen goes black to see where actually it stops working. However, to my surprise I noticed that the system is not starting up after login. I thought if I restart and reboot the system, the issue should resolve. Today, as I was trying to continue running my codes in the command-line shell, I noticed that none of the commands are actually recognized by the shell in Fedora 21 (kernel 4.1.686 on an i686 (tty2)). Below Additions, there is a section called, "resolution," where I have added extra steps that I have taken in order to resolve this issue: This is added under the headline Additions below the question. Upon the request of some users, I decided to add all the intermediate steps and results to my initial post so that users can better walk me through a solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |