Libation/docs/installation/linux.md

# Install on Linux

## Packaging status

[![Packaging status](https://repology.org/badge/vertical-allrepos/libation.svg)](https://repology.org/project/libation/versions)

New Libation releases are automatically packed into `.deb` and `.rpm` package and are available from the [Libation repository's releases page](https://github.com/rmcrackan/Libation/releases).

## Snap

If you install Libation from [Snapcraft](https://snapcraft.io/) (or another Snap channel), data lives under your home directory in versioned folders, for example `~/snap/libation/177/.local/share/Libation/`. Snap keeps a `current` symlink that points at the active revision. Each refresh can add a new numeric folder while copying config into it.

`appsettings.json` in that tree contains a `LibationFiles` string. It must point at the **same** revision directory as the `appsettings.json` file you are editing. If it still says an older path (for example `.../snap/libation/174/...` while you run from `177`), Libation may try to open the database on the old path and fail with a read-only or migration error even when file permissions look correct.

**What to do:** open `appsettings.json` next to the running install (under `~/snap/libation/current/...` or the new revision folder), set `LibationFiles` to the Libation data directory **inside that same revision**, save, and start Libation again. Alternatively set the `LIBATION_FILES_DIR` environment variable to a directory you control (see advanced docs). A user-written walkthrough of this situation is in [GitHub issue #1776](https://github.com/rmcrackan/Libation/issues/1776).

For removable drives and Snap interfaces, your distro's Snap docs apply. Libation also documents common Linux problems in [Troubleshooting](/docs/advanced/troubleshoot).

## Runtime dependencies (Audible sign-in)

The Chardonnay desktop build can log into Audible inside the app when the setting to use Libation's built-in web browser for sign-in is enabled (Import / library settings). On Linux that embedded flow uses WebKit2GTK; the native library is usually exposed as `libwebkit2gtk` (exact package names vary by distro). It is required for in-app OAuth when adding an account or signing in again through that path.

If WebKit2GTK is not installed, use external browser sign-in instead (turn off the built-in browser option in the same settings area), or install your distribution's WebKit2GTK packages, for example:

- Arch Linux: `webkit2gtk` or `webkit2gtk-4.1`
- Debian / Ubuntu: WebKit2GTK 4.x packages such as `libwebkit2gtk-4.1-0` (names can differ by release)
- Fedora / RHEL: the `webkit2gtk4` / WebKit2GTK packages provided for your release

Run these commands in your terminal to download and install Libation. **Make sure you replace** `X.X.X` with the latest Libation version and `ARCH` with your CPU's architechture (either `amd64` or `arm64`).

### Debian

```bash
wget -O libation.deb https://github.com/rmcrackan/Libation/releases/download/vX.X.X/Libation.X.X.X-linux-chardonnay-ARCH.deb
sudo apt install ./libation.deb
```

### Redhat and CentOS

```bash
wget -O libation.rpm https://github.com/rmcrackan/Libation/releases/download/vX.X.X/Libation.X.X.X-linux-chardonnay-ARCH.rpm
sudo yum install ./libation.rpm
```

### Fedora

```bash
wget -O libation.rpm https://github.com/rmcrackan/Libation/releases/download/vX.X.X/Libation.X.X.X-linux-chardonnay-ARCH.rpm
sudo dnf5 install ./libation.rpm
```

---

### AppImage

- Install via [AppMan](https://github.com/ivan-hc/AppMan) (rootless)
  ```bash
  appman -i libation
  ```
- Install via [AM](https://github.com/ivan-hc/AM)
  ```bash
  am -i libation
  ```
Thanks to Package Forge dev [Samuel](https://github.com/Samueru-sama) for [AppImage](https://github.com/pkgforge-dev/Libation-AppImage) maintenence.

When your package manager updates Libation for you, the startup update check has nothing useful to tell you. Turn off "Check for new Libation versions at startup" on the Important settings tab to stop it. Settings > About still has a "Check for Upgrade" button whenever you want to look.

### Arch Linux

```bash
yay -S libation
```

This package is available on [Arch User Repository](https://aur.archlinux.org/packages/libation), install via your choice of [AUR helpers](https://wiki.archlinux.org/title/AUR_helpers).

Thanks to [mhdi](https://aur.archlinux.org/account/mhdi) for taking care of AUR package maintenance.

### NixOS

- Install via `nix-shell`
  ```bash
  nix-shell -p libation
  ```
  A `nix-shell` will temporarily modify your $PATH environment variable. This can be used to try a piece of software before deciding to permanently install it.
- Install via NixOS configuration
  ```nix
  environment.systemPackages = [
    pkgs.libation
  ];
  ```
  Add the following Nix code to your NixOS Configuration, usually located in `/etc/nixos/configuration.nix`
- On NixOS via via `nix-env`
  ```bash
  nix-env -iA nixos.libation
  ```
- On Non NixOS via `nix-env`

  ```Console
  nix-env -iA nixpkgs.libation
  ```

  Warning: Using `nix-env` permanently modifies a local profile of installed packages. This must be updated and maintained by the user in the same way as with a traditional package manager.

  Thanks to [TomaSajt](https://github.com/tomasajt) for taking care of Nix package maintenance.

### Pacstall

Pacstall is the AUR Ubuntu wishes it had. It takes the concept of the AUR and puts a spin on it, making it easier to install programs without scouring github repos and the likes. See the [Pacstall](https://pacstall.dev/) project for more information.

```bash
pacstall -I libation-deb
```
Thanks to [Tobias Heinlein](https://github.com/niontrix) for Pacstall package maintenance.

---

If your desktop uses gtk, you should now see Libation among your applications.

Additionally, you may launch Libation, LibationCli, and Hangover (the Libation recovery app) via the command line using 'libation, libationcli', and 'hangover' aliases respectively.

Report bugs to https://github.com/rmcrackan/Libation/issues