Installation

Installation

Mumcord is in early development. macOS builds are signed and notarized since 0.4.1; Windows builds are still unsigned. See Privacy and code signing.

Download a release

Releases are built from version tags (see Releasing in Development). Each release is first created as a draft and becomes public when the maintainer publishes it. Open the Releases page: https://github.com/Mumcord/mumcord/releases. v0.4.2 is the current release (a fix release on top of 0.4.0, which brought multi-server, themes, watch party and screen sharing; see Epic 2). Mumcord is licensed under AGPL-3.0; versions up to 0.1.1 were MIT.

System	File
Linux	*.deb, *.rpm, *.AppImage (x86_64 and ARM64), AUR mumcord-bin
Windows	*.exe (installer)
macOS	*.dmg, universal (Apple Silicon and Intel)

Each release also has a SHA256SUMS file. To verify a download, run sha256sum -c SHA256SUMS --ignore-missing (Linux), or compare the hash of the file with the matching line. Every build is installed on a fresh machine and smoke-tested against a local Mumble server before the draft is created.

Test builds from branches

The "Test builds" workflow no longer runs on branch pushes. If there is no published release yet, ask the maintainer for a build.

Unsigned app warnings

These apply to builds that are not signed. Today that is Windows; macOS builds from 0.4.1 on are signed and notarized.

• Windows: SmartScreen warns about an unknown publisher. Choose "More info", then "Run anyway".
• macOS: only for builds older than 0.4.1. Gatekeeper blocks the app on first launch; open it via right-click, "Open" in Finder, or allow it under System Settings, Privacy & Security. From 0.4.1 on there is no warning.
• Linux: no warning. Make the AppImage executable first.

A signed Windows installer and auto-update are planned (Epic 5).

Linux

One-line installer

curl -fsSL https://github.com/Mumcord/mumcord/releases/latest/download/install.sh | sh

It installs the package for your distribution (.deb, .rpm, or the AUR package mumcord-bin on Arch when paru or yay is installed and the AUR has it). Anywhere else, or if the AUR package is not available, it falls back to the AppImage. Whenever the AppImage is installed, it checks for H.264 video support (see below). In preparation for 0.4.3: the installer has a new look (banner, numbered steps with a download spinner, a summary at the end, plain text in logs and pipes); it no longer asks about gst-libav when it is already installed, and when it is missing it asks whether to install it right away. To remove Mumcord, add -s -- --uninstall after sh.

AppImage

chmod +x Mumcord_*.AppImage
./Mumcord_*.AppImage

If FUSE is not available, run it with APPIMAGE_EXTRACT_AND_RUN=1 ./Mumcord_*.AppImage.

Requirements:

• A WebKitGTK 4.1 runtime (libwebkit2gtk-4.1) and the AppIndicator library (libayatana-appindicator3) for the tray icon.
• A Secret Service provider for the identity and server passwords, such as GNOME Keyring or KWallet (with its Secret Service interface enabled). It must be unlocked.
• ALSA/PulseAudio/PipeWire audio.
• For global push-to-talk on Wayland, see Troubleshooting.

GStreamer and H.264 (watch party)

Watch party video uses the GStreamer plugins on your system. The .deb, .rpm and AUR packages depend on them. The AppImage bundles the plugins it needs (about 190 MB) and plays YouTube via VP9, but does not bundle H.264 (gst-libav). Since 0.4.2 it also ships the Opus audio parser YouTube needs. Videos that YouTube only serves as H.264 may not play until you install gst-libav; the AppImage also loads system plugins, and the player shows a hint when a codec is missing:

• Debian, Ubuntu: sudo apt install gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-libav
• Fedora: sudo dnf install gstreamer1-plugins-good gstreamer1-plugins-bad-free gstreamer1-libav (gstreamer1-libav may need RPM Fusion)
• Arch, CachyOS, Manjaro: sudo pacman -S gst-plugins-good gst-plugins-bad gst-libav
• openSUSE: sudo zypper install gstreamer-plugins-good gstreamer-plugins-bad gstreamer-plugins-libav

Logs are in ~/.local/share/app.mumcord.client/logs/ (see Troubleshooting).

Windows

Run the *-setup.exe. It needs the WebView2 runtime (preinstalled on Windows 11).

macOS

Open the universal .dmg (one file for Apple Silicon and Intel) and drag Mumcord into Applications. Push-to-talk with a mouse button asks for the Accessibility permission.

• Local Network: macOS asks whether Mumcord may find devices on your local network. Allow it, otherwise local servers and direct connections (screen sharing, full-size images) cannot work. You can change it later under System Settings, Privacy & Security, Local Network.
• Keychain and microphone: the keychain asks once per session for each saved secret (identity, server passwords); choose "Always Allow" to stop the prompts. The microphone permission is asked once, when the microphone is first used, not when you only list devices in the setup wizard or settings.
• Screen sharing needs the "Screen & System Audio Recording" permission; the microphone asks for its own permission.
• Logs: ~/Library/Logs/app.mumcord.client/. If a connection fails, the app and the log give the reason (for example "No route to host" points to the Local Network setting).
• Signing: macOS builds from 0.4.1 on are signed and notarized, so Gatekeeper no longer warns (see Privacy and code signing).

Which server can I use?

Any standard Mumble server, 1.4 or newer for all features. Do not test against servers you do not own; use a local one (see Development).