You downloaded the PlotJuggler AppImage, double-clicked it — and nothing happened. No window, no message, just nothing. That silent failure is the normal failure shape for AppImages, and it almost always comes down to a short list of checks: the file is not marked executable, your system’s glibc is too old for this build, the AppImage runtime support on your system is incomplete, or the download itself is damaged. This guide works through them in order for PlotJuggler 4, then gives you the escape hatch — the .deb and apt routes — for systems where the AppImage is the wrong tool. It sits on the Troubleshooting hub, alongside the broader install troubleshooting guide.
Check 1 — Make the file executable
A downloaded AppImage is data until you mark it as a program. The PJ4 documentation’s own instruction is exactly this: download PlotJuggler-<version>-x86_64.AppImage, run chmod +x on it, then run it. If you skipped that step, a double-click will do precisely nothing, and that is the system working as designed.
chmod +x PlotJuggler-4.0.0-x86_64.AppImage
./PlotJuggler-4.0.0-x86_64.AppImageRun it from a terminal, at least for diagnosis. A terminal launch shows you any message the program or the runtime prints on failure, while a file-manager double-click hides all of it. Most AppImage mysteries stop being mysteries the moment they are launched once from a terminal. The full AppImage walkthrough, including where to keep the file, is in the Ubuntu install guide.
Check 2 — Your glibc version (PJ4 requires 2.35 or newer)
This is the check specific to PlotJuggler 4, and it is a hard requirement, not a recommendation: the PJ4 AppImage requires glibc ≥ 2.35 — Ubuntu 22.04 or later, or an equivalent distribution. On an older system the file can be perfectly downloaded, correctly marked executable, and still unable to run, because the system library it was built against is not there. Check yours with:
ldd --versionIf the version is below 2.35, re-downloading the same AppImage will never help. Your realistic options are a newer system, the PJ3 AppImage builds (PJ3 also shipped an aarch64 AppImage, which PJ4 does not), or building from source. Do not spend an afternoon fighting a version floor — it does not negotiate.
Check 3 — FUSE and the AppImage runtime (general Linux guidance)
Flagged honestly as general Linux guidance, not a PlotJuggler-specific fault: AppImages traditionally rely on FUSE support to mount themselves when run, and some minimal or newer-default systems lack the compatibility library AppImages expect. The symptom class is “the AppImage will not run at all on this system, for any AppImage”. The test is simple: try a different, known AppImage. If no AppImage runs, the problem is your system’s AppImage support — consult your distribution’s documentation for its FUSE library package — and the direct fix for PlotJuggler specifically is to stop using the AppImage format and install the .deb instead (next section). Launching from a terminal, again, is how you see this class of failure instead of guessing at it.
Check 4 — Architecture and download integrity
- Architecture: PJ4 4.0.0 ships an x86_64 AppImage only. There is no PJ4 aarch64 AppImage; on ARM hardware, that file will never run, however correct everything else is. PJ3 is the line with an aarch64 AppImage.
- Integrity: compare the file’s SHA-256 with the GitHub digest published on the Download page (
sha256sum <file>). A truncated or corrupted download fails in ways that imitate every other check on this page; ruling it out takes a minute. - It is a real tracker topic, too: the project has fielded reports such as “Errors when launching AppImage” (issue #816) and, in the PJ4 era, an AppImage that had silently lost a streaming plugin (issue #1420) — a reminder that if the program opens but a feature is missing, that is a different guide: missing data loaders.
The escape hatch: install the .deb or use the apt repository instead
On Debian and Ubuntu, the AppImage is the portable option, not the only option — and for a machine you use every day, it is arguably not the best one. PJ4 offers a single-release .deb (plotjuggler4_4.0.0-1_amd64.deb) installed with sudo apt install ./plotjuggler4_4.0.0-1_amd64.deb, and, new in this generation, an official apt repository that keeps PlotJuggler 4 updated through your normal system upgrades:
curl -fsSL https://apt.plotjuggler.io/pj4_install.sh | sudo sh
sudo apt install plotjuggler4The repository route is documented for Ubuntu 22.04+ and Debian 12+, and it sidesteps the executable-bit and FUSE questions entirely, because a package manager does that work. Step-by-step instructions are in the apt repository guide and the Ubuntu install guide; all channels start from the Install hub. If PlotJuggler now opens but a file will not, continue on the Troubleshooting hub.
Related guides on this hub: if the AppImage opens but a ROS feature or file format is missing once it runs, that is a plugin question — see ROS 2 plugin not loading; and if the program opens but files will not drop into it under Wayland, see drag and drop not working.