Terminal Says 'No manual entry' for Command
Stuck with 'No manual entry' errors? Here's how to add missing man pages in Linux.
I know this error is infuriating. You type man grep and get back 'No manual entry for grep'. It feels broken, but it's probably just missing packages.
Quick fix: Install the man pages
On most Linux systems, the fix is one command. Open a terminal and run:
sudo apt update && sudo apt install man-db man-pages
On Fedora or CentOS, use:
sudo dnf install man-db man-pages
After installing, try man grep again. If that didn't work, run mandb to rebuild the man page index:
sudo mandb
That usually fixes it. I've seen this on Ubuntu 22.04 and Fedora 38.
Why this happens
Man pages aren't always installed by default. Some Linux distros (like Ubuntu Server or minimal installs) skip them to save space. Also, if you're using WSL on Windows, the default install is minimal — no man pages.
The man-db package holds the man command itself. man-pages contains the actual documentation for system calls, library functions, and standard commands. Without both, you get that blank stare.
After installing, mandb scans your system and creates a database of where all man pages live. Without this database, man can't find anything, even if the files exist.
Less common variations
1. Command not found at all, not just man
If the command itself is missing (like iftop), you need to install its package. The man page comes with it. For example:
sudo apt install iftop
2. Man pages exist but aren't showing
Check if manual files are actually installed. Look for them in /usr/share/man/:
ls /usr/share/man/man1/ | head
If you see files like grep.1.gz, mandb might be out of date. Run sudo mandb again. I had this once after a system upgrade — the database was stale.
3. WSL specifically
If you're on Windows Subsystem for Linux (WSL), the default Ubuntu image is stripped down. Run this to restore missing packages:
sudo unminimize
Yep, that's a real command. It re-adds man pages, docs, and other stuff Microsoft left out. It takes a few minutes.
4. Man pages for a package you just compiled
If you built a program from source, man pages might not be in the standard paths. Copy them manually or change the MANPATH environment variable:
export MANPATH=/usr/local/man:$MANPATH
Add that to your .bashrc to make it permanent.
Prevention: Keep man pages around
To avoid this in the future, install man pages early. When you set up a new system, run the install commands above first thing. On Debian/Ubuntu, the package ubuntu-minimal also includes man, but I prefer to install man-pages explicitly.
If you're running a server, man pages are still useful when troubleshooting. Don't skip them to save 10 MB of disk space.
Also, when you install a new package with apt, man pages come along automatically. So sudo apt install nginx also brings man nginx. But if you install from a .deb file or compile from source, you might need to grab the docs separately.
Finally, sometimes a corrupted database can break man pages. If you run into this again, a quick sudo mandb is your friend. Keep that command in your back pocket.
Was this solution helpful?