man command not working in Ubuntu 18.04ubuntu man command display blank pagesCannot upgrade UbuntuUnbuffer stopped working months agoUbuntu 18.04 update issuegrub-efi-amd64-signed update issueRandom freezes in (X)Ubuntu 18.04 caused by filled up RAM
What causes standard door hinges to close up to a certain amount automatically?
Novel set in the future, children cannot change the class they are born into, one class is made uneducated by associating books with pain
What's the most efficient way to draw this region?
Slow coworker receiving compliments while I receive complaints
How to protect my Wi-Fi password from being displayed by Android phones when sharing it with QR code?
How do I weigh a kitchen island to determine what size castors to get?
Is it reasonable to ask candidates to create a profile on Google Scholar?
Delete line if next line is the same
An idiomatic word for "very little" in this context?
Disrespectful employee going above my head and telling me what to do. I am his manager
SSD or HDD for server
How to make a PCB based on ATtiny easily updatable by end users?
Is it possible to cross Arctic Ocean on ski/kayak undetectable now?
Difference between head and tail
Can a character dodge an attack that beats their Armor Class?
Did smallpox emerge in 1580?
"Dear Stack Exchange, I am very disappointed in you" - How to construct a strong opening line in a letter?
Which collation should I use for biblical Hebrew?
Can the bass be used instead of drums?
I didn't do any exit passport control when leaving Japan. What should I do?
What does "drop" mean in this context?
33 Months on Death Row
How can demon technology be prevented from surpassing humans?
Why are KDFs slow? Is using a KDF more secure than using the original secret?
man command not working in Ubuntu 18.04
ubuntu man command display blank pagesCannot upgrade UbuntuUnbuffer stopped working months agoUbuntu 18.04 update issuegrub-efi-amd64-signed update issueRandom freezes in (X)Ubuntu 18.04 caused by filled up RAM
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
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
|
show 1 more comment
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
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 '18 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 '18 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 '18 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 '18 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 '18 at 11:24
|
show 1 more comment
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
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 '18 at 9:30
BCArgBCArg
2374 silver badges12 bronze badges
2374 silver badges12 bronze badges
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 '18 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 '18 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 '18 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 '18 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 '18 at 11:24
|
show 1 more 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 at 11:24
|
show 1 more comment
1 Answer
1
active
oldest
votes
I had the same problem and I solved it by running the following command:
sudo man <command>
It works, but why does it only work with sudo?
– wordsforthewise
May 8 at 22:10
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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/4.0/"u003ecc by-sa 4.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%2faskubuntu.com%2fquestions%2f1094739%2fman-command-not-working-in-ubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same problem and I solved it by running the following command:
sudo man <command>
It works, but why does it only work with sudo?
– wordsforthewise
May 8 at 22:10
add a comment
|
I had the same problem and I solved it by running the following command:
sudo man <command>
It works, but why does it only work with sudo?
– wordsforthewise
May 8 at 22:10
add a comment
|
I had the same problem and I solved it by running the following command:
sudo man <command>
I had the same problem and I solved it by running the following command:
sudo man <command>
edited Apr 29 at 20:59
Kevin Bowen
16k15 gold badges62 silver badges73 bronze badges
16k15 gold badges62 silver badges73 bronze badges
answered Apr 29 at 18:23
Gonzalo Garcia GentaGonzalo Garcia Genta
111 bronze badge
111 bronze badge
It works, but why does it only work with sudo?
– wordsforthewise
May 8 at 22:10
add a comment
|
It works, but why does it only work with sudo?
– wordsforthewise
May 8 at 22:10
It works, but why does it only work with sudo?
– wordsforthewise
May 8 at 22:10
It works, but why does it only work with sudo?
– wordsforthewise
May 8 at 22:10
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- 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%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 '18 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 '18 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 '18 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 '18 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 '18 at 11:24