Fastfetch Troubleshooting: Common Errors and Fixes
Common issues usually come from missing dependencies, an outdated installation, or a configuration problem. Terminal errors may also appear, or some system information may be missing. Most problems are easy to resolve once you identify the cause. The following sections provide practical solutions for common Fastfetch errors.
Why Does Fastfetch Say Command Not Found?
The message fastfetch: command not found means the system cannot locate the command. This usually happens because the tool is not installed or its files are not in the system PATH.
Not Installed
Verify that Fastfetch is installed on your system. If it is missing, install it using the correct method for your operating system.
Wrong Command Spelling
Make sure you typed fastfetch correctly. Even a small spelling mistake can cause this error.
Not in PATH
If you installed Fastfetch manually, your system may not know where to find the program. Add its folder to your PATH, or run it using the full path to the executable.
Unable to Install Fastfetch
Installation problems may be related to the operating system, package manager, or available repositories. You may see errors such as package not found or unable to locate package. The sections below cover common installation problems on Ubuntu, Debian, Arch Linux, Fedora, macOS, and Windows.
Ubuntu
Ubuntu cannot find Fastfetch: update your package information and try the installation again. If the package is still unavailable, make sure your Ubuntu version supports Fastfetch or use another supported installation method.
Debian
A Debian issue can occur when the package is not available in the repositories enabled on your system. An Unable to locate package error usually means your Debian version or repository settings need attention. When the package is unavailable, use a compatible package or another supported installation method.
Arch Linux
A Fastfetch installation error on Arch can happen when the package database is out of date or there is a package conflict. Update your system first, then try the installation again.
sudo pacman -Syu
sudo pacman -S fastfetchFedora
An installation error on Fedora may occur when package information is outdated. Update the package information and try again. When the package is still not found, make sure your Fedora version has a compatible package available.
macOS
When Fastfetch is not working on macOS after a Homebrew installation, update Homebrew and try again. If the package is still unavailable, make sure your macOS version and Homebrew setup are supported.
Windows
Windows installation issues may occur when the package manager is outdated or the package does not support your setup. Update the package manager and try again. When the package cannot be found, use another supported installation method.
Why Is the Config File Not Loading?
A configuration loading problem can result from an incorrect file location, name, or syntax. A config not loading issue can occur if the file is missing, misnamed, or contains an error.
Config File Location
Make sure your config is saved in the expected location. An incorrect path can cause a fastfetch config file not found error. If you use a custom config, make sure its path is correct.
~/.config/fastfetch/config.jsoncFile Name
Make sure the file uses the correct name and extension. For example, config.json may not work if Fastfetch expects config.jsonc.
Syntax Errors
Missing commas, quotes, or brackets can cause a fastfetch config syntax error or fastfetch config parsing error. Issues that appear after an edit may be resolved by reviewing or undoing your latest changes. An unsupported option or module can also prevent the config from loading.
How to Fix Icons, Font, and Symbol Problems
Missing icons often come from a terminal font that does not support the required symbols. This can result in boxes, missing icons, or garbled characters.
Install and Select a Nerd Font
Install a Nerd Font such as Hack Nerd Font, JetBrainsMono Nerd Font, or FiraCode Nerd Font, then set it as your terminal default font. After changing the font, restart your terminal and run Fastfetch again.
On Arch Linux:
sudo pacman -S ttf-nerd-fonts-symbolsReview Your Configuration Settings
Review your configuration for incorrect icon or logo settings when icons do not appear. A valid configuration and a supported font are both required for symbols to display correctly.
Why Is Fastfetch Not Displaying Correctly?
A missing logo may result from an unsupported terminal, an incorrect logo type, or the wrong image path.
Terminal Support
Some terminals do not support image protocols such as Sixel, Kitty, or iTerm. If your terminal does not support the selected protocol, the image may not display.
Logo Type
Make sure the selected logo type matches your terminal. For image logos, you may need to specify the correct type, such as sixel, kitty, or iterm.
Image Path
If you use a custom image, make sure the file path is correct and the image exists at that location. An incorrect path can cause the logo to fail or fall back to the default logo.
Why Isn’t Fastfetch Detecting My Hardware Correctly?
Incorrect hardware detection may result from outdated cached data, missing system support, or a virtualized environment.
Outdated or Cached Data
If hardware information looks outdated, try running Fastfetch again after the hardware change, or check whether a required system library needs updating.
Missing Dependencies
Missing system libraries can make CPU, GPU, or other hardware information incomplete. If hardware information is still missing, review your system environment and make sure Fastfetch has access to the required hardware information.
System Environment (Docker, VM, WSL)
Docker, virtual machines, and WSL may expose only virtualized or limited hardware information. Physical hardware may not be detected correctly in these environments.
Why Do Colors Look Incorrect?
Incorrect colors may result from custom ASCII art, terminal settings, or startup timing.
Custom ASCII Art
The $ symbol is used as a color token. Escape a literal $ in custom ASCII art as $$ to prevent incorrect colors.
Terminal Rendering
Some terminals may handle bold or color combinations differently. Try a different color setting if the output still looks incorrect.
How to Fix Output That’s Too Large for the Terminal
The output may be too wide for your terminal or contain too many modules. The options below help reduce or adjust the output size.
Disable Line Wrapping
Use the following command to prevent long output from wrapping awkwardly in the terminal.
fastfetch --disable-linewrapHide the Logo
To prevent the logo from making the output too wide, run:
fastfetch -l noneReduce the Output
Make your terminal window wider or remove unnecessary modules from your configuration. This can fix truncated output, alignment, and wrapping issues.
Why Doesn’t It Run at Terminal Startup?
Terminal startup does not run the command automatically unless fastfetch is added to the shell startup file. Make sure the command is placed in the correct file for your shell.
| Shell | Startup File |
|---|---|
| Bash | ~/.bashrc |
| Zsh | ~/.zshrc |
| Fish | ~/.config/fish/config.fish |
For example, with Bash:
echo "fastfetch" >> ~/.bashrcThen open a new terminal to confirm that it starts automatically.
Still Does Not Start
Make sure you edited the startup file used by your active shell. An incorrect file, a startup script error, or another prompt tool can prevent it from running.
Why Is Fastfetch Slow to Start?
Slow startup may occur when one or more modules take too long to collect system information. Network checks, package queries, or desktop environment detection can sometimes cause delays.
Identify the Slow Module
Run the following command to see how long each module takes. This helps you identify the source of the delay.
fastfetch --statDisable Slow Modules
Once you identify the slow module, remove or disable it from your configuration. Network and package-related modules are common causes. You can also test without your configuration to confirm whether a module or setting is causing the delay.
fastfetch --config noneWhy Isn’t Fastfetch Detecting My Terminal Correctly?
Incorrect terminal detection may involve environment variables, terminal multiplexers, or shell startup settings. The table below lists common problems and their fixes.
| Problem | Fix |
|---|---|
| Terminal detection is incorrect | Review $TERM or $TERM_PROGRAM and make sure your shell configuration is not changing them. |
| tmux or screen is detected | Fastfetch may detect the multiplexer instead of the original terminal. |
| WSL or SSH environment | Terminal detection may be limited because Fastfetch cannot directly access the host terminal. |
| Startup integration conflict | Check whether your shell or terminal settings change the terminal environment. |
How to Reset Fastfetch After an Error
If none of the fixes above resolve the issue, resetting the configuration to default often clears corrupted or conflicting settings.
Linux and macOS
Rename or remove the configuration file, then run fastfetch to regenerate it with default settings. See the full reset guide for step-by-step instructions.
Windows
The configuration file on Windows is usually located at:
%APPDATA%\fastfetch\config.jsoncTo keep a backup before resetting, rename it:
Rename-Item "$env:APPDATA\fastfetch\config.jsonc" "config.jsonc.bak"Regenerate the Configuration
If the config file is corrupted and will not regenerate normally, run the following command. It opens an interactive prompt that lets you confirm overwriting the existing file and choose a fresh default configuration.
fastfetch --gen-configHow to Collect Information Before Reporting a Bug
Before reporting a Fastfetch bug, collect the basic details below to make the issue easier to understand and reproduce. Avoid sharing passwords, tokens, or other private information in logs or configuration files.
| Information | What to Include |
|---|---|
| Fastfetch version | Run fastfetch –version and include the version number. |
| Operating system | Mention your OS and version. |
| Terminal | Include the terminal you are using, such as Kitty, Alacritty, or Windows Terminal. |
| Configuration | Include the relevant part of your Fastfetch config if the issue involves customization. |
| Error message | Copy the exact error shown in the terminal. |
| Reproduction steps | List the commands or steps that cause the problem. |
| Logs and diagnostics | Run fastfetch –show-errors and include the relevant output. |
Frequently Asked Questions
Quick answers to common questions about Fastfetch errors and behavior.
Conclusion
With the right checks, most issues can be resolved without reinstalling the tool. Reviewing your configuration, terminal environment, and system information can help identify the cause and apply the right fix.
Once it works again, keep your configuration simple and update the tool as needed. When a problem continues, document the issue clearly and include your version and system details when reporting it.
Adam Bennett
Adam Bennett writes the Fastfetch guides on this site, researching and testing each one against official Fastfetch documentation and other reliable technical sources to keep instructions accurate and up to date. Guides are reviewed and updated as Fastfetch continues to evolve, covering everything from installation and configuration to troubleshooting and comparisons with other terminal tools.