Running MnemoVi on Linux
MnemoVi is a desktop app — your videos, transcripts and search index stay on your machine. This page covers what Linux needs to have installed, why, and what to do when something does not work.
For 64-bit x86 (x86_64) systems.
Where it runs
The download carries everything it needs, so only one thing decides whether it starts: the version of your system’s C library. The list below is really a list of the distributions new enough to clear that floor.
| Distribution | Supported from | .deb |
|---|---|---|
| Ubuntu | 24.04 LTS or newer | 24.04 LTS or newer |
| Debian | 13 (trixie) or newer | 13 (trixie) or newer |
| Fedora | 40 or newer | Use the AppImage |
| Arch / Manjaro | Current | Use the AppImage |
| Anything else | glibc 2.39 or newer | glibc 2.39 or newer, plus WebKitGTK 4.1 |
If your distribution is older than the floor, MnemoVi will not start — that is a hard limit, not a setting. Everything newer works, including releases that came out after this page was written.
Worth checking before you buy: Ubuntu 22.04 LTS, Debian 12 and RHEL 9 are below the floor. They are common and they are still supported by their vendors, but their C library is older than MnemoVi needs, and there is no workaround short of moving to a newer release.
One file — and the one thing it does not carry
The download brings the web engine, the media framework, the video tools and the machine-learning runtime with it. The only pieces it does not bring are NVIDIA’s: those come from NVIDIA, and you install them yourself.
AppImage — everything included
One file that carries what the app needs to run. Nothing to install first, no third-party repositories, no packages pulled in behind your back.
- Runs on every supported distribution, including Fedora and Arch
- Plays video out of the box — no codec packages, no extra repository to add
- Larger download, because the pieces travel with it
- No desktop integration by default — it is a file you run
No updater
MnemoVi does not update itself on Linux. When a new version lands you download the new file and run that one — there is no background update service and nothing to approve.
- Every release is a full download, not a patch
- Nothing is installed system-wide, so there is nothing to uninstall
- You decide when you move version, and you can stay where you are
.deb — shares your system libraries
A system package is supposed to share system libraries and let your package manager keep them patched, so the .deb does exactly that: it declares what it needs, and apt installs it.
- Debian and Ubuntu only
- Smaller download — the shared pieces come from your distribution
- Security updates for the web engine and codecs arrive through apt
- Normal desktop integration: menu entry, icon, uninstall through apt
The AppImage is 430.6 MiB. That is the cost of everything being included — and since there is no updater, it is what each new release downloads.
Getting it running
One file, three steps, nothing from your distribution.
AppImage
Download it, make it executable, run it.
chmod +x MnemoVi_<version>_amd64.AppImage./MnemoVi_<version>_amd64.AppImageAppImages need FUSE. If the file will not start at all, either install your distribution’s FUSE 2 package, or run it without FUSE:
./MnemoVi_<version>_amd64.AppImage --appimage-extract-and-runInstalled, started, imported, transcribed, indexed and played end to end in clean containers on Ubuntu 24.04, Debian 13 and current Fedora.
Debian / Ubuntu — .deb
Debian familyInstall it with apt rather than dpkg, so the packages the .deb declares get resolved for you.
sudo apt install ./MnemoVi_<version>_amd64.debKeep the ./ in front of the filename — without it apt looks for a package by that name in the archive instead of the file on disk. Run the command from wherever the file landed, usually ~/Downloads. Once installed, the package is called mnemo-vi — that is the name to use with apt remove.
Installing the requirements by hand
You only need this section if you are installing the .deb — the AppImage already carries all of it. It covers installing the .deb’s requirements ahead of time, and running MnemoVi from system libraries on Fedora or Arch.
Debian / Ubuntu
The web engine, the desktop toolkit and the media plugins:
sudo apt install \ libwebkit2gtk-4.1-0 \ libgtk-3-0 \ librsvg2-2 \ libayatana-appindicator3-1 \ gstreamer1.0-plugins-base \ gstreamer1.0-plugins-good \ gstreamer1.0-plugins-bad \ gstreamer1.0-libavFedora
The same set, under Fedora’s package names:
sudo dnf install \ webkit2gtk4.1 \ gtk3 \ librsvg2 \ libappindicator-gtk3 \ gstreamer1-plugins-good \ gstreamer1-plugins-bad-freeArch / Manjaro
Everything is in the standard repositories:
sudo pacman -S --needed \ webkit2gtk-4.1 gtk3 librsvg libappindicator-gtk3 \ gst-plugins-base gst-plugins-good gst-plugins-bad gst-libavFedora does not ship H.264 video support by default
This is a patent-licensing decision by Fedora, not something MnemoVi can work around. Running from system libraries without it, the app installs and starts, but video previews stay black. Pick one of the two fixes:
sudo dnf config-manager setopt fedora-cisco-openh264.enabled=1sudo dnf install openh264 gstreamer1-plugin-openh264sudo dnf install \ https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpmsudo dnf install gstreamer1-libav gstreamer1-plugins-bad-freeworldOr use the AppImage and skip all of this — it carries its own codecs, so video plays on Fedora with nothing added.
The graphics card, and the software it needs
Searching your videos by meaning runs on the graphics card. On Linux that means an NVIDIA card today — support for other makes is in progress. MnemoVi ships none of NVIDIA’s software: it looks for it on your machine, and if it is not there it names what is missing and sends you to NVIDIA.
| Component | Version |
|---|---|
| NVIDIA CUDA Toolkit | 12.8 or newer 12.x — not 13 |
| NVIDIA cuDNN | 9.x, the build for CUDA 12 |
| NVIDIA driver | Any driver supporting CUDA 12 |
It has to be the 12 series. CUDA 13 will not do instead: the libraries carry the major version in their filename, and MnemoVi looks for the 12 ones by name — a 13 install leaves it reporting the same thing as no install at all. The two can sit side by side, so installing 12 does not disturb a 13 you already have. Within the 12 series pick 12.8 or newer: cards from the RTX 50 series onwards are not known to earlier releases. The driver is almost never the problem — drivers are backward compatible, so a current one already runs CUDA 12, and you should never downgrade a working driver.
Get them from NVIDIA. We do not mirror their software and we do not write install steps for it — their download pages are the only place either should come from:
Start here, before downloading anything. The version nvidia-smi prints is the newest CUDA your driver could support — not what is installed. Reading it as "CUDA is present" is the single most common reason people are sure they have it while MnemoVi says they do not. These two commands answer the real question:
nvcc --versionldconfig -p | grep -E 'libcudart\.so\.12|libcudnn\.so\.9'Read this before following NVIDIA’s download page. That page serves the newest release, and its copy-paste block currently finishes with cuda-toolkit-13-3 — CUDA 13, the one series that cannot work here. The 12 series sits in the same repository; it only has to be asked for by name. This installs the keyring once, then names both packages explicitly:
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2404/x86_64/cuda-keyring_1.1-1_all.debsudo dpkg -i cuda-keyring_1.1-1_all.debsudo apt-get updatesudo apt-get -y install cuda-toolkit-12-9 cudnn9-cuda-12You may not need the multi-gigabyte toolkit at all. NVIDIA publishes the same libraries as Python packages, and MnemoVi already looks inside them — no root, no repository, no system changes, and they are found automatically after a restart:
pip install --user nvidia-cuda-runtime-cu12 nvidia-cublas-cu12 \ nvidia-cudnn-cu12 nvidia-cufft-cu12 nvidia-curand-cu12 \ nvidia-cuda-nvrtc-cu12MnemoVi searches the usual places on its own — /usr/local/cuda, /opt/cuda, your distribution’s library directories, and Python package directories. If yours live somewhere it would not think to look, name the directory and it will look there first. It also respects CUDA_PATH, CUDA_HOME, CUDNN_PATH and LD_LIBRARY_PATH if you already set those:
export MN_CUDA_LIB_DIR=/path/to/your/cuda/lib64You do not have to guess, and you do not have to reinstall the app to find out. When MnemoVi reports the components as missing it offers a "Check again" button that re-examines the machine on the spot. Once it reports them found, restart the app — the engines are chosen at startup.
You install it, we do not ship it
MnemoVi carries no part of NVIDIA’s runtime. It checks your machine, and when something is missing it tells you which component and which version, with a link to the download page. Install it, restart MnemoVi, and it picks it up.
Without a supported card
Your videos are still imported, transcribed and captioned, the library is still indexed, and keyword search still finds moments. Searching by meaning is the part that needs the card — that is the part you do not get.
Other graphics makes
NVIDIA is where Linux support starts, not where it stops. Work on other makes is in progress, and this page will say so the day it lands.
One download, then it is yours
On first use MnemoVi fetches the machine-learning models it needs. This happens once and needs an internet connection — and it is the only time the app requires one. Everything after that runs locally on your machine.
When something does not work
Sorted by what you actually see, because that is how you arrive here.
| What you see | What it means | What to do |
|---|---|---|
| The AppImage will not run at all | FUSE is missing | Install your distribution’s FUSE 2 package, or run the file with --appimage-extract-and-run. |
| Terminal shows a GLIBC_2.xx not found error | Your distribution is older than the supported floor | MnemoVi needs glibc 2.39 or newer. There is no workaround on an older release — upgrading the distribution is the only path. |
| Search by meaning returns nothing, but keyword search still finds moments | The graphics card cannot be used — either there is no supported card, or CUDA and cuDNN are not installed | Open Settings → Diagnostics. If it names missing components, install them from NVIDIA and restart MnemoVi; if it reports no supported card, see the Graphics section above. |
| MnemoVi says a component is missing, but you installed it | The installed version is not the one the app needs | The message names what it found and what it needs — CUDA Toolkit 12.x and cuDNN 9.x. Install the needed version, then restart MnemoVi. |
| App hangs on the first search and never returns | The search runtime could not be located | This is a packaging fault, not your system. Send us Settings → Diagnostics and we will fix the build. |
| App starts, video preview is a black rectangle | A media codec did not load — most often H.264 | The AppImage carries its own codecs, so this should not happen. Send us Settings → Diagnostics. |
| App does not start; terminal shows "error while loading shared libraries" | A required system library is missing — only possible on the .deb | Install the packages for your distribution from the section above. The message names the library it could not find. |
| On the .deb, video preview is a black rectangle | Media codecs are missing — most often H.264 | Install gstreamer1.0-libav on Debian/Ubuntu, or see the Fedora section above. |
| Video plays but there is no sound | Audio codec plugins are missing | Install the plugins-good and plugins-bad packages for your distribution. |
Getting help
Getting help
Settings → Diagnostics shows exactly what MnemoVi found on your system: media runtime, graphics components, codec support, video tools and system versions. Copy that panel into any bug report — it answers most of what we would otherwise have to ask you.
Licensing
MnemoVi bundles FFmpeg (LGPL v3) and its machine-learning runtime components (MIT). The AppImage additionally carries the web engine and media framework it needs in order to run without system packages. NVIDIA’s CUDA Toolkit and cuDNN are not part of the download and are not distributed by us — you get them from NVIDIA, under NVIDIA’s terms. The full list, with license texts, is in Settings → Legal. On the .deb path the shared system libraries come from your distribution and are not distributed by us either.
Ready when your machine is.
One file, everything included, and your videos never leave the room.