Install a package
Wusel is published as a signed repository through the openSUSE Build Service, so your package manager installs it and keeps it up to date like anything else on the machine. Pick your family below; each takes a few commands.
If your distribution is not one of the four, skip to A single file, for everything else or build from source: Install from source. Packages is the full table of what is published where.
Installing does not switch Wusel on. Do Mount at login afterwards — or follow a tutorial, which walks the whole way: on GNOME, on another desktop or on a server.
Fedora
sudo dnf config-manager addrepo --from-repofile=https://download.opensuse.org/repositories/home:/cdhermann:/wusel/Fedora_44/home:cdhermann:wusel.repo
sudo dnf install wusel
The repository is built for Fedora 44. dnf imports the signing key on first
install and asks you to confirm its fingerprint.
sudo dnf install wusel is enough on GNOME: where GNOME Files is installed,
dnf adds wusel-nautilus (emblems and the context menu) on its own. Naming
both — sudo dnf install wusel wusel-nautilus — does the same and is harmless.
openSUSE Tumbleweed
sudo zypper addrepo https://download.opensuse.org/repositories/home:/cdhermann:/wusel/openSUSE_Tumbleweed/home:cdhermann:wusel.repo
sudo zypper refresh
sudo zypper install wusel
As on Fedora, zypper adds wusel-nautilus on its own where GNOME Files is
installed; naming it as well is harmless.
Debian 13
echo 'deb http://download.opensuse.org/repositories/home:/cdhermann:/wusel/Debian_13/ /' \
| sudo tee /etc/apt/sources.list.d/home:cdhermann:wusel.list
curl -fsSL https://download.opensuse.org/repositories/home:cdhermann:wusel/Debian_13/Release.key \
| gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_cdhermann_wusel.gpg > /dev/null
sudo apt update
sudo apt install wusel wusel-nautilus
apt does not add wusel-nautilus on its own, so name it on a GNOME desktop:
it brings the emblems and the context menu to GNOME Files. Without GNOME Files,
sudo apt install wusel alone.
Ubuntu 26.04
The same, against the Ubuntu repository:
echo 'deb http://download.opensuse.org/repositories/home:/cdhermann:/wusel/xUbuntu_26.04/ /' \
| sudo tee /etc/apt/sources.list.d/home:cdhermann:wusel.list
curl -fsSL https://download.opensuse.org/repositories/home:cdhermann:wusel/xUbuntu_26.04/Release.key \
| gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_cdhermann_wusel.gpg > /dev/null
sudo apt update
sudo apt install wusel wusel-nautilus
Arch Linux
Not on the AUR yet, but the PKGBUILD is in the repository and builds the way
any AUR package does. The checkout only supplies the PKGBUILD: it downloads
the source tarball of the release tag its pkgver names and builds that, not
the files in your checkout.
git clone https://github.com/itbh-at/wusel.git
cd wusel/packaging/aur
makepkg -si
-s installs the build dependencies through pacman first; -i installs the
result — both packages, wusel and wusel-nautilus. Without GNOME Files, run
makepkg -s instead and install only the first:
sudo pacman -U wusel-[0-9]*.pkg.tar.zst. Updating means pulling a PKGBUILD with a newer pkgver and running it
again.
A single file, for everything else
Every release also attaches both packages, as RPM and as .deb, per architecture to its
GitHub Release. These are
unsigned, and nothing updates them for you — fetch the next release the same
way. Use them when you cannot add a repository, or when your distribution is
none of the four above and is close enough to Fedora 44 or Debian 13 to run
one.
sudo dnf install ./wusel-*.rpm # RPM-based
sudo apt install ./wusel_*.deb ./wusel-nautilus_*.deb # Debian-based
Without GNOME Files, take only the wusel file.
Use apt, not dpkg -i. apt resolves the dependencies; dpkg only reports
that they are missing.
Staying up to date
This is the point of the repository, and it needs no further setup: Wusel is now an ordinary package on the machine, so whatever you already run to update the system picks up each new release.
| Distribution | Updates arrive with |
|---|---|
Fedora |
|
openSUSE Tumbleweed |
|
Debian, Ubuntu |
|
Arch |
Nothing automatic. |
A single file from a GitHub Release |
Nothing. Download the next one and install it over the top. |
A new version does not restart your mount. After an update, either log out and back in, or:
systemctl --user restart wusel@default
The Nautilus extension and the search provider are loaded at session start, so a full re-login is what picks those up — see below.
Then log out and back in
The Nautilus extension and the GNOME Shell search provider are loaded by their host processes when a session starts, so they are not picked up by the running one. Log out and back in once.
Faster, if you would rather not: restart Nautilus with nautilus -q (it
relaunches on next use), and restart GNOME Shell — on X11 press kbd:[Alt+F2],
type r, press kbd:[Enter]; on Wayland only a re-login does it. A full re-login
always works.
What is installed, and what is not
The mount needs no desktop. wusel brings fuse3 and nothing else — about
four packages — and its notifications, sidebar entry and Shell search need no
further library. The GNOME Files integration is wusel-nautilus, and it brings
only what Nautilus itself uses. On a server or a KDE machine, install wusel
alone; what is then missing is the emblems and the context menu — not the
filesystem. See Packages and
Platform support.