Troubleshooting
The AppImage won’t start
Section titled “The AppImage won’t start”If starting it prints dlopen(): error loading libfuse.so.2, your system is missing libfuse2, which
AppImages need (Ubuntu 22.04 and later no longer install it by default). Install it:
sudo apt install libfuse2Or run the AppImage without FUSE:
./Spekterm-<version>.AppImage --appimage-extract-and-runclaude is not found when spekterm is started from the desktop menu
Section titled “claude is not found when spekterm is started from the desktop menu”A program started from the desktop menu does not inherit your terminal’s environment. spekterm reads your
login shell’s environment once when it starts, and uses its PATH to find claude. So:
- make sure the directory that contains
claudeis added toPATHin your shell’s startup files (for zsh,.zshrcor.zprofile); - restart spekterm after changing them — the environment is read once at startup, so opening a new session is not enough.
A change to my shell environment does not show up
Section titled “A change to my shell environment does not show up”Same cause: spekterm reads your environment once, at startup. Quit spekterm and start it again.
The side panel or the file tree stops updating
Section titled “The side panel or the file tree stops updating”Your inotify watch limit is probably too low (the error, ENOSPC, only shows up on spekterm’s standard
error output). Check it:
cat /proc/sys/fs/inotify/max_user_watchesIf it is 8192, raise it:
echo 'fs.inotify.max_user_watches=524288' | sudo tee /etc/sysctl.d/60-inotify.confsudo sysctl --systemWhich build am I running?
Section titled “Which build am I running?”Settings → About shows the version, build time, and commit. Include them when you report a problem on GitHub.