Troubleshooting

Troubleshooting

The command is not found after installation

Noob mode

export PATH="$HOME/.local/bin:$PATH"
rehash 2>/dev/null || hash -r 2>/dev/null || true

For a persistent fix:

binman doctor --fix-path

Pro mode

A child process cannot alter its parent's PATH or command hash table. The install may have succeeded even when the current shell does not see the new command. Check the actual path with:

command -v binman
ls -l ~/.local/bin/binman

Verification failures

binman verify
binman doctor

Verification checks presence, executability, expected app entries, and shims; it does not execute applications or install missing dependencies. Old or externally copied directories inside the app store can be discovered as candidate apps and may fail because they lack BinMan metadata.

Optional tools

Some features use optional commands such as fzf, zip, rsync, curl, Docker, Podman, nmcli, ssh, or sudo. Run the relevant command's --help, then check whether the dependency exists with command -v TOOL.

Pro debugging

BINMAN_DEBUG=1 binman list
BINMAN_DEBUG=1 binman verify

Capture the exact path, mode, and exit status before reporting a bug. A terminal screenshot is useful; the command and its output are even more useful and take up less disk space than a screenshot collection with commitment issues.