man command not working in Ubuntu 18.04
up vote
0
down vote
favorite
My man command is not working at all on my Ubuntu 18.04 machine. Unlike most of the cases I have found described in the internet, where there is an error message after calling man, I do not get any output/ error message at all
If I type which man
I will get /usr/bin/man. And I have checked with echo PATH that/usr/bin is on my PATH.
I have already tried sudo apt install --reinstall man-db, restarted the terminal, but no success.
Does anyone know what the problem can be?
18.04 manpage
asked Nov 21 at 9:30
BCArg
212212
add a comment |
up vote
0
down vote
favorite
My man command is not working at all on my Ubuntu 18.04 machine. Unlike most of the cases I have found described in the internet, where there is an error message after calling man, I do not get any output/ error message at all
If I type which man
I will get /usr/bin/man. And I have checked with echo PATH that/usr/bin is on my PATH.
I have already tried sudo apt install --reinstall man-db, restarted the terminal, but no success.
Does anyone know what the problem can be?
18.04 manpage
asked Nov 21 at 9:30
BCArg
212212
What do you get if you trywhereis man? This should provide any locations forman, plus the locations for the manual pages (for the commandman)
– guiverc
Nov 21 at 9:54
I getman: /usr/bin/man /usr/local/man /usr/share/man /usr/share/man/man1/man.1.gz /usr/share/man/man7/man.7.gzNone of them work by callingmanwith the full path (some are directories). But thewhichcommand will tell me whichmanlinux will call when callingman, right? As I described in my question it is /usr/bin/man, which is in my $PATH
– BCArg
Nov 21 at 10:02
maybe you can runstrace manand then paste the debug info in some nopaste site?(since the info would be long)
– Alvin Liang
Nov 21 at 10:12
I would check you have some free disk space (df -h) in case it needs it to operate. Next I woulddpkg -S /usr/bin/manto ensure your found program comes fromman-db(as expected). I'm not sure what you mean by "calling man with the full path" as to access page 1 youman 1 man, to access page 7man 7 man(which doesn't use the path; unless you meant/usr/bin/man 1 manto view page 1). If you check file type of your binary (ie.file /usr/bin/man) do you get a ELF LSB shared object dyn.linked of correct architecture?
– guiverc
Nov 21 at 10:52
To answer your comments: 1. space should not be a problem, 2. calling man with the full path I mean typing/usr/bin/maninstead of justman. But, again, this does not work either. 3. the output offile /usr/bin/manisELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c80771d215f4d9df4bf138ec9cfbf23bc58c950d, stripped
– BCArg
Nov 21 at 11:24
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My man command is not working at all on my Ubuntu 18.04 machine. Unlike most of the cases I have found described in the internet, where there is an error message after calling man, I do not get any output/ error message at all
If I type which man
I will get /usr/bin/man. And I have checked with echo PATH that/usr/bin is on my PATH.
I have already tried sudo apt install --reinstall man-db, restarted the terminal, but no success.
Does anyone know what the problem can be?
18.04 manpage
asked Nov 21 at 9:30
BCArg
212212
My man command is not working at all on my Ubuntu 18.04 machine. Unlike most of the cases I have found described in the internet, where there is an error message after calling man, I do not get any output/ error message at all
If I type which man
I will get /usr/bin/man. And I have checked with echo PATH that/usr/bin is on my PATH.
I have already tried sudo apt install --reinstall man-db, restarted the terminal, but no success.
Does anyone know what the problem can be?
18.04 manpage
18.04 manpage
asked Nov 21 at 9:30
BCArg
212212
asked Nov 21 at 9:30
BCArg
212212
asked Nov 21 at 9:30
BCArg
212212
asked Nov 21 at 9:30
BCArg
212212
asked Nov 21 at 9:30
BCArg
212212
212212
What do you get if you trywhereis man? This should provide any locations forman, plus the locations for the manual pages (for the commandman)
– guiverc
Nov 21 at 9:54
I getman: /usr/bin/man /usr/local/man /usr/share/man /usr/share/man/man1/man.1.gz /usr/share/man/man7/man.7.gzNone of them work by callingmanwith the full path (some are directories). But thewhichcommand will tell me whichmanlinux will call when callingman, right? As I described in my question it is /usr/bin/man, which is in my $PATH
– BCArg
Nov 21 at 10:02
maybe you can runstrace manand then paste the debug info in some nopaste site?(since the info would be long)
– Alvin Liang
Nov 21 at 10:12
I would check you have some free disk space (df -h) in case it needs it to operate. Next I woulddpkg -S /usr/bin/manto ensure your found program comes fromman-db(as expected). I'm not sure what you mean by "calling man with the full path" as to access page 1 youman 1 man, to access page 7man 7 man(which doesn't use the path; unless you meant/usr/bin/man 1 manto view page 1). If you check file type of your binary (ie.file /usr/bin/man) do you get a ELF LSB shared object dyn.linked of correct architecture?
– guiverc
Nov 21 at 10:52
To answer your comments: 1. space should not be a problem, 2. calling man with the full path I mean typing/usr/bin/maninstead of justman. But, again, this does not work either. 3. the output offile /usr/bin/manisELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c80771d215f4d9df4bf138ec9cfbf23bc58c950d, stripped
– BCArg
Nov 21 at 11:24
add a comment |
What do you get if you trywhereis man? This should provide any locations forman, plus the locations for the manual pages (for the commandman)
– guiverc
Nov 21 at 9:54
I getman: /usr/bin/man /usr/local/man /usr/share/man /usr/share/man/man1/man.1.gz /usr/share/man/man7/man.7.gzNone of them work by callingmanwith the full path (some are directories). But thewhichcommand will tell me whichmanlinux will call when callingman, right? As I described in my question it is /usr/bin/man, which is in my $PATH
– BCArg
Nov 21 at 10:02
maybe you can runstrace manand then paste the debug info in some nopaste site?(since the info would be long)
– Alvin Liang
Nov 21 at 10:12
I would check you have some free disk space (df -h) in case it needs it to operate. Next I woulddpkg -S /usr/bin/manto ensure your found program comes fromman-db(as expected). I'm not sure what you mean by "calling man with the full path" as to access page 1 youman 1 man, to access page 7man 7 man(which doesn't use the path; unless you meant/usr/bin/man 1 manto view page 1). If you check file type of your binary (ie.file /usr/bin/man) do you get a ELF LSB shared object dyn.linked of correct architecture?
– guiverc
Nov 21 at 10:52
To answer your comments: 1. space should not be a problem, 2. calling man with the full path I mean typing/usr/bin/maninstead of justman. But, again, this does not work either. 3. the output offile /usr/bin/manisELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c80771d215f4d9df4bf138ec9cfbf23bc58c950d, stripped
– BCArg
Nov 21 at 11:24
What do you get if you try
whereis man ? This should provide any locations for man, plus the locations for the manual pages (for the command man)– guiverc
Nov 21 at 9:54
What do you get if you try
whereis man ? This should provide any locations for man, plus the locations for the manual pages (for the command man)– guiverc
Nov 21 at 9:54
I get
man: /usr/bin/man /usr/local/man /usr/share/man /usr/share/man/man1/man.1.gz /usr/share/man/man7/man.7.gz None of them work by calling man with the full path (some are directories). But the which command will tell me which man linux will call when calling man, right? As I described in my question it is /usr/bin/man, which is in my $PATH– BCArg
Nov 21 at 10:02
I get
man: /usr/bin/man /usr/local/man /usr/share/man /usr/share/man/man1/man.1.gz /usr/share/man/man7/man.7.gz None of them work by calling man with the full path (some are directories). But the which command will tell me which man linux will call when calling man, right? As I described in my question it is /usr/bin/man, which is in my $PATH– BCArg
Nov 21 at 10:02
maybe you can run
strace man and then paste the debug info in some nopaste site?(since the info would be long)– Alvin Liang
Nov 21 at 10:12
maybe you can run
strace man and then paste the debug info in some nopaste site?(since the info would be long)– Alvin Liang
Nov 21 at 10:12
I would check you have some free disk space (
df -h) in case it needs it to operate. Next I would dpkg -S /usr/bin/man to ensure your found program comes from man-db (as expected). I'm not sure what you mean by "calling man with the full path" as to access page 1 you man 1 man, to access page 7 man 7 man (which doesn't use the path; unless you meant /usr/bin/man 1 man to view page 1). If you check file type of your binary (ie. file /usr/bin/man) do you get a ELF LSB shared object dyn.linked of correct architecture?– guiverc
Nov 21 at 10:52
I would check you have some free disk space (
df -h) in case it needs it to operate. Next I would dpkg -S /usr/bin/man to ensure your found program comes from man-db (as expected). I'm not sure what you mean by "calling man with the full path" as to access page 1 you man 1 man, to access page 7 man 7 man (which doesn't use the path; unless you meant /usr/bin/man 1 man to view page 1). If you check file type of your binary (ie. file /usr/bin/man) do you get a ELF LSB shared object dyn.linked of correct architecture?– guiverc
Nov 21 at 10:52
To answer your comments: 1. space should not be a problem, 2. calling man with the full path I mean typing
/usr/bin/man instead of just man. But, again, this does not work either. 3. the output of file /usr/bin/man is ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c80771d215f4d9df4bf138ec9cfbf23bc58c950d, stripped– BCArg
Nov 21 at 11:24
To answer your comments: 1. space should not be a problem, 2. calling man with the full path I mean typing
/usr/bin/man instead of just man. But, again, this does not work either. 3. the output of file /usr/bin/man is ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c80771d215f4d9df4bf138ec9cfbf23bc58c950d, stripped– BCArg
Nov 21 at 11:24
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f1094739%2fman-command-not-working-in-ubuntu-18-04%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
What do you get if you try
whereis man? This should provide any locations forman, plus the locations for the manual pages (for the commandman)– guiverc
Nov 21 at 9:54
I get
man: /usr/bin/man /usr/local/man /usr/share/man /usr/share/man/man1/man.1.gz /usr/share/man/man7/man.7.gzNone of them work by callingmanwith the full path (some are directories). But thewhichcommand will tell me whichmanlinux will call when callingman, right? As I described in my question it is /usr/bin/man, which is in my $PATH– BCArg
Nov 21 at 10:02
maybe you can run
strace manand then paste the debug info in some nopaste site?(since the info would be long)– Alvin Liang
Nov 21 at 10:12
I would check you have some free disk space (
df -h) in case it needs it to operate. Next I woulddpkg -S /usr/bin/manto ensure your found program comes fromman-db(as expected). I'm not sure what you mean by "calling man with the full path" as to access page 1 youman 1 man, to access page 7man 7 man(which doesn't use the path; unless you meant/usr/bin/man 1 manto view page 1). If you check file type of your binary (ie.file /usr/bin/man) do you get a ELF LSB shared object dyn.linked of correct architecture?– guiverc
Nov 21 at 10:52
To answer your comments: 1. space should not be a problem, 2. calling man with the full path I mean typing
/usr/bin/maninstead of justman. But, again, this does not work either. 3. the output offile /usr/bin/manisELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c80771d215f4d9df4bf138ec9cfbf23bc58c950d, stripped– BCArg
Nov 21 at 11:24