Troubleshooting

Troubleshooting

Push-to-talk on Linux Wayland

Wayland does not let apps read keys globally. Mumcord uses the desktop's global-shortcuts portal for keyboard push-to-talk.

• KDE shows a dialog: this is the portal asking you to confirm the shortcut. Accept it. Mumcord registers itself with the portal before binding shortcuts. Make sure you installed the app in a way that provides its desktop entry (the AppImage and packages do).

• "Push to talk isn't available": your desktop offers no global-shortcuts portal. Voice activation works without a key. Alternatively, use Compatibility mode (below).

• Mouse buttons do not work: the portal cannot capture mouse buttons. Turn on Settings, Voice, "Allow mouse buttons (requires input group)", then add yourself to the input group and log out and in again:

  sudo usermod -aG input $USER
  

  Mumcord shows this exact command when permission is missing. Be aware that input group membership lets any program you run read all input devices, including the keyboard. That is why the option is off by default. Mumcord opens only mouse devices and reacts only to the one configured button; it never logs input.

• Compatibility mode (like TeamSpeak): the switch under Settings, Voice runs Mumcord through the desktop's X11 compatibility layer (XWayland). Push-to-talk then works without a portal dialog and without the input group. It takes effect after a restart (Mumcord offers "Restart now" and disconnects briefly). It is less isolated than the modern way.

  • On KDE, your desktop decides what Mumcord may see under System Settings, Legacy X11 App Support. By default only key combinations and modifier keys work; mouse buttons only if you allow them there.

On X11, Windows and macOS push-to-talk works natively. On macOS, allow Mumcord under System Settings, Privacy & Security, Accessibility when asked.

Overlay on KDE Wayland

Clicks already pass through the window overlay, but KDE on Wayland does not let an app keep its own window on top or place it, so the overlay may sit behind games or windows.

• Open Settings, Overlay and use the helper button to create the KWin window rule in one click.
• Prefer to set it up yourself? Use "Open KDE window rules" and add a rule for the Mumcord overlay window.
• Alternative: switch on Compatibility mode (Settings, Voice; see above). Mumcord then runs through XWayland, where the overlay behaves normally. It takes effect after a restart.
• Games in exclusive fullscreen hide any window overlay. Use borderless windowed mode, or the in-game overlay once it is released.
• There is no overlay on macOS.

Dropping images

Drop images onto the message box (the text input at the bottom of the chat), not onto the message list. A dropped image then appears in a preview tray above the input; you can drop or paste several, then send. If a drop does nothing, paste the image with Ctrl+V instead.

Ctrl+R does not reload the app

Mumcord is a desktop app, not a web page: Ctrl+R (and F5) do not reload it. To recover from a problem, quit Mumcord and start it again.

Linux: app icon and desktop entry

Mumcord's app id is app.mumcord.client. On Wayland, desktops match the window to a desktop entry of that name to show the icon and for the shortcut portal. The AppImage installs a matching desktop entry and icon on first start (~/.local/share/applications/app.mumcord.client.desktop). If you see a generic icon or the KDE shortcut dialog does not show Mumcord, start the AppImage once, then log out and in again so the desktop re-reads its entries.

Linux AppImage: tray icon missing or crash at start

The tray needs the libayatana-appindicator3 library. Current AppImages bundle it, so Mumcord starts even if your system lacks it. Older AppImages crashed without it: update, or install libayatana-appindicator3-1 (Debian/Ubuntu; libayatana-appindicator on Arch). On GNOME the tray icon also needs the AppIndicator extension, otherwise it stays invisible.

What the status icons mean

Hover an icon for its tooltip.

• Guest / registered: whether the person is registered on this server.
• Self mute / self deafen: they muted or deafened themselves.
• Server mute: an admin muted them.
• Suppressed: they may not speak in this channel.
• Muted for you: you muted them locally (their name is red). Others still hear them.

Keyring or "secure storage" errors

Mumcord keeps your identity certificate and server passwords in the OS secure storage and refuses to fall back to plain files.

• Message "Mumcord can't reach your system's secure storage": unlock your keyring or password manager and try again.
• Linux: you need a Secret Service provider running and unlocked, such as GNOME Keyring or KWallet (with its Secret Service interface enabled). A keyring with an empty password may not create the default collection; create or unlock a normal login keyring.
• Minimal desktops and containers often have no D-Bus session or keyring. Start one (for example gnome-keyring-daemon --unlock --components=secrets inside dbus-run-session) before starting Mumcord.

Certificate change warning

Mumcord remembers the certificate of each server you trusted. If it changes, the connection is blocked with a clear warning until you decide.

• A legitimate reason: the server was reinstalled or its certificate renewed. Check with the server's administrator, compare the fingerprint, then accept the new one.
• Otherwise do not continue; someone may be intercepting the connection.

Unregistered users and avatars

Unregistered people (guests) get a guest icon. Mumble servers keep an avatar only for registered users. If you are not registered, the server forgets your avatar when you disconnect. Mumcord remembers your avatar per saved server and sends it again on every connect, so it should reappear. A hint in the avatar settings explains this when you are not registered. To keep it on the server, register from the user menu, "Register on this server" (back up your identity first). Servers also limit image size; Mumcord scales avatars to fit.

Cannot join voice after connecting

This is by design (the setting "Connect muted until I join a channel" is on by default; switch it off to connect unmuted). A fresh connect is read-only: you land in the default channel, muted and deafened. Join a channel (double-click or "Join") and unmute. After joining, your last mute and deafen setting is restored. After an app restart, a prompt above the chat offers to rejoin your last voice channel.

Following a channel does not work

Following needs a server 1.4 or newer, and the server must allow listening. Older servers hide the feature. The test server limit mimics a server that refuses it.

Logs

Mumcord writes rotating log files (7 kept) with a configurable level. Logs contain no chat contents, passwords, certificates or audio. The folder is the Tauri app log directory for the identifier app.mumcord.client:

OS	Location
Linux	~/.local/share/app.mumcord.client/logs/
Windows	%LOCALAPPDATA%\app.mumcord.client\logs\
macOS	~/Library/Logs/app.mumcord.client/

The Windows and macOS paths are the Tauri defaults for app_log_dir; they were not checked on those systems. The app data folder (with mumcord.sqlite3) sits next to the logs on Linux and Windows.

For bug reports, use Settings, Diagnostics, Save diagnostic file. It contains app version, OS, audio devices, connection statistics and recent log lines, with no chat, passwords or certificates.

Windows and macOS security warnings

Builds are unsigned. See Installation.

Reporting a problem

Open an issue at https://github.com/ToBee94/mumcord/issues with your OS, desktop (and Wayland/X11 on Linux), server version, and the diagnostic file. Never post passwords or your identity file.