Which package should I download for my distro?

Use .deb for Debian, Ubuntu, Linux Mint and Pop!_OS. Use .rpm for Fedora and openSUSE. Use the .pkg.tar.zst Arch package for Arch, CachyOS, Manjaro and EndeavourOS. Use the AppImage only if none of those match your distribution, since a native package integrates better.

Does installing CLU VIEW on Linux need root?

Installing a system package needs sudo, as any package install does. Running the application does not. The Linux sensor backend is completely unprivileged, so there is no kernel driver and no password prompt when you launch it. The AppImage needs no sudo at all.

Why is there a separate Arch package?

Arch and its derivatives are rolling releases, so libraries such as webkit2gtk and gtk move their ABI over time and a binary compiled on another distribution can break against them. The Arch package is compiled on Arch itself, against Arch's own libraries at release time, so it stays compatible.

How do I uninstall it?

For a .deb use sudo apt remove clu-view, for an .rpm use sudo dnf remove clu-view (sudo zypper remove clu-view on openSUSE), and for the Arch package use sudo pacman -R clu-view. For the AppImage, delete the file and the two FPS-layer files it registered for your user: ~/.local/share/vulkan/implicit_layer.d/cluview_fps.json and ~/.local/share/clu-view/libcluview_fps.so.

Does it work on Wayland?

Yes. Wayland and X11 sessions are both supported. FPS monitoring uses a custom Vulkan layer, so games running under Proton report frame rate without elevation.

How to Install a Sensor Panel on Linux

CLU VIEW ships four Linux packages. Pick the one for your distro and run a single command. Installing needs sudo, like any package install does; the app itself never asks for root. If you want the background first, start with sensor panel for Linux.

> Pick your package_

■.deb for Debian, Ubuntu, Linux Mint, Pop!_OS
■.rpm for Fedora, openSUSE
■.pkg.tar.zst for Arch, CachyOS, Manjaro, EndeavourOS
■.AppImage for anything else. Portable, but use one of the native packages above if it fits your distro.

All four are on the CLU VIEW page, or in the panel to the right. The commands below assume you're in the directory you downloaded to (usually cd ~/Downloads first).

> Debian, Ubuntu, Mint, Pop!_OS_

Install the .deb with apt rather than dpkg, so any dependencies are resolved in the same step:

sudo apt install ./clu-view_*_amd64.deb

The leading ./ matters: without it, apt looks for a repository package of that name instead of your file.

> Fedora, openSUSE_

On Fedora:

sudo dnf install ./clu-view-*.x86_64.rpm

On openSUSE:

sudo zypper install --allow-unsigned-rpm ./clu-view-*.x86_64.rpm

The package isn't GPG-signed, and zypper stops on that without --allow-unsigned-rpm.

> Arch, CachyOS, Manjaro, EndeavourOS_

sudo pacman -U clu-view-*-x86_64.pkg.tar.zst

This one is compiled on Arch itself, against Arch's own libraries at release time, not repackaged from another distro's build. A rolling release moves its webkit2gtk and gtk ABI over time, and a binary compiled somewhere else eventually breaks against it.

> Any other distro: the AppImage_

There's no install step and no sudo here. Mark it executable and run it:

chmod +x clu-view_*.AppImage
./clu-view_*.AppImage

An AppImage doesn't add itself to your application menu and won't update with the rest of your system. That's the reason to take a native package where there is one.

> First run_

01 Launch it from your application menu, or run clu-view in a terminal. It shouldn't ask for a password; the sensor backend is unprivileged by design.

02 Drop widgets on the canvas and assign sensors, or import a layout from the template packs to start from something finished.

03 Switch to Panel Mode to run the dashboard fullscreen on a second screen. Wayland and X11 sessions are both supported.

If you play games through Proton, FPS is read via a custom Vulkan layer, so it reports without any elevation.

> Uninstalling_

sudo apt remove clu-view      # Debian / Ubuntu
sudo dnf remove clu-view      # Fedora
sudo zypper remove clu-view   # openSUSE
sudo pacman -R clu-view       # Arch

If the package name doesn't match, dpkg -l | grep clu (or pacman -Q | grep clu) will show what it registered as. For the AppImage, delete the file, then the FPS layer it registered for your user: rm ~/.local/share/vulkan/implicit_layer.d/cluview_fps.json ~/.local/share/clu-view/libcluview_fps.so

> If something goes wrong_

A missing sensor usually means your board doesn't expose it, not that the install went wrong. If the app won't start, or a reading looks off, the Discord is the fastest way to get an answer. Mention your distro and whether you're on Wayland or X11.

For the other part of the setup, read Linux sensor and display support and the Linux installation steps. Once the app runs, the editor guide covers importing a layout and connecting widgets.

How to install a sensor panel on Linux