How to fix “command not found” when it appears starting terminal on ubuntu
When I run the terminal in my elementary OS(Ubuntu 14.04 dist) it appears as follow:
Support: command not found
anargu@anargu-notebook-PC:~$
the first line (Support: ...) appeared after trying to install nodejs but I had problems to install it and I tried to install like 5 times in different ways and finally I could install it. But the "Support: command not found" appeared each time I run the terminal.
I'm new in ubuntu and I don't know what it refers with Support but I can type some commands like ls, cd, sudo apt-get and those work fine. So, please someone can help me?
Thanks in advance
linux ubuntu
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
|
show 1 more comment
When I run the terminal in my elementary OS(Ubuntu 14.04 dist) it appears as follow:
Support: command not found
anargu@anargu-notebook-PC:~$
the first line (Support: ...) appeared after trying to install nodejs but I had problems to install it and I tried to install like 5 times in different ways and finally I could install it. But the "Support: command not found" appeared each time I run the terminal.
I'm new in ubuntu and I don't know what it refers with Support but I can type some commands like ls, cd, sudo apt-get and those work fine. So, please someone can help me?
Thanks in advance
linux ubuntu
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
You see this everytime you startup the terminal app? Might be something hardcoded in your profile....( ~/.profile ) Edit/view this file to see if has any mention of the "support" cmd. Also.....look for a strange configuration in your bashrc or a mistyped parameter in your launch-terminal command in your menu. ( ~/.bashrc )
– Stephen R.
Dec 17 '15 at 2:05
When you said that I have to check the "profile" you were talking about the .profile that is located in /home right??? I will check that. And Also i was checking the bashrc but I don't know how to interpret the code and how to identify if something is wrong.
– Anargu
Dec 17 '15 at 3:35
I read .profile was only read when logging in the first time - if already logged in and open a terminal then just .basrc & maybe one other is run
– Xen2050
Dec 17 '15 at 12:11
To start trygrep Support ~/.*... then if you find check from where it is called from. It's a row strart. Else more clean you can follow line by line your initialization files. You shoul find around the end if it is an addition. Last you shoul have eaten a#character somewhere especially if you edited by hand... good hunt.
– Hastur
Dec 18 '15 at 5:32
Welcome aboard. Just curios - since you have posted on, and are aware of, our Ubuntu and Unix & Linux sister sites, why ask this question here?
– Mawg
Jan 8 at 7:35
|
show 1 more comment
When I run the terminal in my elementary OS(Ubuntu 14.04 dist) it appears as follow:
Support: command not found
anargu@anargu-notebook-PC:~$
the first line (Support: ...) appeared after trying to install nodejs but I had problems to install it and I tried to install like 5 times in different ways and finally I could install it. But the "Support: command not found" appeared each time I run the terminal.
I'm new in ubuntu and I don't know what it refers with Support but I can type some commands like ls, cd, sudo apt-get and those work fine. So, please someone can help me?
Thanks in advance
linux ubuntu
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
When I run the terminal in my elementary OS(Ubuntu 14.04 dist) it appears as follow:
Support: command not found
anargu@anargu-notebook-PC:~$
the first line (Support: ...) appeared after trying to install nodejs but I had problems to install it and I tried to install like 5 times in different ways and finally I could install it. But the "Support: command not found" appeared each time I run the terminal.
I'm new in ubuntu and I don't know what it refers with Support but I can type some commands like ls, cd, sudo apt-get and those work fine. So, please someone can help me?
Thanks in advance
linux ubuntu
linux ubuntu
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
asked Dec 17 '15 at 0:00
AnarguAnargu
7315
7315
You see this everytime you startup the terminal app? Might be something hardcoded in your profile....( ~/.profile ) Edit/view this file to see if has any mention of the "support" cmd. Also.....look for a strange configuration in your bashrc or a mistyped parameter in your launch-terminal command in your menu. ( ~/.bashrc )
– Stephen R.
Dec 17 '15 at 2:05
When you said that I have to check the "profile" you were talking about the .profile that is located in /home right??? I will check that. And Also i was checking the bashrc but I don't know how to interpret the code and how to identify if something is wrong.
– Anargu
Dec 17 '15 at 3:35
I read .profile was only read when logging in the first time - if already logged in and open a terminal then just .basrc & maybe one other is run
– Xen2050
Dec 17 '15 at 12:11
To start trygrep Support ~/.*... then if you find check from where it is called from. It's a row strart. Else more clean you can follow line by line your initialization files. You shoul find around the end if it is an addition. Last you shoul have eaten a#character somewhere especially if you edited by hand... good hunt.
– Hastur
Dec 18 '15 at 5:32
Welcome aboard. Just curios - since you have posted on, and are aware of, our Ubuntu and Unix & Linux sister sites, why ask this question here?
– Mawg
Jan 8 at 7:35
|
show 1 more comment
You see this everytime you startup the terminal app? Might be something hardcoded in your profile....( ~/.profile ) Edit/view this file to see if has any mention of the "support" cmd. Also.....look for a strange configuration in your bashrc or a mistyped parameter in your launch-terminal command in your menu. ( ~/.bashrc )
– Stephen R.
Dec 17 '15 at 2:05
When you said that I have to check the "profile" you were talking about the .profile that is located in /home right??? I will check that. And Also i was checking the bashrc but I don't know how to interpret the code and how to identify if something is wrong.
– Anargu
Dec 17 '15 at 3:35
I read .profile was only read when logging in the first time - if already logged in and open a terminal then just .basrc & maybe one other is run
– Xen2050
Dec 17 '15 at 12:11
To start trygrep Support ~/.*... then if you find check from where it is called from. It's a row strart. Else more clean you can follow line by line your initialization files. You shoul find around the end if it is an addition. Last you shoul have eaten a#character somewhere especially if you edited by hand... good hunt.
– Hastur
Dec 18 '15 at 5:32
Welcome aboard. Just curios - since you have posted on, and are aware of, our Ubuntu and Unix & Linux sister sites, why ask this question here?
– Mawg
Jan 8 at 7:35
You see this everytime you startup the terminal app? Might be something hardcoded in your profile....( ~/.profile ) Edit/view this file to see if has any mention of the "support" cmd. Also.....look for a strange configuration in your bashrc or a mistyped parameter in your launch-terminal command in your menu. ( ~/.bashrc )
– Stephen R.
Dec 17 '15 at 2:05
You see this everytime you startup the terminal app? Might be something hardcoded in your profile....( ~/.profile ) Edit/view this file to see if has any mention of the "support" cmd. Also.....look for a strange configuration in your bashrc or a mistyped parameter in your launch-terminal command in your menu. ( ~/.bashrc )
– Stephen R.
Dec 17 '15 at 2:05
When you said that I have to check the "profile" you were talking about the .profile that is located in /home right??? I will check that. And Also i was checking the bashrc but I don't know how to interpret the code and how to identify if something is wrong.
– Anargu
Dec 17 '15 at 3:35
When you said that I have to check the "profile" you were talking about the .profile that is located in /home right??? I will check that. And Also i was checking the bashrc but I don't know how to interpret the code and how to identify if something is wrong.
– Anargu
Dec 17 '15 at 3:35
I read .profile was only read when logging in the first time - if already logged in and open a terminal then just .basrc & maybe one other is run
– Xen2050
Dec 17 '15 at 12:11
I read .profile was only read when logging in the first time - if already logged in and open a terminal then just .basrc & maybe one other is run
– Xen2050
Dec 17 '15 at 12:11
To start try
grep Support ~/.*... then if you find check from where it is called from. It's a row strart. Else more clean you can follow line by line your initialization files. You shoul find around the end if it is an addition. Last you shoul have eaten a # character somewhere especially if you edited by hand... good hunt.– Hastur
Dec 18 '15 at 5:32
To start try
grep Support ~/.*... then if you find check from where it is called from. It's a row strart. Else more clean you can follow line by line your initialization files. You shoul find around the end if it is an addition. Last you shoul have eaten a # character somewhere especially if you edited by hand... good hunt.– Hastur
Dec 18 '15 at 5:32
Welcome aboard. Just curios - since you have posted on, and are aware of, our Ubuntu and Unix & Linux sister sites, why ask this question here?
– Mawg
Jan 8 at 7:35
Welcome aboard. Just curios - since you have posted on, and are aware of, our Ubuntu and Unix & Linux sister sites, why ask this question here?
– Mawg
Jan 8 at 7:35
|
show 1 more comment
3 Answers
3
active
oldest
votes
The bash error "xxxxxx: command not found" shows up when you try to run a command/program that's not installed or not in the path, etc. Per Hastur's comment, searching for "Support" in .bashrc is a great idea, and check .login & .profile too if they exist (I don't think they should be running just for opening a terminal.
Could be in the ~/.bashrc file. In general to find a mystery error I'd test it like this:
Try opening a terminal and type
source ~/.bashrc
If the error shows up, then it's definitely something in there that's the problem. Look through the file for the line that causes the error - could go line by line pasting into a terminal if it's not overwhelming, or add echo "step 1" ... echo "step 2" etc lines to narrow it down. Then remove/modify the offending line.
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
When I put in the terminal:source ~/.bashrcthen the terminal returns anotherSupport: command not foundSo I will check the file...
– Anargu
Dec 18 '15 at 16:20
It does show up then? Just open & edit .bashrc then, and fix/remove/comment out the line that's got "Support ...." in it
– Xen2050
Dec 18 '15 at 16:34
Yes, I could solve the problem I think, because I just commented a piece of code then The "support command not found" dissapeared. The origin of the problem is because I installed nativescript (nativescript.org) and part of this installations went to the bashrc file.
– Anargu
Dec 18 '15 at 16:55
add a comment |
Thanks Xen2050, I was checking my bashrc file (with echo "step1"...)and I found this part:
###-tns-completion-start-###
if [ -f /home/anargu/.tnsrc ]; then
source /home/anargu/.tnsrc
fi
###-tns-completion-end-###
Well I coul identify it because I installed nativescript (https://www.nativescript.org/) and this part of code correspond to it. When I commented (put several "#") those lines, the:
Support: command not found just dissapeared.
I think I solved this problem just commenting that part of code because then I couldn't find any problem at the moment. Thank you so much!
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
No problem, I'll give it an upvote :) those lines source (like "read/load") the /home/anargu/.tnsrc file, it must contain the "Support ..." line, maybe it's a comment that's not commented, maybe there's a program that wasn't installed correctly, or something else. If there's anything else in that file you want/need you could fix it, but if everything works well now then why bother ;-)
– Xen2050
Dec 19 '15 at 15:19
add a comment |
Answer by @Anargu lead me to the source of the problem. In ~/.tnsrc I had a comment on the first line that hasn't actually been commented out. The first word of the statement was Support, that's why the error showed that word.
I've opened the file, deleted the line, and the error stopped showing up.
answered Oct 26 '17 at 5:47
yperyper
1216
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1014471%2fhow-to-fix-command-not-found-when-it-appears-starting-terminal-on-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The bash error "xxxxxx: command not found" shows up when you try to run a command/program that's not installed or not in the path, etc. Per Hastur's comment, searching for "Support" in .bashrc is a great idea, and check .login & .profile too if they exist (I don't think they should be running just for opening a terminal.
Could be in the ~/.bashrc file. In general to find a mystery error I'd test it like this:
Try opening a terminal and type
source ~/.bashrc
If the error shows up, then it's definitely something in there that's the problem. Look through the file for the line that causes the error - could go line by line pasting into a terminal if it's not overwhelming, or add echo "step 1" ... echo "step 2" etc lines to narrow it down. Then remove/modify the offending line.
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
When I put in the terminal:source ~/.bashrcthen the terminal returns anotherSupport: command not foundSo I will check the file...
– Anargu
Dec 18 '15 at 16:20
It does show up then? Just open & edit .bashrc then, and fix/remove/comment out the line that's got "Support ...." in it
– Xen2050
Dec 18 '15 at 16:34
Yes, I could solve the problem I think, because I just commented a piece of code then The "support command not found" dissapeared. The origin of the problem is because I installed nativescript (nativescript.org) and part of this installations went to the bashrc file.
– Anargu
Dec 18 '15 at 16:55
add a comment |
The bash error "xxxxxx: command not found" shows up when you try to run a command/program that's not installed or not in the path, etc. Per Hastur's comment, searching for "Support" in .bashrc is a great idea, and check .login & .profile too if they exist (I don't think they should be running just for opening a terminal.
Could be in the ~/.bashrc file. In general to find a mystery error I'd test it like this:
Try opening a terminal and type
source ~/.bashrc
If the error shows up, then it's definitely something in there that's the problem. Look through the file for the line that causes the error - could go line by line pasting into a terminal if it's not overwhelming, or add echo "step 1" ... echo "step 2" etc lines to narrow it down. Then remove/modify the offending line.
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
When I put in the terminal:source ~/.bashrcthen the terminal returns anotherSupport: command not foundSo I will check the file...
– Anargu
Dec 18 '15 at 16:20
It does show up then? Just open & edit .bashrc then, and fix/remove/comment out the line that's got "Support ...." in it
– Xen2050
Dec 18 '15 at 16:34
Yes, I could solve the problem I think, because I just commented a piece of code then The "support command not found" dissapeared. The origin of the problem is because I installed nativescript (nativescript.org) and part of this installations went to the bashrc file.
– Anargu
Dec 18 '15 at 16:55
add a comment |
The bash error "xxxxxx: command not found" shows up when you try to run a command/program that's not installed or not in the path, etc. Per Hastur's comment, searching for "Support" in .bashrc is a great idea, and check .login & .profile too if they exist (I don't think they should be running just for opening a terminal.
Could be in the ~/.bashrc file. In general to find a mystery error I'd test it like this:
Try opening a terminal and type
source ~/.bashrc
If the error shows up, then it's definitely something in there that's the problem. Look through the file for the line that causes the error - could go line by line pasting into a terminal if it's not overwhelming, or add echo "step 1" ... echo "step 2" etc lines to narrow it down. Then remove/modify the offending line.
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
The bash error "xxxxxx: command not found" shows up when you try to run a command/program that's not installed or not in the path, etc. Per Hastur's comment, searching for "Support" in .bashrc is a great idea, and check .login & .profile too if they exist (I don't think they should be running just for opening a terminal.
Could be in the ~/.bashrc file. In general to find a mystery error I'd test it like this:
Try opening a terminal and type
source ~/.bashrc
If the error shows up, then it's definitely something in there that's the problem. Look through the file for the line that causes the error - could go line by line pasting into a terminal if it's not overwhelming, or add echo "step 1" ... echo "step 2" etc lines to narrow it down. Then remove/modify the offending line.
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
edited Dec 18 '15 at 16:33
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
answered Dec 17 '15 at 12:52
Xen2050Xen2050
10.5k31536
10.5k31536
When I put in the terminal:source ~/.bashrcthen the terminal returns anotherSupport: command not foundSo I will check the file...
– Anargu
Dec 18 '15 at 16:20
It does show up then? Just open & edit .bashrc then, and fix/remove/comment out the line that's got "Support ...." in it
– Xen2050
Dec 18 '15 at 16:34
Yes, I could solve the problem I think, because I just commented a piece of code then The "support command not found" dissapeared. The origin of the problem is because I installed nativescript (nativescript.org) and part of this installations went to the bashrc file.
– Anargu
Dec 18 '15 at 16:55
add a comment |
When I put in the terminal:source ~/.bashrcthen the terminal returns anotherSupport: command not foundSo I will check the file...
– Anargu
Dec 18 '15 at 16:20
It does show up then? Just open & edit .bashrc then, and fix/remove/comment out the line that's got "Support ...." in it
– Xen2050
Dec 18 '15 at 16:34
Yes, I could solve the problem I think, because I just commented a piece of code then The "support command not found" dissapeared. The origin of the problem is because I installed nativescript (nativescript.org) and part of this installations went to the bashrc file.
– Anargu
Dec 18 '15 at 16:55
When I put in the terminal:
source ~/.bashrc then the terminal returns another Support: command not found So I will check the file...– Anargu
Dec 18 '15 at 16:20
When I put in the terminal:
source ~/.bashrc then the terminal returns another Support: command not found So I will check the file...– Anargu
Dec 18 '15 at 16:20
It does show up then? Just open & edit .bashrc then, and fix/remove/comment out the line that's got "Support ...." in it
– Xen2050
Dec 18 '15 at 16:34
It does show up then? Just open & edit .bashrc then, and fix/remove/comment out the line that's got "Support ...." in it
– Xen2050
Dec 18 '15 at 16:34
Yes, I could solve the problem I think, because I just commented a piece of code then The "support command not found" dissapeared. The origin of the problem is because I installed nativescript (nativescript.org) and part of this installations went to the bashrc file.
– Anargu
Dec 18 '15 at 16:55
Yes, I could solve the problem I think, because I just commented a piece of code then The "support command not found" dissapeared. The origin of the problem is because I installed nativescript (nativescript.org) and part of this installations went to the bashrc file.
– Anargu
Dec 18 '15 at 16:55
add a comment |
Thanks Xen2050, I was checking my bashrc file (with echo "step1"...)and I found this part:
###-tns-completion-start-###
if [ -f /home/anargu/.tnsrc ]; then
source /home/anargu/.tnsrc
fi
###-tns-completion-end-###
Well I coul identify it because I installed nativescript (https://www.nativescript.org/) and this part of code correspond to it. When I commented (put several "#") those lines, the:
Support: command not found just dissapeared.
I think I solved this problem just commenting that part of code because then I couldn't find any problem at the moment. Thank you so much!
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
No problem, I'll give it an upvote :) those lines source (like "read/load") the /home/anargu/.tnsrc file, it must contain the "Support ..." line, maybe it's a comment that's not commented, maybe there's a program that wasn't installed correctly, or something else. If there's anything else in that file you want/need you could fix it, but if everything works well now then why bother ;-)
– Xen2050
Dec 19 '15 at 15:19
add a comment |
Thanks Xen2050, I was checking my bashrc file (with echo "step1"...)and I found this part:
###-tns-completion-start-###
if [ -f /home/anargu/.tnsrc ]; then
source /home/anargu/.tnsrc
fi
###-tns-completion-end-###
Well I coul identify it because I installed nativescript (https://www.nativescript.org/) and this part of code correspond to it. When I commented (put several "#") those lines, the:
Support: command not found just dissapeared.
I think I solved this problem just commenting that part of code because then I couldn't find any problem at the moment. Thank you so much!
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
No problem, I'll give it an upvote :) those lines source (like "read/load") the /home/anargu/.tnsrc file, it must contain the "Support ..." line, maybe it's a comment that's not commented, maybe there's a program that wasn't installed correctly, or something else. If there's anything else in that file you want/need you could fix it, but if everything works well now then why bother ;-)
– Xen2050
Dec 19 '15 at 15:19
add a comment |
Thanks Xen2050, I was checking my bashrc file (with echo "step1"...)and I found this part:
###-tns-completion-start-###
if [ -f /home/anargu/.tnsrc ]; then
source /home/anargu/.tnsrc
fi
###-tns-completion-end-###
Well I coul identify it because I installed nativescript (https://www.nativescript.org/) and this part of code correspond to it. When I commented (put several "#") those lines, the:
Support: command not found just dissapeared.
I think I solved this problem just commenting that part of code because then I couldn't find any problem at the moment. Thank you so much!
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
Thanks Xen2050, I was checking my bashrc file (with echo "step1"...)and I found this part:
###-tns-completion-start-###
if [ -f /home/anargu/.tnsrc ]; then
source /home/anargu/.tnsrc
fi
###-tns-completion-end-###
Well I coul identify it because I installed nativescript (https://www.nativescript.org/) and this part of code correspond to it. When I commented (put several "#") those lines, the:
Support: command not found just dissapeared.
I think I solved this problem just commenting that part of code because then I couldn't find any problem at the moment. Thank you so much!
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
answered Dec 18 '15 at 16:48
AnarguAnargu
7315
7315
No problem, I'll give it an upvote :) those lines source (like "read/load") the /home/anargu/.tnsrc file, it must contain the "Support ..." line, maybe it's a comment that's not commented, maybe there's a program that wasn't installed correctly, or something else. If there's anything else in that file you want/need you could fix it, but if everything works well now then why bother ;-)
– Xen2050
Dec 19 '15 at 15:19
add a comment |
No problem, I'll give it an upvote :) those lines source (like "read/load") the /home/anargu/.tnsrc file, it must contain the "Support ..." line, maybe it's a comment that's not commented, maybe there's a program that wasn't installed correctly, or something else. If there's anything else in that file you want/need you could fix it, but if everything works well now then why bother ;-)
– Xen2050
Dec 19 '15 at 15:19
No problem, I'll give it an upvote :) those lines source (like "read/load") the /home/anargu/.tnsrc file, it must contain the "Support ..." line, maybe it's a comment that's not commented, maybe there's a program that wasn't installed correctly, or something else. If there's anything else in that file you want/need you could fix it, but if everything works well now then why bother ;-)
– Xen2050
Dec 19 '15 at 15:19
No problem, I'll give it an upvote :) those lines source (like "read/load") the /home/anargu/.tnsrc file, it must contain the "Support ..." line, maybe it's a comment that's not commented, maybe there's a program that wasn't installed correctly, or something else. If there's anything else in that file you want/need you could fix it, but if everything works well now then why bother ;-)
– Xen2050
Dec 19 '15 at 15:19
add a comment |
Answer by @Anargu lead me to the source of the problem. In ~/.tnsrc I had a comment on the first line that hasn't actually been commented out. The first word of the statement was Support, that's why the error showed that word.
I've opened the file, deleted the line, and the error stopped showing up.
answered Oct 26 '17 at 5:47
yperyper
1216
add a comment |
Answer by @Anargu lead me to the source of the problem. In ~/.tnsrc I had a comment on the first line that hasn't actually been commented out. The first word of the statement was Support, that's why the error showed that word.
I've opened the file, deleted the line, and the error stopped showing up.
answered Oct 26 '17 at 5:47
yperyper
1216
add a comment |
Answer by @Anargu lead me to the source of the problem. In ~/.tnsrc I had a comment on the first line that hasn't actually been commented out. The first word of the statement was Support, that's why the error showed that word.
I've opened the file, deleted the line, and the error stopped showing up.
answered Oct 26 '17 at 5:47
yperyper
1216
Answer by @Anargu lead me to the source of the problem. In ~/.tnsrc I had a comment on the first line that hasn't actually been commented out. The first word of the statement was Support, that's why the error showed that word.
I've opened the file, deleted the line, and the error stopped showing up.
answered Oct 26 '17 at 5:47
yperyper
1216
edited Jan 8 at 5:57
answered Oct 26 '17 at 5:47
yperyper
1216
answered Oct 26 '17 at 5:47
yperyper
1216
answered Oct 26 '17 at 5:47
yperyper
1216
1216
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1014471%2fhow-to-fix-command-not-found-when-it-appears-starting-terminal-on-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You see this everytime you startup the terminal app? Might be something hardcoded in your profile....( ~/.profile ) Edit/view this file to see if has any mention of the "support" cmd. Also.....look for a strange configuration in your bashrc or a mistyped parameter in your launch-terminal command in your menu. ( ~/.bashrc )
– Stephen R.
Dec 17 '15 at 2:05
When you said that I have to check the "profile" you were talking about the .profile that is located in /home right??? I will check that. And Also i was checking the bashrc but I don't know how to interpret the code and how to identify if something is wrong.
– Anargu
Dec 17 '15 at 3:35
I read .profile was only read when logging in the first time - if already logged in and open a terminal then just .basrc & maybe one other is run
– Xen2050
Dec 17 '15 at 12:11
To start try
grep Support ~/.*... then if you find check from where it is called from. It's a row strart. Else more clean you can follow line by line your initialization files. You shoul find around the end if it is an addition. Last you shoul have eaten a#character somewhere especially if you edited by hand... good hunt.– Hastur
Dec 18 '15 at 5:32
Welcome aboard. Just curios - since you have posted on, and are aware of, our Ubuntu and Unix & Linux sister sites, why ask this question here?
– Mawg
Jan 8 at 7:35