Troubleshooting
Solutions to common issues you might encounter with jolt.
Installation Issues
Section titled “Installation Issues””command not found: jolt”
Section titled “”command not found: jolt””The jolt binary isn’t in your PATH.
Homebrew install:
# Verify installationbrew list jolt
# If installed, try:eval "$(/opt/homebrew/bin/brew shellenv)"Cargo install:
# Add cargo bin to PATHexport PATH="$HOME/.cargo/bin:$PATH"
# Or reinstallcargo install jolt-tui --forceSource install:
# Copy to PATHsudo cp ./target/release/jolt /usr/local/bin/Build fails from source
Section titled “Build fails from source”Missing Xcode tools:
xcode-select --installRust not installed:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shOutdated Rust:
rustup updateDisplay Issues
Section titled “Display Issues”Corrupted/garbled display
Section titled “Corrupted/garbled display”-
Resize terminal — Often fixes rendering issues
-
Force redraw — Press
Ctrl+L -
Check TERM variable:
Terminal window echo $TERM# Should be xterm-256color or similar -
Set correct TERM:
Terminal window export TERM=xterm-256colorjolt
Colors look wrong
Section titled “Colors look wrong”-
Verify 256 color support:
Terminal window # Should show colored gradientfor i in {0..255}; do printf "\e[48;5;${i}m \e[0m"; done; echo -
Check theme:
Terminal window jolt --theme default -
Try different terminal:
- iTerm2, Alacritty, and Kitty have best color support
- Default Terminal.app may have issues with some themes
UI doesn’t fit terminal
Section titled “UI doesn’t fit terminal”jolt needs a minimum terminal size:
- Width: 80 columns
- Height: 24 rows
Resize your terminal or reduce font size.
Data Issues
Section titled “Data Issues””No power metrics available”
Section titled “”No power metrics available””Power metrics require Apple Silicon:
- M1, M2, M3, M4 series chips
- Intel Macs cannot report power consumption
Verify your chip:
sysctl -n machdep.cpu.brand_stringBattery data is stale/wrong
Section titled “Battery data is stale/wrong”-
Check macOS battery:
Terminal window pmset -g batt -
Compare with ioreg:
Terminal window ioreg -r -c AppleSmartBattery | grep -E "Cycle|Capacity|Health" -
Report bug if mismatched — jolt should match these sources
Process list is empty
Section titled “Process list is empty”-
Check permissions:
- System Settings → Privacy & Security → Full Disk Access
- Add your terminal app
-
Run debug:
Terminal window jolt debug -
Check for errors:
Terminal window jolt 2>&1 | grep -i error
Daemon Issues
Section titled “Daemon Issues”Daemon won’t start
Section titled “Daemon won’t start”-
Check if already running:
Terminal window jolt daemon statuspgrep -f "jolt daemon" -
Check logs:
Terminal window jolt logs -
Try foreground mode:
Terminal window jolt daemon start --foreground -
Check socket:
macOS:
Terminal window ls -la ~/Library/Caches/jolt/daemon.sockLinux:
Terminal window ls -la ~/.local/share/jolt/daemon.sock
TUI can’t connect to daemon
Section titled “TUI can’t connect to daemon”-
Verify daemon is running:
Terminal window jolt daemon status -
Check socket permissions:
macOS:
Terminal window ls -la ~/Library/Caches/jolt/daemon.sockLinux:
Terminal window ls -la ~/.local/share/jolt/daemon.sock -
Restart daemon:
Terminal window jolt daemon stopjolt daemon start
Daemon uses too much CPU
Section titled “Daemon uses too much CPU”Increase sample interval in your config file:
macOS: ~/Library/Application Support/jolt/config.toml
Linux: ~/.config/jolt/config.toml
[daemon]sample_interval = 120 # Every 2 minutesThen restart:
jolt daemon stop && jolt daemon startConfig Issues
Section titled “Config Issues”Config file not found
Section titled “Config file not found”jolt creates it on first run. If missing:
# Check locationjolt config --path
# Create default configjolt config --resetConfig changes not taking effect
Section titled “Config changes not taking effect”-
Verify syntax:
macOS:
Terminal window cat ~/Library/Application\ Support/jolt/config.tomlLinux:
Terminal window cat ~/.config/jolt/config.toml -
Check for typos — TOML is case-sensitive
-
Restart jolt — Some changes require restart
-
Check for overrides:
Terminal window # Environment variables override configecho $JOLT_THEME
Reset to defaults
Section titled “Reset to defaults”jolt config --resetOr manually delete the config file (see jolt config --path for location).
Performance Issues
Section titled “Performance Issues”jolt is slow/laggy
Section titled “jolt is slow/laggy”-
Reduce refresh rate:
Terminal window jolt --refresh-ms 2000 -
Enable low power mode:
Terminal window jolt --low-power -
Close other heavy apps — jolt shows you what’s using resources!
High CPU from jolt itself
Section titled “High CPU from jolt itself”-
Check refresh rate:
refresh_ms = 1000 # Don't go below 500 -
Disable process tracking:
[panels]processes = false -
Report bug — jolt should use minimal CPU
Getting Help
Section titled “Getting Help”Collect debug info
Section titled “Collect debug info”jolt debug > debug.txtCheck version
Section titled “Check version”jolt --versionReport issues
Section titled “Report issues”Include in bug reports:
- jolt version
- macOS version
- Chip type (Intel/M1/M2/etc)
- Terminal app
- Output of
jolt debug - Steps to reproduce
Report at: https://github.com/jordond/jolt/issues